The c value is calculated for each node that has a target date. It is equivalent to the number of standard deviations between the node's expected and target dates. It is calculated using the formula
w here /, is the expected date and T the target date.
Exercise 7.7 The c value for event 4 is (10 - 9.00)/0.53 = 1.8867.
Calculate the c values for the other events with target dates in the network show n in Figure 7.4.
Converting z values to probabilities
A z value may he converted to the probability of not meeting the target date by using the graph in Figure 7.5.
This graph is the equivalent of tables of z values, also known as standard normal deviates, which may be found in most statistics textbooks
Exercise 7.8 Ilie z value for the project completion (event 6) is 1.23. Using Figure 7.5 we can see that this equates to a probability of approximately 11that is, there is an 11K risk of not meeting the target date of the end of week 15.
Find the probabilities of not achieving events 4 or 5 by their target dates of the end of week 10.
What is the likelihood of completing the project by week 14?
We have seen that by requesting multivalued activity duration estimates and calculating expected dates. PERT focuses attention on the uncertainty of forecasting. We can use the technique to calculate the standard deviation for each task and use this to rank them according to their degree of risk. Using this ranking, we can see, for example, that activity F is the one over which we have greatest uncertainty, whereas activity C should, in principle, give us relatively little cause for concern.
If we use the expected times and standard deviations for forw ard passes through the network we can, for any event or activity completion, estimate the probability of meeting any set target. In particular, by setting target dates along the critical path, we can focus on those activities posing the greatest risk to the project's schedule.
As an alternative to the PERT technique, and to provide a greater degree of flexibility in specifying likely activity durations, we can use Monte Carlo simulation techniques to evaluate the risks of not achieving deadlines. The basis of this technique is the calculation of event times for a project network a large number of times, each time selecting activity times randomly from a set of estimates for each activity. The results are then be tabulated, summarized or displayed as a graph such as that show n in Figure 7.6.
Figure 7.6 Risk profile for on activity generated using Monte Carlo simulation.
Activity duration estimates can be specified in a variety of forms, depending upon the information available. If for example, we have historic data available about the durations of similar activities, we might be able to specify durations as a probability distribution. With less information available we should, at least, be able to provide three time estimates as used by PERT.
Monte Carlo simulation was also discussed in Section 3.7 in the context of project evaluation.
There are a number of packages available for carrying out Monte Carlo simulation. Some will exchange data with project scheduling applications and some interface to standard spreadsheet software. The majority of these packages will apply Monte Carlo risk analysis to cost and resource as well as duration estimates.
In this chapter, we have seen how to identify and manage the risks that might affect the success of a project. Risk management is concerned with assessing and prioritizing risks and drawing up plans for addressing those risks before they become problems.
This chapter has also described techniques for estimating the effect of risk on the project's activity network and schedule.
Many of the risks affecting software projects can be reduced by allocating more experienced staff to those activities that are affected. In the next chapter we consider the allocation of staff to activ ities in more detail.
1. Identify five risks than might affect the success of the Brightmouth College payroll project and suggest strategies that Brigette might consider for dealing with each of them.
2. The list of risks and risk reduction strategies in Table 7.2 is concerned with generic risks for software projects. What additional risks, in addition to those itemized in Table 7.1, can you identify that would be specific to Amanda's IOE accounts project?
3. List the major risks that might affect your next programming assignment and identify strategies for minimizing each of those risks.
4. If you have access to a project planning computer application find out whether or not it supports the PERT methods described in this chapter.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.