Network Planning and Critical Path Method
| Line 7: | Line 7: | ||
One of the benefits of using this tool is that allows to identify the most critical activities of the project. Moreover, if one of these is delayed, the project itself is compromised. Thus, it helps project managers to have a good overview in which task they must put more focus on. Nonetheless, CPM also has its limitations. In this article these disadvantages will be described and how to deal with them will be explained. | One of the benefits of using this tool is that allows to identify the most critical activities of the project. Moreover, if one of these is delayed, the project itself is compromised. Thus, it helps project managers to have a good overview in which task they must put more focus on. Nonetheless, CPM also has its limitations. In this article these disadvantages will be described and how to deal with them will be explained. | ||
| − | ==The Critical Path== | + | ==The Critical Path Method== |
===History=== | ===History=== | ||
| + | |||
| + | The critical path method or CPM was developed in the 1950s by two engineers working for the DuPont Corporation, Morgan R. Walker and James E. Kelly. Large building projects like the development of chemical and nuclear power facilities were the first ones to apply the critical route technique. Although it swiftly found uses in a variety of sectors, including as software development, manufacturing, and services. | ||
| + | |||
| + | The 1960s and 1970s saw a significant increase in the use of CPM as a tool for managing big, complicated projects. It was especially helpful for projects that called for the coordination of several interdependent activities as well as resources and timelines. | ||
==Implementation== | ==Implementation== | ||
Revision as of 18:14, 13 February 2023
Contents |
Abstract
Scheduling a project is one of the main challenges in project management. According to ISO21502 the purpose of schedule management is to enable work to be undertaken in a timely manner and to reduce slippage to an acceptable level. The schedule should be an integrated part of the project’s plan and developed under the direction of the project manager[1] .
There are several scheduling techniques that can be used to plan and estimate the duration of a project according to its complexity and uncertainty. One of the most common is the critical path method or CPM. This scheduling tool calculates the theoretical early and late start and finish dates for all activities, with no resource constraints, performing a bottom-up analysis forward and backward the entire network [2]. The “critical path” is the longest sequence of activities that must finish in time to fully complete the project. However, it also determines the shortest period in which the project can be finished.
One of the benefits of using this tool is that allows to identify the most critical activities of the project. Moreover, if one of these is delayed, the project itself is compromised. Thus, it helps project managers to have a good overview in which task they must put more focus on. Nonetheless, CPM also has its limitations. In this article these disadvantages will be described and how to deal with them will be explained.
The Critical Path Method
History
The critical path method or CPM was developed in the 1950s by two engineers working for the DuPont Corporation, Morgan R. Walker and James E. Kelly. Large building projects like the development of chemical and nuclear power facilities were the first ones to apply the critical route technique. Although it swiftly found uses in a variety of sectors, including as software development, manufacturing, and services.
The 1960s and 1970s saw a significant increase in the use of CPM as a tool for managing big, complicated projects. It was especially helpful for projects that called for the coordination of several interdependent activities as well as resources and timelines.
Implementation
Limitations
CPM vs other scheduling tools
Conclusion
See also
Bibliography
A Guide to the Project Management Body of Knowledge, fourth edition, 2008, Project Management Institute.
