The four values
Agile values the left of each pair more — while still valuing the right:
| Value this… | …over this | |
|---|---|---|
| Individuals and interactions | over | processes and tools |
| Working software | over | comprehensive documentation |
| Customer collaboration | over | contract negotiation |
| Responding to change | over | following a plan |
The twelve principles (in brief)
- Satisfy the customer through early, continuous delivery of value.
- Welcome changing requirements, even late.
- Deliver working software frequently (weeks, not months).
- Business and developers work together daily.
- Build projects around motivated individuals; trust them.
- Favor face-to-face conversation.
- Working software is the primary measure of progress.
- Maintain a sustainable, constant pace.
- Continuous attention to technical excellence.
- Simplicity — maximize the work not done.
- The best work emerges from self-organizing teams.
- Reflect regularly and adjust how you work.
Paraphrased for brevity — see the original for exact wording.
Exam traps
- "No documentation/plans." Agile values them less than the left side, not zero.
- Agile = Scrum. Scrum is one agile framework; the Manifesto is the shared foundation.
- Change is bad. Agile explicitly welcomes change as a competitive advantage.
Test yourself
4 quick questions — tap an answer to check it instantly. Nothing is sent anywhere.
1. The Agile Manifesto has how many core values?
Answer: B. Four values and twelve principles.
2. Which does agile value MORE?
Answer: B. 'Individuals and interactions over processes and tools.'
3. In agile, the primary measure of progress is…
Answer: B. 'Working software is the primary measure of progress.'
4. Agile treats changing requirements as…
Answer: B. Agile welcomes changing requirements, even late, as a competitive advantage.
Sources
- Beck et al. — Manifesto for Agile Software Development (2001).
Summary and paraphrase for reference. See agilemanifesto.org for the original wording.