Agile manifesto

Definition

The Agile Manifesto is a foundational document created in 2001 by a group of software developers to guide agile development practices. It outlines core values and principles that prioritise collaboration, adaptability, and customer satisfaction over rigid processes and documentation. The manifesto serves as the philosophical framework behind agile methodologies such as Scrum, Kanban, and Extreme Programming.

For example, the Agile Manifesto shifts focus from delivering large, finalised products to delivering working software in smaller, iterative cycles that evolve based on feedback.

Advanced

The Agile Manifesto is built on four key 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. These values are supported by 12 guiding principles that promote continuous delivery, sustainable development, and close collaboration between business and technical teams.

Advanced application of the manifesto extends beyond software to project management, product design, and even organisational culture. Businesses adopt agile principles to improve responsiveness in competitive markets. Integrating the manifesto with practices such as DevOps and Lean further strengthens adaptability, automation, and efficiency across development pipelines.

Why it matters

• Provides the foundation for agile methodologies used worldwide.
• Encourages flexibility to adapt to changing business needs.
• Improves collaboration between stakeholders and developers.
• Supports faster delivery of value to customers.

Use cases

• Guiding the adoption of agile practices in software development teams.
• Aligning project goals with customer feedback and collaboration.
• Training teams on agile values and principles to improve culture.
• Scaling agile practices across enterprise-level organisations.

Metrics

• Rate of customer satisfaction with iterative releases.
• Improvement in delivery speed and lead time.
• Adoption levels of agile values across teams.
• Reduction in project risks through continuous feedback.

Issues

• Misinterpretation of the manifesto as a rigid methodology rather than guiding values.
• Resistance from organisations accustomed to traditional project management.
• Inconsistent adoption across teams leading to fragmented processes.
• Overemphasis on speed without maintaining quality or sustainability.

Example

A software company struggling with delayed product launches adopts agile practices based on the Agile Manifesto. By focusing on collaboration, frequent releases, and customer feedback, the company reduces time to market, improves team morale, and delivers solutions better aligned with customer needs.