Agile Manifesto

September 5, 2025
« Back to Glossary Index

What is the Agile Manifesto?

The Agile Manifesto is a foundational document that outlines the core values and principles of agile project management. Created in 2001 by a group of software developers, it promotes a flexible, people-focused approach to managing work, especially in fast-paced or uncertain environments. The manifesto encourages collaboration, responsiveness to change, and continuous delivery of value to customers. While initially designed for software development, its ideas now influence many industries and project types.

Key Points

  • The Agile Manifesto is based 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.
  • It includes 12 principles that provide further guidance on agile work practices, such as delivering value frequently, welcoming changing requirements, and maintaining a sustainable pace.
  • The manifesto shifts focus from rigid planning and control to flexibility, teamwork, and customer satisfaction.
  • It supports iterative development, where teams work in small cycles to produce usable outcomes on a regular basis.
  • Agile methods guided by the manifesto often result in faster delivery, higher quality, and better alignment with customer needs.

Related Terms

  • The Scrum framework is a popular agile method that follows the principles outlined in the Agile Manifesto through structured roles, events, and artifacts.
  • Kanban methodology uses visual boards and continuous delivery to apply agile values to workflow management.
  • Sprints are short, time-boxed periods in Scrum that reflect the manifesto’s emphasis on frequent delivery and adaptation.
  • User stories represent customer-focused requirements, aligning with the manifesto’s value on customer collaboration.
  • A minimum viable product (MVP) supports the idea of delivering working software quickly to gather feedback and improve it.

Agile Manifesto: Example

A software company uses the Agile Manifesto to guide its mobile app development. Instead of following a detailed year-long plan, the team works in short cycles, delivering updates every two weeks. They meet daily to discuss progress and challenges, quickly adapt when users request changes, and prioritize direct communication over lengthy reports. This approach helps the team stay aligned with customer needs and market trends.

Agile Manifesto: Best Practices

  • Educate teams on the values and principles to create a shared understanding of agile work.
  • Encourage open communication and face-to-face collaboration whenever possible.
  • Focus on delivering small, usable results frequently to gain feedback and improve.
  • Be flexible and prepared to adjust plans in response to real-world changes or user input.
  • Build a culture that values trust, teamwork, and continuous learning.

Additional Resources

Agile Manifesto - The Project Manager's Guide to Mastering Agile: Principles and Practices for an Adaptive Approach     Agile Manifesto - Clean Agile: Back to Basics

Preparing for a PMI certification?

« Back to Glossary Index