This is the voice of experience.
1, developers try to single-threaded work, while avoiding to participate in two or more projects and focus in order to ensure efficiency and quality.
2, commitment to customers outside the time limit, to leave a little extra time to the team, as a buffer between the two projects, to respond to regulatory requirements, the maintenance period of work, the project summary.
3, some of the technical documentation must not be less, not formality, but to facilitate future generations to take over. Interface documentation, database design specifications (can be directly reflected in the notes among the tables and fields, you do not have a document) is necessary, others see the situation.
4, forcing programmers to study the requirements document, interactive prototype, after ensuring full understanding of the needs, and then start.
5, before a prototype is not confirmed, the front and rear ends are prohibited to start.
6, someone must regularly reviewed (at least weekly) code failed to work overtime rework, not allowed to be lazy.
7, all of the demand for change must be documented, regardless of whether the impact on the schedule and cost, must be recorded.