The Agile Manifesto » History » Version 1
Thomas Ganley, 02/24/2023 12:33 AM
1 | 1 | Thomas Ganley | h1. The Agile Manifesto |
---|---|---|---|
2 | |||
3 | Our highest priority is to satisfy the customer |
||
4 | through early and continuous delivery |
||
5 | of valuable software. |
||
6 | |||
7 | Welcome changing requirements, even late in |
||
8 | development. Agile processes harness change for |
||
9 | the customer's competitive advantage. |
||
10 | |||
11 | Deliver working software frequently, from a |
||
12 | couple of weeks to a couple of months, with a |
||
13 | preference to the shorter timescale. |
||
14 | |||
15 | Business people and developers must work |
||
16 | together daily throughout the project. |
||
17 | |||
18 | Build projects around motivated individuals. |
||
19 | |||
20 | Give them the environment and support they need, and trust them to get the job done. |
||
21 | |||
22 | The most efficient and effective method of |
||
23 | conveying information to and within a development team is face-to-face conversation. |
||
24 | |||
25 | Working software is the primary measure of progress. |
||
26 | |||
27 | Agile processes promote sustainable development. |
||
28 | |||
29 | The sponsors, developers, and users should be able to maintain a constant pace indefinitely. |
||
30 | |||
31 | Continuous attention to technical excellence |
||
32 | and good design enhances agility. |
||
33 | |||
34 | Simplicity--the art of maximizing the amount of work not done--is essential. |
||
35 | |||
36 | The best architectures, requirements, and designs emerge from self-organizing teams. |
||
37 | |||
38 | At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. |