Summary of the Agile Manifesto & Agile Principles

This post isn’t really news – the agile manifesto and agile principles have been put down on paper in 2001. However I wanted to post this here, so I can look it up anytime! :)

Agile Manifesto
Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Agile Principles
Customer satisfaction by early and continuous delivery of valuable software

Welcome changing requirements, even in late development

Working software is delivered frequently (weeks rather than months)

Close, daily cooperation between business people and developers

Projects are built around motivated individuals, who should be trusted

Face-to-face conversation is the best form of communication (co-location)

Working software is the principal measure of progress

Sustainable development, able to maintain a constant pace

Continuous attention to technical excellence and good design

Simplicity—the art of maximising the amount of work not done—is essential

Best architectures, requirements, and designs emerge from self-organising teams

Regularly, the team reflects on how to become more effective, and adjusts accordingly

Comments are closed, but trackbacks and pingbacks are open.