Agile is actually about making software development relevant to customers and doing it quickly

In 2001 seventeen “organizational anarchists” got together in a ski resort in Utah to discuss how software development could be best done with a specific view to moving away from document driven development.

They believed that traditional forms of development disaggregated developers from customers. They wished to move software development to later in the cycle and improve customer centricity.

They were fans of a variety of software development methods including Extreme Programming, scrum, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development and Pragmatic Programming. At the end of their seminar, they agreed the Agile Manifesto, which had twelve principles that can be seen below.

Agile principles
1. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
2. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
3. Continuous attention to technical  excellence and good design enhances agility.
4. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage
5. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
6. Business people and developers must work together daily throughout the project
7. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
8. Working software is the primary measure of progress.
9. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
10. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. Simplicity--the art of maximizing the amount of work not done--is essential.

 The original manifesto can still be found at:

Return to agile home

Common features of agile working

What is agile?