Any implementation of any project needs to be divided into several phases, and each stage can be divided into several steps. In order to improve the progress of the entire project, multiple groups of parallel implementations are used, but due to the time constraints between these steps (eg, buying cement, steel, brick tiles, etc.) before the construction of construction, We need to establish a key path first and then implement it in the order of order.
The method of key pathways is widely used for projects that produce-shaped products such as material production, architectural, but often ignored in software development projects. These scenarioses usually appear in the software project I developed: 2 modules A, B, and B dependence A (that is, it is required to develop, B after B), due to the development of A, cause A late due to some reason No completion (even yet started), how to deal with the developers when B needs to develop B? We will let B complete a part of the content in the internal process in the process (B needs to use A), and then directly embedding the contents directly into the contents of B after complexing.
This method results in repeated work: part of: B is completed in the internal completion of a part of the content; the other part is to replace the contents associated with A in B.
This problem is mainly, everyone has never seen the "key path" in software development, there is no "critical path" in the brain. In addition, the easy-changing software of the software has caused everyone to do not realize the importance of "critical path". If the brick is in the construction, the cement has not arrived, we said that the brick is made first with soil, and the cement is changed to change the mud with cement. Anyone will find that this is uncommon, but it often happens in the software project.
