Agile Manifesto
What is the Agile Manifesto?
The Agile Manifesto is the 2001 statement of four values and twelve principles, written by seventeen practitioners at Snowbird, Utah, that founded the agile movement. It sets priorities for software work rather than a process.
Updated November 2026 · 3 min read
The Agile Manifesto, formally the Manifesto for Agile Software Development, is a short statement of four values and twelve principles for developing software in a way that responds to change and delivers working results early and often. It is the founding document of the agile movement. It does not prescribe a process; it describes priorities that methods such as Scrum, Extreme Programming and Kanban put into practice.
The manifesto was written in February 2001 by seventeen software practitioners who met at the Snowbird ski resort in Utah. They represented several "lightweight" methods, including Scrum, Extreme Programming, DSDM, Crystal, Feature-Driven Development and Adaptive Software Development, and agreed on "agile" as a common name. Signatories included Kent Beck, Alistair Cockburn, Ward Cunningham, Martin Fowler, Jim Highsmith, Ron Jeffries, Robert C. Martin, Ken Schwaber and Jeff Sutherland. The Agile Alliance, a nonprofit, was formed later that year.
The four values
The manifesto begins: "We are uncovering better ways of developing software by doing it and helping others do it." It then lists four preferences:
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
It ends: "That is, while there is value in the items on the right, we value the items on the left more." That sentence is often forgotten. The manifesto does not reject documentation, plans or contracts; it says which to favor when they conflict. See agile values for each value in practice.
The twelve principles
The principles, published alongside the values, are summarized here:
- Satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development, for the customer's competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, preferring the shorter timescale.
- Business people and developers work together daily throughout the project.
- Build projects around motivated individuals, give them the environment and support they need, and trust them.
- Face-to-face conversation is the most efficient and effective way to convey information to and within a team.
- Working software is the primary measure of progress.
- Promote sustainable development, with a pace sponsors, developers and users can maintain indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity, the art of maximizing the amount of work not done, is essential.
- The best architectures, requirements and designs emerge from self-organizing teams.
- At regular intervals the team reflects on how to become more effective and adjusts its behavior.
The agile principles entry covers how each one applies today.
How the Manifesto applies beyond software
The text names software, but teams in marketing, operations, HR and finance have adapted it by replacing "working software" with whatever their usable output is: a live campaign, a working process, a filled role. The underlying ideas of short feedback loops, close collaboration with the people being served and willingness to change course translate well. What translates less well is the assumption that output can be delivered in small, independent increments; some work, such as a regulatory filing, has to be complete to have value.
Agile Manifesto example
Consider a hypothetical agency building a booking system for a clinic network under a fixed-scope contract. Six weeks in, clinic staff testing an early version say that the most important need is not online booking but reducing no-shows. A strict contract reading would require a formal change request and re-pricing.
Applying the manifesto, the agency and client agree to swap three planned features, worth about 15% of the original estimate, for automated appointment reminders of similar size. The contract is amended to a fixed budget with scope agreed each month. Documentation is kept to what the clinic's IT team needs to run the system. The client gets the outcome it needed, and the change costs a two-hour meeting instead of a multi-week renegotiation.
Common misreadings
- "Agile means no documentation." The manifesto values working software more; it does not say documentation has no value. Write what people will actually use.
- "Agile means no planning." Responding to change requires a plan to change. Agile teams plan often, in smaller pieces.
- "The manifesto is a method." It is a set of values. Methods and frameworks are separate and should be judged against it.
- Following the tools over the values. Adopting tracking software and ceremonies while ignoring collaboration reverses the first value.
The Agile Manifesto is the source of agile as a shared idea and the basis for agile software development. Frameworks such as Scrum and Kanban are practical ways of acting on it.
Frequently asked questions
What are the four values of the Agile Manifesto?
The Agile Manifesto values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. It adds that the items on the right still have value, but the items on the left are valued more, so the values set priorities rather than rejecting plans or documents.
Who wrote the Agile Manifesto?
Seventeen software practitioners wrote the Agile Manifesto in February 2001 at the Snowbird ski resort in Utah. They represented methods including Scrum, Extreme Programming, DSDM, Crystal, Feature-Driven Development and Adaptive Software Development. Signatories included Kent Beck, Alistair Cockburn, Ward Cunningham, Martin Fowler, Jim Highsmith, Ron Jeffries, Robert C. Martin, Ken Schwaber and Jeff Sutherland.
Does the Agile Manifesto say teams should not write documentation?
No. The Agile Manifesto values working software over comprehensive documentation, but it explicitly says there is value in documentation too. It tells teams which to favor when the two conflict, not to stop writing documents. In practice, agile teams write the documentation people will actually use, such as what an operations team needs to run a system, and skip the rest.
Related terms
Agile Values
Four paired preferences at the heart of the Agile Manifesto.
Agile Principles
Twelve practical statements that accompany the Agile Manifesto.
Agile
Shipping small increments and adjusting the plan from frequent feedback.
Agile Software Development
Building software through brief iterations and frequent user feedback.