Agile Manifesto

The Agile Manifesto (officially the Manifesto for Agile Software Development) is a brief, foundational document created in 2001 that changed how software is built. It was written by 17 software developers who met at a ski resort in Snowbird, Utah, to find an alternative to the “heavyweight,” documentation-heavy processes that were then standard.

The manifesto is built on 4 Core Values and 12 Guiding Principles.

1. The 4 Core Values

The manifesto famously uses the phrase “over” to show where the focus should shift. It does not say the items on the right are useless; it simply states that the items on the left are more valuable.

• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation.
• Responding to change over following a plan.

2. The 12 Guiding Principles

These principles provide the practical framework for the Agile mindset:

1. Customer Satisfaction: Priority #1 is satisfying the customer through early and continuous delivery.
2. Welcome Change: Changing requirements are viewed as a competitive advantage, even late in development.
3. Frequent Delivery: Deliver working software often (weeks rather than months).
4. Collaboration: Business people and developers must work together daily.
5. Support & Trust: Build projects around motivated people; give them the environment they need and trust them.
6. Face-to-Face Conversation: The most efficient way to convey information is through direct talk.
7. Working Software: This is the primary measure of progress.
8. Sustainable Development: Teams should be able to maintain a constant, steady pace indefinitely.
9. Technical Excellence: Continuous attention to good design and technical quality enhances agility.
10. Simplicity: Focus on the “art of maximizing the amount of work not done.”
11. Self-Organizing Teams: The best work comes from teams that manage themselves.
12. Regular Reflection: Teams should regularly pause to look at how to become more effective and adjust accordingly.

Why it matters

Before Agile, many projects followed the Waterfall model, where every detail was planned years in advance. This often led to software being “outdated” by the time it was actually finished. The Agile Manifesto shifted the industry toward a “learn as you go” culture that prioritizes people and adaptability.

In the video below, one of the original signatories explains the story and the thought process behind the creation of these values.