Agile Manifesto

### Introduction

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

* Comment: 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.

11

* **Wor**king software over comprehensive documentation

12

* Comment: 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 adds no value and is often quickly outdated.

13

* **Cu**stomer collaboration over contract negotiation

14

* Comment: 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.

15

* **Res**ponding to change over following a plan

16

* Comment: Agile teams should expect changes, such as in requirements or technical aspects, and design the source code to be easily adaptable. They should be prepared to adapt it to customer needs, even if it means deviating from the original plan.

17

18

That is, while there is value in the items on the right, we value the items on the left more.

19

20

* Comment: All items listed above have their right to exist and should not be ignored. However, to be most productive, the items on the left have higher priority.

### Mnemonic Bridge

**"Ind**ustrious **wor**ms **cu**ltivate **res**ilience."

### The 12 Principle

Additionally, there are [twelve principles](https://agilemanifesto.org/principles.html) for further guidance.