|
| 1 | +--- |
| 2 | +topic: agile |
| 3 | +aliases: agile-development, agile-software-development |
| 4 | +display_name: Agile |
| 5 | +short_description: Agile is a software development methology, popularized in the 2001 Manifesto for Agile Software Development. |
| 6 | +related: kanban, scrum, kanboard, project-management, agile-testing, okr, extreme-programming, feature-driven-development, tdd, waterfall-model |
| 7 | +url: https://agilemanifesto.org/ |
| 8 | +wikipedia_url: https://en.wikipedia.org/wiki/Agile_software_development |
| 9 | +released: 2001 |
| 10 | +created_by: Kent Beck, Ward Cunningham, Dave Thomas, Jeff Sutherland, Ken Schwaber, Jim Highsmith |
| 11 | +--- |
| 12 | +**Agile** is a software development methology. Popularized in the 2001 Manifesto for Agile Software Development, these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban. |
| 13 | + |
| 14 | +The following 12 Principles are based on the Agile Manifesto: |
| 15 | +1. Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software. |
| 16 | +2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. |
| 17 | +3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. |
| 18 | +4. Business people and developers must work together daily throughout the project. |
| 19 | +5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. |
| 20 | +6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. |
| 21 | +7. Working software is the primary measure of progress. |
| 22 | +8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. |
| 23 | +9. Continuous attention to technical excellence and good design enhances agility. |
| 24 | +10. Simplicity–the art of maximizing the amount of work not done–is essential. |
| 25 | +11. The best architectures, requirements, and designs emerge from self-organizing teams. |
| 26 | +12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. |
0 commit comments