The wind standard on the church spire, even by steel, if you don't know how to meet the art, you will be destroyed immediately by the storm.
- Heinrich. Hayne
I. Declaration of agile software development
1, individuals and interactions winning process and tools
People are the most important factors for success. Cooperation, communication, and interaction ability are more important than simple programming capabilities. A team consisting of average level of programmers, if there is a good communication skill, which will have a group of high-level programmers, but members can't communicate more likely to succeed.
Choosing the right tool instead of a large tool, using too much huge, cumbersome tools are like lacking tools, trying to use a tool until you find that he can't apply him when you can't apply him.
The team's construction is more important than the environment.
2, the software that can work is better than the document
Software with no documents is a disaster, too much document is worse than too little document. For a team, writing and maintaining a system principle and structural document will always be a good idea, the document should be short and the subject is prominent, the document is for program service, do not write documents for writing documents.
When you teach new team members, the best two documents are code and team. The code really expresses what he does. The interaction of people and people see the fastest and effective way to pass the content to others.
3, customer cooperation is better than contract negotiations
Successful projects require order, frequent customer feedback. Not relying on contracts or statements about work, but to make software customers and development teams work closely and provide feedback as much as possible. To let customers know that we and they are on the same front, the problem that needs to be solved is our common enemy.
4, the response change is better than the plan
The ability to respond changes often determine the success or failure of a software project. When we build a plan, it should ensure that the plan is flexible and easy to adapt to business and technical changes.
Plan must do it, but you can't do a long-term fine plan, making a detailed plan for short-term tasks, a long-term task, a rough plan.
in principle:
1. We must do the best to make customers satisfied through the as early as possible.
2. Even in the late development, you will also welcome the demand. Agile process uses changes to create competitive advantages for customers
3, frequently delivered software that can work, the interval delivered from a few weeks to a few months, the shorter delivery time interval, the better
4. During the development of the entire project, business people and development must work together every day.
5, build a project around the individual being embraced. Give them the required environment and support, and trust them to complete work
6. Methods of communicating information in the team, most effectively and efficient, is facing face-to-face communication
7. The software work is a metrics for the primary progress.
8. Agile process advocates sustainable development speed. Responsible persons, developers and users should be able to maintain a long-term, constant development speed
9. Constantly paying attention to excellent skills and good designs will enhance agility
10. Simple - Maximize the unfinished work - is fundamental
11, the best architecture, need and design from self-organizing team
12. Every time, the team will make anti-provinces better work, then adjust their behavior
