The Agile Manifesto
A collection of 4 values and 12 principles that define the mindset Agile teams strive for. Published in 2001 by 17 software developers. It describes a philosophy; specific frameworks like Scrum and kanban are the means by which the philosophy is practiced.
The four values
The manifesto prefers the items on the left over those on the right — while still valuing both:
- 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 12 principles, grouped into 4 themes
Theme 1 — Value Delivery
How do Agile teams deliver highly valuable products?
- Highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Deliver working software frequently, from a couple of weeks to a couple of months.
- Working software is the primary measure of progress.
- Simplicity — the art of maximizing the amount of work not done — is essential.
- Continuous attention to technical excellence and good design enhances agility.
Summary: Deliver fast to get feedback and mitigate time risk. Simplicity lets the team focus on what matters.
Theme 2 — Business Collaboration
How do Agile teams work with business partners?
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Business people and developers must work together daily throughout the project.
Summary: Constant collaboration with the business enables instant adjustment to new information.
Theme 3 — Team Dynamics and Culture
How does a team maintain the interpersonal dynamics that deliver value?
- Build projects around motivated individuals. Give them the environment and support they need; trust them to get the job done.
- Face-to-face conversation is the most efficient and effective way to convey information.
- Agile processes promote sustainable development. Sponsors, developers, and users should maintain a constant pace indefinitely.
- The best architectures, requirements, and designs emerge from self-organizing teams.
Summary: Make sure the team is motivated, trusted, resourced, and working at a sustainable pace.
Theme 4 — Retrospectives and Continuous Learning
How does the team continuously increase performance?
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Summary: Strive to continuously learn and adapt.
Questions for improvement:
- How is the team doing?
- Are the customers happy?
- Are there processes or tools we could optimize?
- Are we following the values?
Application
The manifesto is a reference for mindset, not procedure. When a team debates whether to follow a process strictly or bend it to serve a customer need, the values give the answer: the left-hand items take precedence.
Connections
- scrum-framework — primary Agile framework that materializes the manifesto
- kanban vuca
- course-5-agile-project-management