Agile Software Development Declaration
Http://www.agilemanifesto.org/iso/zhchs/
We have been exploring better software development methods in practice and helping others. Therefore, we have established the following values:
Individuals and interactions are higher than processes and tools
Working software is higher than detailed documentation
Customer cooperation is higher than contract negotiation
Response changes are higher than follow-up plans
That is to say, although the right item has its value, we pay more attention to the value of the Left item.
|
Kent Beck Mike Beedle Arie Van bennekum Alistair Cockburn Ward cunnheim Martin Fowler |
James Grenning Jim Highsmith Andrew hunt Ron Jeffries Jon Kern Brian Marick |
Robert C. Martin Steve Mellor Ken schwaber Jeff Sutherland Dave Thomas |
Copyright owned by the aforementioned author, January 1, 2001
This declaration can be freely reproduced in any form, but its full text must include the above statement.
12 principles of Agile Software
1. Our most important goal is to satisfy our customers through continuous and early delivery of valuable software. [Continuous delivery]
2. We are happy to face the demand changes, even after development. Agile processes control changes for the competitive advantage of customers. [Embrace change]
3. often deliver workable software, which is several weeks or one or two months apart and tends to take a short period of time. [Small step forward]
4. Business and development personnel must cooperate with each other, and every day of the Project is no exception. [Close cooperation]
5. inspire individual morale and build projects with them as the core. Provide the required environment and support, coupled with trust, to achieve the goal. [People-oriented]
6. whether inside or outside the team, the best and most efficient way to deliver information is face-to-face conversations. Face-to-face communication]
7. Workable software is the primary measurement of progress. [Early delivery]
8. The agile process advocates sustainable development. The responsible person, developers and users should be able to maintain a stable and continuous pace together. [Steady and sustainable]
9. persistently pursuing technical excellence and good design, and increasing agility. [Pursuit of excellence]
10. being concise, it is an art to reduce unnecessary work. [Avenue to simplicity]
11. The best architecture, requirements, and design come from a self-organizing team. [Self-organizing team]
12. The Team regularly reflects on how they can improve their performance and adjust their behavior accordingly. [Regular reflection]