<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agile Software Development :: Link You to Scrum</title><link>/r4/agile/index.html</link><description>Agile Manifesto The Agile Manifesto serves as the foundation of agile software development.
4 Values:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
12 Principles:
Principles behind the Agile Manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 13 Feb 2026 14:45:46 +0800</lastBuildDate><atom:link href="/r4/agile/index.xml" rel="self" type="application/rss+xml"/><item><title>Scaling Agile</title><link>/r4/agile/scaling-agile/index.html</link><pubDate>Fri, 13 Feb 2026 14:45:46 +0800</pubDate><guid>/r4/agile/scaling-agile/index.html</guid><description>Scaling and Common Scaling Challenges Sometimes a product is too complex for a single team to handle. When this happens, there are two natural ways to scale:
Adding more people to the existing team Adding more teams However, simply doing either of these introduces new complexity of its own. More people and more teams mean more communication overhead, higher collaboration costs, and an increased risk of misalignment. Among the many challenges that arise, two are particularly critical:</description></item></channel></rss>