Waterloo of Software Development -- continue

After writing the previous two overview notes (see note 1 and note 2), I began to try to read and analyze each project case in more detail, and tries to summarize the key factors briefly, and then combine the previous project experience, follow the steps of discovering problems-analyzing problems-proposing your own solutions-finding similar situations in your previous projects-analyzing, comparing, and summarizing these cases repeatedly. However, with repeated studies of these cases, it is not easy to accomplish this task well, because real projects-the projects in the book are also true-are always so complicated, as the author said, there is indeed one of the most important factors that lead to Project Runaway, but more than one factor usually works at the same time.

To put it bluntly, even if we make the case analysis very clear, it is not that easy to build a project, because there are still many factors that cannot be completely controlled by us, it is best to make overall planning and risk management of the project.

When I think of this, I am happy and frustrated. Conflict.