The archive · Work & Ways of Doing · Operational decision · 2001
Agile Manifesto 2001: 17 developers sign 68 words that rewrite software delivery
Seventeen software rebels at a 2001 Utah ski resort sign a 68-word, four-value manifesto that turns software delivery away from heavyweight planning
Agile Alliance
What it had to solve
By 2000 a wave of 'lightweight' software methods — Extreme Programming, SCRUM, Crystal, DSDM, Feature-Driven Development — was succeeding where heavyweight, documentation-driven processes failed, but every camp promoted its own method and managers could not compare them.
How it works
In the late 1990s most software was built 'Waterfall' style: a project was designed up front in long documents, like manufacturing a wristwatch, and only then coded and shipped. Teams were regularly buried by planning they never got to use. Out of that frustration a set of insurgent methods — Extreme Programming, SCRUM, Crystal, DSDM, Adaptive Software Development, Feature-Driven Development — found success by delivering small working pieces fast, each camp led by a vocal practitioner with its own vocabulary.
Robert C. Martin of Object Mentor emailed the method leaders in September 2000 to propose a reunion; after a debate over venues, Snowbird, Utah beat Chicago and Anguilla. On February 11–13, 2001, seventeen people — some direct competitors — gathered at The Lodge at Snowbird ski resort and, over two days, negotiated down to four 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.
The signed page was 68 words; the group called itself the Agile Alliance. The manifesto did not prescribe any single practice, so no camp had to surrender its method to endorse it. Two decades later Agile is the default frame for software delivery — The Atlantic found it in use at Spotify and eBay, on Walmart's experiment record, and advertised in a Twitter job listing for an 'Agile Coach', with the Agile Alliance counting Lockheed Martin, ExxonMobil, and Verizon among its corporate members.
Why it lands
- 68 words fit whole on a slide: every article, talk, and job ad could quote the values verbatim, so the creed spread without anyone having to read a book.
- It united competitors by agreeing on values, not practices — Beck's XP and Schwaber's Scrum kept their differences while sharing the same creed.
- Plain, oppositional phrasing named a pain everyone felt — 'documentation over working software' — turning a technical dispute into a statement anyone in the building could take sides on.
- Because the manifesto set priorities, not rules, it needed no updates: twenty years on it still says the same four lines.
What it did
A 68-word document that became the industry's rallying creed: the Agile Alliance counts Lockheed Martin, ExxonMobil, and Verizon among corporate members, and The Atlantic could confirm Agile in use at Spotify, eBay, and Walmart — stand-ups, sprints, and iterations became default vocabulary.
What you can take
One page of shared values outweighs volumes of methodology docs: keep it short enough to quote whole, plain enough for rivals to sign, and let the creed evangelize.
Since then
The manifesto has never been revised; the alliance added twelve principles and the document's wording remains the canonical citation for Agile. Its two signatories Ken Schwaber and Jeff Sutherland later codified Scrum into the guide used around the world, and 'Agile Coach' became a real job title. The same success bred its own critique — the idea became so corporate-ubiquitous that 'agile theater', process without the values, became a running complaint, which the manifesto's own slogan about values over tools arguably anticipated.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card