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.
Over the next weeks, We will discuss different parts of the Agile Manifesto, beginning with individuals and interactions.
People count the most on any project. People who are happy, who communicate well, and who support their teammates will help drive successful projects.
When you value elevating people over processes,
- Communication is clear and effective
- Communication is quick and efficient
- Teamwork becomes strong as people work together
- Development teams can self-organizeDevelopment teams have more chances to innovate
- Development teams can customize processes as necessary
- Development team members can take personal ownership of the project
- Development team members have deeper job satisfaction
Successful agile project team members need the capacity to be involved, responsible and innovative. People may need to let go of ego to work well as members of a team.
You use processes and tools on agile projects, but those tools are intentionally streamlined and directly support product creation. Agile approaches will always value people over processes.
* Agile Manifesto Copyright 2001: 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
This declaration may be freely copied in any form, but only in its entirety through this notice.
