📋Agile Manifesto
Also known as Manifesto for Agile Software Development
A short list from 2001 with four values and twelve principles. Agile ways of working grow from it.
Think of it like
It is like the rules on a classroom wall. Four short lines say what the class cares about most.
Example
A team in Berlin argues about writing a 60-page spec first. They recall the second value, working software over documents. So they build a small test version instead.
Why it matters
Scrum, Kanban teams and Extreme Programming all point back to it. It is the shortest way to see what agile is for.
Definition
Common mistake
Key takeaways
- 1Four values. Each one puts people and results first.
- 2Twelve principles. Plain rules, like ship working software often.
- 3Left over right. The right side still has some value.