Agile is a set of values and principles, not a process or framework. It emerged in 2001 when seventeen software practitioners signed the Agile Manifesto. The manifesto is intentionally short — four values and twelve principles — because agile is a mindset, not a methodology.
The Manifesto
The four values are often quoted but rarely understood in context. Each value is a trade-off, not a rejection of the right-hand side.
| We value more | Over |
|---|---|
| Individuals and interactions | Processes and tools |
| Working software | Comprehensive documentation |
| Customer collaboration | Contract negotiation |
| Responding to change | Following a plan |
Individuals and interactions — the best tools won’t save a team that can’t communicate. Invest in people and their collaboration first; tooling supports them, not the other way around.
Working software — documentation has value, but it’s not the product. A running system that users can touch is worth more than a perfect specification nobody reads.
Customer collaboration — requirements change when customers see what’s possible. Continuous conversation beats a fixed contract.
Responding to change — plans are useful for alignment, but clinging to them when reality shifts is waste. Embrace change as a competitive advantage.
The 12 Principles
Grouped by theme rather than original order.
Delivery cadence
- Deliver working software frequently (weeks, not months)
- Working software is the primary measure of progress
- Satisfy the customer through early and continuous delivery
People
4. Build projects around motivated individuals — trust them
5. Business people and developers must work together daily
6. Face-to-face conversation is the most effective communication
Technical excellence
7. Continuous attention to technical excellence and good design
8. Sustainable development — maintain a constant pace indefinitely
9. Simplicity: maximise the amount of work not done
Self-organisation
10. The best architectures, requirements, and designs emerge from self-organising teams
11. The team regularly reflects on how to become more effective
12. Agile processes promote sustainable development
Modern Relevance
Agile is still critical in 2025, but the landscape has changed:
- DevOps and CI/CD make “deliver frequently” the default, not the aspiration
- Remote work challenges “face-to-face” but the principle (high-bandwidth communication) still applies
- Platform teams and Platform Engineering enable agile at scale without heavyweight frameworks
- Product thinking has matured — agile delivery without Product Discovery is just building the wrong thing faster
The important distinction is “doing agile” (ceremonies, tools, certifications) vs “being agile” (values internalised, teams empowered, feedback loops tight). Most organisations do the former and claim the latter.
Agile vs Waterfall
| Agile | Waterfall | |
|---|---|---|
| Planning | Iterative, adaptive | Upfront, sequential |
| Requirements | Evolving, user stories | Fixed, detailed specs |
| Delivery | Incremental (every sprint) | Big bang (end of project) |
| Feedback | Continuous | Late (after build) |
| Risk | Discovered early | Discovered late |
| Change | Embraced | Resisted / costly |
| Documentation | Sufficient | Comprehensive |
| Best for | Uncertain, evolving problems | Well-understood, stable scope |
Anti-Patterns
Dark Scrum — using Scrum ceremonies to micromanage rather than empower. Daily standups become status reports to managers.
Agile theatre — all the rituals, none of the values. Retros happen but nothing changes. Sprints exist but scope is dictated top-down.
Estimation as commitment — story points are a planning tool, not a promise. When estimates become deadlines, teams pad and trust erodes.
Wagile — waterfall with agile terminology. Requirements are still locked upfront; sprints are just two-week phases of a fixed plan.
Cargo-cult agile — copying practices from successful teams without understanding why they work. Spotify Model syndrome.