Program evaluation and review technique
(10 through 50) and six activities (A through F) The program evaluation and review technique (PERT) is a statistical tool used in project management, which was designed to analyze and represent the tasks involved in completing a given…
≈ 9 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
(10 through 50) and six activities (A through F) The program evaluation and review technique (PERT) is a statistical tool used in project management, which was designed to analyze and represent the tasks involved in completing a given project. PERT was originally developed by Charles E. Clark for the United States Navy in 19581; it is commonly used in conjunction with the Critical Path Method (CPM), which was also introduced in 1958.
History
PERT was developed primarily to simplify the planning and scheduling of large and complex projects. It was developed by the United States Navy Special Projects Office, Lockheed Aircraft, and Booz Allen Hamilton to support the Navy's Polaris missile project. It found applications throughout industry.
An early example is the 1968 Winter Olympics in Grenoble which used PERT from 1965 until the opening of the 1968 Games. This project model was the first of its kind, a revival for the scientific management of Frederick Taylor and later refined by Henry Ford (Fordism). DuPont's CPM was invented at roughly the same time as PERT.
Initially PERT stood for Program Evaluation Research Task, but by 1959 was renamed. It had been made public in 1958 in two publications of the U.S. Department of the Navy, entitled Program Evaluation Research Task, Summary Report, Phase 1. and Phase 2. both primarily written by Charles F. Clark.
In a 1959 article in The American Statistician, Willard Fazar, Head of the Program Evaluation Branch, Special Projects Office, U.S. Navy, gave a detailed description of the main concepts of PERT. He explained: Ten years after the introduction of PERT, the American librarian Maribeth Brennan compiled a selected bibliography with about 150 publications on PERT and CPM, all published between 1958 and 1968.
For the subdivision of work units in PERT another tool was developed: the Work Breakdown Structure. The Work Breakdown Structure provides "a framework for complete networking, the Work Breakdown Structure was formally introduced as the first item of analysis in carrying out basic PERT/CPM."
Terminology
te = \frac{o + 4m + p} 6 TE = \sum_{i=1}^n te_i standard deviation of time : the variability of the time for accomplishing an activity (σ te ) or a path (σ TE ) \begin{align} & \sigma_{te} = \frac{p-o} 6 \\[8pt] & \sigma_{TE} = \sqrt{\sum_{i=1}^n {\sigma_{te_i}}^2} \end{align} In order to determine this information it is assumed that the activities and normal duration times are given. The first step is to determine the ES and EF.
The ES is defined as the maximum EF of all predecessor activities, unless the activity in question is the first activity, for which the ES is zero (0). The EF is the ES plus the task duration (EF = ES + duration). The ES for start is zero since it is the first activity.
Since the duration is zero, the EF is also zero. This EF is used as the ES for a and b. The ES for a is zero. The duration (4 work days) is added to the ES to get an EF of four.
This EF is used as the ES for c and d. The ES for b is zero. The duration (5.33 work days) is added to the ES to get an EF of 5.33. The ES for c is four.
The duration (5.17 work days) is added to the ES to get an EF of 9.17. The ES for d is four. The duration (6.33 work days) is added to the ES to get an EF of 10.33.
This EF is used as the ES for f. The ES for e is the greatest EF of its predecessor activities (b and c). Since b has an EF of 5.33 and c has an EF of 9.17, the ES of e is 9.17. The duration (5.17 work days) is added to the ES to get an EF of 14.34. This EF is used as the ES for g. The ES for f is 10.33.
The duration (4.5 work days) is added to the ES to get an EF of 14.83. The ES for g is 14.34. The duration (5.17 work days) is added to the ES to get an EF of 19.51.
The ES for finish is the greatest EF of its predecessor activities (f and g). Since f has an EF of 14.83 and g has an EF of 19.51, the ES of finish is 19.51. Finish is a milestone (and therefore has a duration of zero), so the EF is also 19.51. Barring any unforeseen events, the project should take 19.51 work days to complete.
The next step is to determine the late start (LS) and late finish (LF) of each activity. This will eventually show if there are activities that have slack. The LF is defined as the minimum LS of all successor activities, unless the activity is the last activity, for which the LF equals the EF.
The LS is the LF minus the task duration (LS = LF − duration). The LF for finish is equal to the EF (19.51 work days) since it is the last activity in the project. Since the duration is zero, the LS is also 19.51 work days.
This will be used as the LF for f and g. The LF for g is 19.51 work days. The duration (5.17 work days) is subtracted from the LF to get an LS of 14.34 work days. This will be used as the LF for e. The LF for f is 19.51 work days.
The duration (4.5 work days) is subtracted from the LF to get an LS of 15.01 work days. This will be used as the LF for d. The LF for e is 14.34 work days. The duration (5.17 work days) is subtracted from the LF to get an LS of 9.17 work days.
This will be used as the LF for b and c. The LF for d is 15.01 work days. The duration (6.33 work days) is subtracted from the LF to get an LS of 8.68 work days. The LF for c is 9.17 work days.
The duration (5.17 work days) is subtracted from the LF to get an LS of 4 work days. The LF for b is 9.17 work days. The duration (5.33 work days) is subtracted from the LF to get an LS of 3.84 work days.
The LF for a is the minimum LS of its successor activities. Since c has an LS of 4 work days and d has an LS of 8.68 work days, the LF for a is 4 work days. The duration (4 work days) is subtracted from the LF to get an LS of 0 work days.
The LF for start is the minimum LS of its successor activities. Since a has an LS of 0 work days and b has an LS of 3.84 work days, the LS is 0 work days. The next step is to determine the critical path and if any activities have slack.
The critical path is the path that takes the longest to complete. To determine the path times, add the task durations for all available paths. Activities that have slack can be delayed without changing the overall time of the project.
Slack is computed in one of two ways, slack = LF − EF or slack = LS − ES. Activities that are on the critical path have a slack of zero (0). The duration of path adf is 14.83 work days.
The duration of path aceg is 19.51 work days. The duration of path beg is 15.67 work days. The critical path is aceg and the critical time is 19.51 work days.
There can be more than one critical path (in a project more complex than this example) or that the critical path can change. For example, let's say that activities d and f take their pessimistic (b) times to complete instead of their expected (T E ) times. The critical path is now adf and the critical time is 22 work days.
On the other hand, if activity c can be reduced to one work day, the path time for aceg is reduced to 15.34 work days, which is slightly less than the time of the new critical path, beg (15.67 work days). Assuming these scenarios do not happen, the slack for each activity can now be determined.
Start and finish are milestones and by definition have no duration, therefore they can have no slack (0 work days). The activities on the critical path by definition have a slack of zero; however, it is always a good idea to check the math anyway when drawing by hand.
LF a – EF a = 4 − 4 = 0 LF c – EF c = 9.17 − 9.17 = 0 LF e – EF e = 14.34 − 14.34 = 0 LF g – EF g = 19.51 − 19.51 = 0 Activity b has an LF of 9.17 and an EF of 5.33, so the slack is 3.84 work days. Activity d has an LF of 15.01 and an EF of 10.33, so the slack is 4.68 work days. Activity f has an LF of 19.51 and an EF of 14.83, so the slack is 4.68 work days.
Therefore, activity b can be delayed almost 4 work days without delaying the project. Likewise, activity d or activity f can be delayed 4.68 work days without delaying the project (alternatively, d and f can be delayed 2.34 work days each). . Note the critical path is in red.
Text derived from https://en.wikipedia.org/w/index.php?oldid=1371318921 under CC BY-SA 4.0; modifications have been made.
References
- ↩Wikipedia “Program evaluation and review technique” publication date (×1) · confidence 0.95 revision URL