Agile software development names a family of iterative, incremental approaches to building software, favoring working software, direct collaboration with the customer, and responding to change over exhaustive up-front planning and documentation. On February 11 to 13, 2001, seventeen practitioners representing Extreme Programming, Scrum, Dynamic Systems Development Method, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming and related approaches met at a ski lodge in Snowbird, Utah, and produced the Manifesto for Agile Software Development, a short statement of four values and twelve principles. The meeting grew out of an earlier gathering of Extreme Programming practitioners that Kent Beck organized in Oregon in the spring of 2000. The manifesto did not invent iterative development, which the individual methods represented at Snowbird had already practiced for years, but it named and unified the alternative to the heavier, document-driven processes then common in the industry, discussed above as the waterfall model.
Facts
Core PrincipleDevelop software in short, repeated cycles that deliver working software early and often, adjusting plans as real feedback arrives rather than committing to a complete specification before building begins. 1 Origin Year2001 is when the Snowbird meeting produced the Manifesto for Agile Software Development; the individual methods it united, including Extreme Programming and Scrum, were practiced for some years before the manifesto named the shared alternative. FAQs
What are the four values of the Agile Manifesto?
It values people, working software, customer collaboration and responding to change over processes, documentation, contracts and fixed plans.
The Manifesto for Agile Software Development states four values as pairs. It values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. The manifesto adds that there is value in the items on the right, but that the authors value the items on the left more. The items on the right are not rejected, only ranked below the ones on the left.
Connections
Associated With
Source Extreme programming (Wikipedia)Wikipedia contributors
Source Scrum (project management) (Wikipedia)Wikipedia contributors
In Field
Source Agile software development (Wikipedia)
Preceded By
Source History: The Agile Manifesto
Sources
1. History: The Agile Manifesto
Agile Manifesto (agilemanifesto.org), 2001opening paragraph
On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground.
- Preceded By: Waterfall Model
View the Source Scrum (project management) (Wikipedia)
Wikipedia contributors, Wikimedia FoundationAssociated With: Scrum (Software Development), IntroductionQuote, Associated With: Scrum (Software Development), Introduction
Scrum is an agile management team collaboration framework commonly used in software development and other industries.
View the Source Extreme programming (Wikipedia)
Wikipedia contributors, Wikimedia FoundationAssociated With: Extreme Programming, IntroductionQuote, Associated With: Extreme Programming, Introduction
As a type of agile software development, it advocates frequent releases in short development cycles, intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted.
View the Source Agile software development (Wikipedia)
In Field: Software Engineering, Categories
Agile software development
In Group: Software Development Processes, Introduction
Agile software development is an umbrella term for approaches to developing software that reflect the values and principles agreed upon by The Agile Alliance, a group of 17 software practitioners, in 2001.
View the SourceReader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.
View At A Past Year
Choose a year to see this entry's facts and connections as the atlas records them at that moment: what it held then, what it held instead, and what it had not yet adopted. Choose Present for the current record.