The Agile Manifesto
Jump to navigation
Jump to search
An The Agile Manifesto is a software development manifesto published in 2001.
- See: Kanban (Development), Self-Organizing Communities, Cross-Functional Team, Customer, End User, Continual Improvement Process, The Agile Manifesto.
References
2019b
- (Wikipedia, 2019) ⇒ https://en.wikipedia.org/wiki/Agile_software_development#Agile_software_development_values Retrieved:2019-4-27.
Based on their combined experience of developing software and helping others do that, the seventeen signatories to the manifesto proclaimed that they value:
That is to say, the items on the left are valued more than the items on the right.
As Scott Ambler elucidated:[1]
- Tools and processes are important, but it is more important to have competent people working together effectively.
- Good documentation is useful in helping people to understand how the software is built and how to use it, but the main point of development is to create software, not documentation.
- A contract is important but is no substitute for working closely with customers to discover what they need.
- A project plan is important, but it must not be too rigid to accommodate changes in technology or the environment, stakeholders' priorities, and people's understanding of the problem and its solution.
Some of the authors formed the Agile Alliance, a non-profit organization that promotes software development according to the manifesto's values and principles. Introducing the manifesto on behalf of the Agile Alliance, Jim Highsmith said, Template:Quote
- ↑ "Examining the Agile Manifesto". Ambysoft Inc.. http://www.ambysoft.com/essays/agileManifesto.html. Retrieved 6 April 2011.
References
2019a
- (Wikipedia, 2019) ⇒ https://en.wikipedia.org/wiki/Agile_software_development#Agile_software_development_principles Retrieved:2019-4-27.
The Manifesto for Agile Software Development is based on twelve principles:[1]
- Customer satisfaction by early and continuous delivery of valuable software.
- Welcome changing requirements, even in late development.
- Deliver working software frequently (weeks rather than months)
- Close, daily cooperation between business people and developers
- Projects are built around motivated individuals, who should be trusted
- Face-to-face conversation is the best form of communication (co-location)
- Working software is the primary measure of progress
- Sustainable development, able to maintain a constant pace
- Continuous attention to technical excellence and good design
- Simplicity—the art of maximizing the amount of work Template:Not a typo done—is essential
- Best architectures, requirements, and designs emerge from self-organizing teams
- Regularly, the team reflects on how to become more effective, and adjusts accordingly
- ↑ Kent Beck; James Grenning; Robert C. Martin; Mike Beedle; Jim Highsmith; Steve Mellor; Arie van Bennekum; Andrew Hunt et al. (2001). "Principles behind the Agile Manifesto". Agile Alliance. Archived from the original on 14 June 2010. http://www.agilemanifesto.org/principles.html. Retrieved 6 June 2010.