---
# System prepended metadata

title: Agile Manifesto - from notes
tags: [Scrum]

---

# Agile Manifesto - from notes
###### tags: `Scrum`

## Manifesto for Agile Software Development

We are uncovering better ways of developing softwareby doing it and helping others do it.Through this work we have come to value:

1. **Individuals and interactions** over processes andtools
2. **Working software** over comprehensive documentation
3. **Customer collaboration** over contract negotiation
4. **Responding to change** over following a plan That is, while there is value in the items on the right, we value the items on the left more.

## Principles behind the Agile Manifesto

We follow these principles:

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
4. Welcome changing requirements, even late in development. Agile processe sharness change for the customer's competitive advantage.
6. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
8. Business people and developers must work togetherdaily throughout the project.
9. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
10. The most efficient and effective method of conveying information to and with in a development team is face-to-face conversation.
11. Working software is the primary measure of progress.
12. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
13. Continuous attention to technical excellence and good design enhances agility.
14. Simplicity the art of maximizing the amount of worknot done is essential.
15. The best architectures, requirements, and designs emerge from self-organizing teams.
16. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.