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