Chapter Two dead, tells the story of a project failure problem causes, and the various roles a project internal members faced:
(1) programming veteran, the main programmer: There is no blueprint prior to construction, will encounter many unexpected problems. Unless you can be sure you can make something, otherwise it is difficult to say how long it would take: This is the Jianmin teacher has been giving us issues highlighted in the program before doing a little small projects, for the time they need to do an estimate before doing it is necessary to estimate what kind of think back to their own problems encountered in the production of their familiarity with this issue, and so it takes time to resolve, and then through such a process can clearly They know their strengths and their weak areas. There are problems blueprint, in the production of items they need to make at least need to be cleared out of the feature, and then infer the problems, and so you may encounter.
(2) relatively young programmers, novice: too many uncertainties, the time you need depends on the time spent by others: issues related to the cooperation between the teams, due to the very limited time to make the project, and each the individual mandate there will be some dependence on others, in order to save time, in the allocation of tasks, you need to try to reduce such dependence.
Overall, the development plan before a project is more important than the development process of the entire project.