Agile Manifesto

What is the Agile Manifesto?

The Agile Manifesto was published in 2001 under the name “Manifesto for Agile Software Development” and describes the rules of conduct and values of agile teams. The 17 authors include Jeff Sutherland and Ken Schwaber, the founders of the Scrum framework, and Ken Beck, the creator of the agile method Extreme Programming. Precisely because of its origins in software development, the Agile Manifesto also provides a reference for the collaboration of agile teams in other contexts.

Four guiding principles form the foundation of the Agile Manifesto

1. Individuals and interactions are more important than processes and tools.
2. Functioning software is more important than comprehensive documentation.
3. Collaboration with the customer is more important than contract negotiation.
4. Reacting to change is more important than following a plan.

What are the Agile Principles?

These four core statements are considered the pillars of the agile methodology. The 12 principles of the Agile Manifesto are based on them. Together with the four guiding principles, these much more detailed values form a concrete framework for agile teams.

The following 12 principles of the Agile Manifesto are defined

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome requirement changes even late in the development process. Agile processes use change to the customer’s competitive advantage.
3. Deliver working software regularly within a few weeks or months, preferring the shorter timeframe.
4. Subject matter experts and developers must work closely together throughout the process.
5. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
6. The most efficient and effective way to communicate information to and within a development team is face-to-face.
7. Working software is the most important measure of progress.
8. Agile processes promote sustainable development. Clients, developers and users should be able to maintain a steady pace indefinitely.
9. Constant attention to technical excellence and good design promotes agility.
10. Simplicity – the art of maximizing the amount of work not done – is essential.
11. The best architectures, requirements and designs are created by self-organized teams.
12. At regular intervals, the team reflects on how it can become more effective and adapts its behavior accordingly.