Tar pitfall-performance of project failure-zwavelet

The first part of the tar pit chapter shows the project failure:

"On the surface, it seems that no single problem will lead to difficulties, and every problem can be solved. But when they get entangled and accumulate together, the team's actions will become increasingly slow." We can hardly see the essence of the problem. However, if we want to solve the problem, we must first try to understand the problem.

Then, the introduction to "Programming System products" below reflects the shortcomings and misunderstandings of people who have known this problem and determined the workload, programs to programming products, programs to become a component of the Programming System, the workload needs to multiply by 3. To achieve most system development goals and programming system products, the workload needs to take 9.

If so, it is no wonder that a "good" software product cannot be launched as expected. However, is this data suitable for any situation? If so, how can we plan our product goals and product development processes? Can the boss accept the exponential increase in time and cost? There is no answer here. But how can we solve the problem?

Programming is "The pleasure and annoyance of the profession". In consideration of human factors, he only proposed the factors that will affect programmers. However, the human factor is the biggest variable and the most active factor in software engineering. General Software Engineering Research is measured by the average statistical value. However, how can this factor be effectively controlled? How to do it can improve their fun, reduce their distress, so that he can work efficiently.

But have Brooks fully expressed these questions and made the project fail ??

(The source text link has been lost)