You are on page 1of 1


Agile software development - Wikipedia, the free encyclopedia

Agile principles [edit]

The Agile Manifesto is based on twelve principles:[8] 1. Customer satisfaction by rapid delivery of useful software 2. Welcome changing requirements, even late in development 3. Working software is delivered frequently (weeks rather than months) 4. Working software is the principal measure of progress 5. Sustainable development, able to maintain a constant pace 6. Close, daily cooperation between business people and developers 7. Face-to-face conversation is the best form of communication (co-location) 8. Projects are built around motivated individuals, who should be trusted 9. Continuous attention to technical excellence and good design 10. Simplicitythe art of maximizing the amount of work not doneis essential 11. Self-organizing teams 12. Regular adaptation to changing circumstances



Later, Ken Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Ken left the Scrum Alliance in the fall of 2009, and founded to further improve the quality and effectiveness of Scrum. In 2005, a group headed by Alistair Cockburn and Jim Highsmith wrote an addendum ofproject management principles, the Declaration of Interdependence,[9] to guide software project management according to agile development methods. In 2009, a movement spearheaded by Robert C Martin wrote an extension of software development principles, the Software Craftsmanship Manifesto, to guide agile software development according to professional conduct and mastery.