Agile Manifesto for Software Development

The principles behind the way we work

The Agile Manifesto was devised in 2001 because there was a need for an alternative to document-driven, heavyweight software development processes. We abide by the manifesto, and our projects are a success because of it. It says that:

We are uncovering better ways of developing software by doing it and helping others to do it. Through this work we have come to value:
Individuals and interactions
over
processes and tools
Working software
over
comprehensive documentation
Customer collaboration
over
contract negotiation
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.

The Authors

Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas
© 2001, the Agile Manifesto authors
This declaration may be freely copied in any form, but only in its entirety through this notice.

Principles behind the Agile Manifesto

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