Skip to main content
Agile is not a process. It’s not a framework. It’s not Scrum with a capital S or a two-week sprint cadence. It’s a set of values and principles, written down in a Snowbird ski lodge in 2001 by seventeen software developers who were fed up with waterfall 🏔️ The Agile Manifesto is four sentences long. Most teams that say they’re “doing agile” have never read it.

​
The four values

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan
The right side isn’t worthless - processes, documentation, contracts, and plans all have their place. The left side just matters more.

​
What it actually means

Agile is a response to a specific failure mode: big upfront plans that collapse on contact with reality. The insight is that software development is an exercise in learning, not just execution. Requirements change, users surprise you, technical assumptions turn out to be wrong. The answer isn’t better planning. It’s shorter cycles, earlier feedback, and the ability to change direction without it costing a fortune 💡

​
Where it goes wrong

“Agile” has been co-opted so thoroughly that it now often means the opposite of what was intended. Scaled Agile frameworks with quarterly planning ceremonies and program increment objectives. Scrum Masters enforcing process compliance. Velocity metrics reported to executives as a measure of productivity. None of that is in the manifesto. What’s in the manifesto is: ship working software frequently, welcome changing requirements, and build around motivated individuals who are trusted to get the job done. Marty Cagan is pointed on this in Inspired - agile delivery without product discovery is just a faster way to build the wrong thing. The methodology only works if what flows into it has been validated 🙌

​
The frameworks

Agile principles get implemented through frameworks - Scrum, Kanban, Scrumban, XP, SAFe, and others. Each makes different trade-offs. None of them is agile itself. Lesson learned: the most agile team I ever worked on had no defined framework, no Scrum Master, and no story points. They talked to users every week, shipped every two weeks, and changed direction whenever the evidence said to. That’s what the manifesto was describing.