Using Pert For Schedule Estimation: Janet K. Ply, PHD President, Pendére Inc
Using Pert For Schedule Estimation: Janet K. Ply, PHD President, Pendére Inc
Using Pert For Schedule Estimation: Janet K. Ply, PHD President, Pendére Inc
Originally published in
Successful Project Management, May, 2002.
Estimation is not an easy task, especially for complex enterprise software solutions. We
seldom have sufficient information to understand completely the scope of the project, the
interfaces (oh, you expected these to be documented?), volumes of data (you expected the
data to be complete and accurate?), the amount of business process reengineering (yes,
we think there may be a few processes to change, but nothing major), and on and on. Yet,
the delivery team is expected to be able to take these types of ambiguous descriptions of
requirements and miraculously come up with an estimate within 0.5 percent accuracy.
Usually the budget gets based on some initial SWAG and then everyone expresses
disbelief that the project manager predicts cost and schedule overruns as more
information becomes available.
A powerful technique for estimating tasks where there may not be sufficient information
is the Program Evaluation Review Technique (PERT).Using the PERT approach for
determining the project schedule enables the project manager to provide much more
information by taking into account poorly defined areas, probabilities, and ranges for the
schedule (versus single point estimates).
PERT Estimation
PERT allows the estimator to include three estimates: optimistic, pessimistic, and most
likely, given by the equation:
For example, take a network with the following dependent tasks, with each successor task
having a finish-to-start relationship with the predecessor task:
Estimation Confidence
Another advantage of using PERT is that you are able to provide a level of confidence for
the duration that was developed. The probability of completing the project within the
expected duration can be calculated by the standard deviations of each task, given by the
equation1:
σ = pessimistic – optimistic
6
The standard deviation of the total path is given by taking the square root of the sum of
the squares of each task standard deviation. Using the earlier example, the standard
deviation for each task, as well as the overall network path standard deviation, is
calculated. The overall standard deviation is calculated as the square root of the sum of
the squares of each task’s standard deviation, as follows:
From statistics, one standard deviation (one sigma) represents a 68 percent chance of
completion, two standard deviations (two sigma) yield a 95 percent chance, and three
standard deviations (3 sigma) raise the chance to 99 percent. From our example, we can
determine ranges for completion using different standard deviations, as shown below:
Using this approach enables the project manager to take into consideration many of the
unknowns by stating project ranges with varying levels of confidence instead of the
single point estimate. The customer is given more information for decision-making and is
made aware of the levels of uncertainty and the impact they may have on the overall
schedule.
Now, when asked for a schedule estimate, the project manager can report something like,
“By using PERT, an approach based on probability and statistics, there is a 95 percent
confidence level that the project can be completed within 12 to 16 months. There is a
significant variance based on numerous areas of uncertainty, which is reflected in this
1
Harold Kerzner, Project Management, A Systems Approach for Planning, Scheduling, and Controlling, 6th
edition (New York: Van Nostrand Reinhold, 1998), pp.661-662.
range. A 99 percent confidence level will increase the range from 10 to 18 months. As
additional information becomes available, the variance should decrease and a smaller
range can be calculated.”
This is a much more powerful statement than “I think we can complete the project within
12 months but we can’t say for sure until we have more information.” See the difference?