Skip to Content

Wiki source code of Agile Manifesto

Version 1.10 by chrisby on 2023/10/20 19:40
Show last authors
1 ### Introduction
2
3 The [Agile Manifesto](https://agilemanifesto.org/) was created because of dissatisfaction with existing software development workflows such as [waterfall](https://en.wikipedia.org/wiki/Waterfall_model). It lays out ideals that guide software development teams toward more effective and adaptive practices, and serves as the ideological foundation for modern agile methodologies, including Extreme Programming, Scrum, and many others. Below is the original form of the Manifesto and some brief explanations.
4
5 ### Commented Agile Manifest
6
7 We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
8
9 * **Ind**ividuals and interactions over processes and tools
10
11 {{info}}
12 Ongoing human communication, teamwork, and collaboration are more important than strict adherence to processes such as workflows and guidelines, or software development and project management tools. Processes and tools should be flexible and enhance team productivity, not hinder it.
13 {{/info}}
14
15 * **Wor**king software over comprehensive documentation
16
17 {{info}}
18 The primary goal is to deliver a working product. Developers should aim for enough documentation to understand and maintain the software, but avoid excessive detail that does not add value.
19 {{/info}}
20
21 * **Cu**stomer collaboration over contract negotiation
22
23 {{info}}
24 Ongoing open communication with customers about the product is more important than relying strictly on the initial contract terms. Developers and customers should work together regularly to identify and address evolving requirements.
25 {{/info}}
26
27 * **Res**ponding to change over following a plan
28
29 {{info}}
30 Agile teams should expect changes, such as in requirements or technical aspects, and design the product to be flexible. They should be prepared to adapt it to customer needs, even if it means deviating from the original plan.
31 {{/info}}
32
33 That is, while there is value in the items on the right, we value the items on the left more.
34
35 Mnemonic Bridge: "**Ind**ustrious **wor**ms **cu**ltivate **res**ilience."
36
37 ### The 12 Principle
38
39 Additionally, there are [twelve principles](https://agilemanifesto.org/principles.html) for further guidance:
40
41 * Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
42 * Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
43 * Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
44 * Business people and developers must work together daily throughout the project.
45 * Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
46 * The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
47 * Working software is the primary measure of progress.
48 * Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
49 * Continuous attention to technical excellence and good design enhances agility. Simplicity, the art of maximizing the amount of work not done, is essential.
50 * The best architectures, requirements, and designs emerge from self-organizing teams.
51 * At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.