1. Describe errors with popular language, should not return the system directly to an error.
2. There is no giant, one by one review.
3. The legacy issues of the meeting must have a person responsible for the completion of time.
4. The pre-trial conference should be more effective than the temporary review.
5. Mail should reply in time and ask questions and suggestions.
6. While issuing important messages, use the phone or orally known.
7. Development must design the process and have a document.
8. Documentation review must establish a signature and pre-trial qualifications to review meetings.
9. The demand is unclear and cannot be guessed, and should be actively communicated with the customer.
10. The project group should have a blackboard, 1. Post progress and notice. 2. discuss. 3 praise and criticism
11. Project members have bad phenomena to stop as soon as possible, otherwise they will be bigger
12. A software project must have a quality assurance system, such as the automation test process of XUnit, cultivate the self-test awareness of developers, and can not rely on test or quality sector
13. The work of project members should be different as soon as possible to prevent access to the job, and use the XP process to interact and review, and share the code.
14. The power of the power will force people to mind narrow, and compete with each other. 15. Development team Max: "There is no reason, there is bug that is not." "In the event of an error", post it with big characters in a conspicuous place. 16. Don't let people can't hinder innovation.
