In the late 1990’s, several methodologies began to gain increasing public attention, each having a different combination of old and new ideas. These methodologies emphasized close collaboration between the development team and business stakeholders; frequent delivery of business value, tight, self-organizing teams; and smart ways to craft, confirm, and deliver code.
The term “Agile” was applied to this collection of methodologies in early 2001 when 17 software development practitioners gathered in Snowbird, Utah to discuss their shared ideas and various approaches to software development. This joint collection of values and principles was expressed in the Manifesto for Agile Software Development and the corresponding twelve principles.
The Agile Alliance was formed shortly after this gathering to encourage practitioners to further explore and share ideas and experiences.
12 Principles of Agile Software Development
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
Sources:
