The Agile methodology is a project management approach that involves breaking the project into phases and emphasizes continuous collaboration and improvement. Teams follow a cycle of planning, executing, and evaluating. Let’s start the Agile Cheat Sheet.

Agile Software Develo­pment
Group of software development methods in which requir­ements and solutions evolve through collab­oration between self-o­rga­nizing, cross-­fun­ctional teams.
– Adaptive planning
– Evolut­ionary develo­pment
– Early delivery
– Continuous improv­ement
– Rapid and flexible response to change
Agile Software Develo­pment frameworks
Adaptive software development (ASD)
Agile modeling
Agile Unified Process (AUP)
Crystal Clear Methods
Discip­lined agile delivery
Dynamic systems development method (DSDM)
Extreme progra­mming (XP)
Featur­e-d­riven develo­pment (FDD)
Lean software develo­pment
Kanban (devel­opment)
Scrum ban
Manifesto for Agile Software Develo­pment

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

– Indivi­duals and intera­ctions over Processes and tools
– Working software over Compre­hensive documentation
– Customer collab­oration over Contract negoti­ation
– Responding to change over Following a plan
– That is, while there is value in the items on the right, we value the items on the left more.[2]

Kent Beck, James Grenning, Robert C. Martin, Mike Beedle, Jim Highsmith, Steve Mellor, Arie van Bennekum, Andrew Hunt, Ken Schwaber, Alistair Cockburn, Ron Jeffries, Jeff Suther­land, Ward Cunnin­gham, Jon Kern, Dave Thomas, Martin Fowler, Brian Marick

© 2001, the above authors. This declar­ation may be freely copied in any form, but only in its entirety through this notice.

Agile Principles
Customer satisf­action by rapid delivery of useful software
Welcome changing requir­ements, even late in develo­pment
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-t­o-face conver­sation is the best form of commun­ication (co-lo­cation)
Working software is the principal measure of progress
Sustai­nable development, able to maintain a constant pace
Continuous attention to technical excellence and good design
Simpli­cit­y—the art of maximizing the amount of work not done—is essential
Self-o­rga­nizing teams
Regular adaptation to changing circum­stance

The Agile Manifesto is based on 12 principles

Leave a Comment