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