Show Menu

Principles of the Agile Manifesto Cheat Sheet (DRAFT) by [deleted]

Principles guiding software development

This is a draft cheat sheet. It is a work in progress and is not finished yet.


In February 2001 seventeen software developers met at a ski resort in Snowbird, Utah to do some skiing while spending time reflecting on what defined the core principles of agile software develo­pment methods. Although they had unique experience and expect­ations, they united with the objective to uncover better ways of developing software and to help others to do the same. In their discus­sions they found consensus around four main values, which we know now today as the “Agile Manife­sto”.

Manife­sto's 4 Guiding Values

Indivi­duals and intera­ctions over processes and tools
Working software over compre­hensive docume­nta­tion
Customer collab­oration over contract negoti­ation
Responding to change over following a plan

Supple­menting the Manifesto

1. Our highest priority is to satisfy the custom­ert­hrough early and continuous delivery of valuable software.
2. Welcome changing requir­ements, even late in develo­pment. Agile processes harness change for the customer’
compet­itive advantage.
3. Deliver working software freque­ntly, from a couple of weeks to a couple of months, with a preference to the shorter
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated indivi­duals. Give them the enviro­nment and support they need, and trust them to get the
job done.
6. The most efficient and effective method of conveying inform­ation to and within a develo­pment team is face-t­o-face
7. Working software is the primary measure of progress.
8. Agile processes promote sustai­nable develo­pment. The sponsors, develo­pers, and users should be able to maintain a
constant pace indefi­nitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simpli­cit­y–the art of maximizing the amount of work not done–is essential.
11. The best archit­ect­ures, requir­ements, and designs emerge from self-o­rga­nizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accord­ingly.

Agile Manifesto

Support Cheatography!