Signed in as:
filler@godaddy.com
Agile Manifesto
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others 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.
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-2019, the above Agile Manifesto authors
this declaration may be freely copied in any form,
but only in its entirety through this notice.
12 Principles behind the Agile Manifesto
Number 1
Number 1
Number 1
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Number 2
Number 1
Number 1
Welcome changing requirements, even in late development. Agile processes harness change for the customer's competitive advantage.
Number 3
Number 1
Number 3
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Number 4
Number 4
Number 3
Business people and developers must work together daily throughout the project.
Number 5
Number 4
Number 5
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Number 6
Number 4
Number 5
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Number 7
Number 8
Number 8
Working software is the primary measure of progress.
Number 8
Number 8
Number 8
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Number 9
Number 8
Number 10
Continuous attention to technical excellence and good design enhances agility.
Number 10
Number 10
Number 10
Simplicity -- the art of maximizing the amount of work not done -- is essential.
Number 11
Number 10
Number 11
The best architectures, requirements, and designs emerge from self-organizing teams.
Number 12
Number 10
Number 11
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.