Multiple activities often feed into other activities.
Critical Path Analysis and PERT are powerful tools that help you to schedule and manage complex projects.
They were developed in the 1950s to control large defense projects, and have been used routinely since then.
As with Gantt Charts , Critical Path Analysis (CPA) or the Critical Path Method (CPM) helps you to plan all tasks that must be completed as part of a project.
They act as the basis both for preparation of a schedule, and of resource planning. During management of a project, they allow you to monitor achievement of project goals. They help you to see where remedial action needs to be taken to get a project back on course.
Within a project it is likely that you will display your final project plan as a Gantt Chart (using Microsoft Project or other software for projects of medium complexity or an excel spreadsheet for projects of low complexity).The benefit of using CPA within the planning process is to help you develop and test your plan to ensure that it is robust. Critical Path Analysis formally identifies tasks which must be completed on time for the whole project to be completed on time. It also identifies which tasks can be delayed if resource needs to be reallocated to catch up on missed or overrunning tasks. The disadvantage of CPA, if you use it as the technique by which your project plans are communicated and managed against, is that the relation of tasks to time is not as immediately obvious as with Gantt Charts. This can make them more difficult to understand.
A further benefit of Critical Path Analysis is that it helps you to identify the minimum length of time needed to complete a project. Where you need to run an accelerated project, it helps you to identify which project steps you should accelerate to complete the project within the available time.
As with Gantt Charts, the essential concept behind Critical Path Analysis is that you cannot start some activities until others are finished. These activities need to be completed in a sequence, with each stage being more-or-less completed before the next stage can begin. These are 'sequential' activities.
Other activities are not dependent on completion of any other tasks. You can do these at any time before or after a particular stage is reached. These are non-dependent or 'parallel' tasks.
Use the following steps to draw a CPA Chart:
For each activity, show the earliest start date, estimated length of time it will take, and whether it is parallel or sequential. If tasks are sequential, show which stage they depend on.
For the project example used here, you will end up with the same task list as explained in the article on Gantt Charts (we will use the same example as with Gantt Charts to compare the two techniques). The chart is repeated in Figure 1 below:
|Task||Earliest start||Length||Type||Dependent on...|
|A. High level analysis||Week 0||1 week||Sequential|
|B. Selection of hardware platform||Week 1||1 day||Sequential||A|
|C. Installation and commissioning of hardware||Week 1.2||2 weeks||Parallel||B|
|D. Detailed analysis of core modules||Week 1||2 weeks||Sequential||A|
|E. Detailed analysis of supporting modules||Week 3||2 weeks||Sequential||D|
|F. Programming of core modules||Week 3||2 weeks||Sequential||D|
|G. Programming of supporting modules||Week 5||3 weeks||Sequential||E|
|H. Quality assurance of core modules||Week 5||1 week||Sequential||F|
|I. Quality assurance of supporting modules||Week 8||1 week||Sequential||G|
|J.Core module training||Week 6||1 day||Parallel||C,H|
|K. Development and QA of accounting reporting||Week 5||1 week||Parallel||E|
|L. Development and QA of management reporting||Week 5||1 week||Parallel||E|
|M. Development of Management Information System||Week 6||1 week||Sequential||L|
|N. Detailed training||Week 9||1 week||Sequential||I, J, K, M|
Critical Path Analyses are presented using circle and arrow diagrams.
In these, circles show events within the project, such as the start and finish of tasks. The number shown in the left hand half of the circle allows you to identify each one easily. Circles are sometimes known as nodes.
An arrow running between two event circles shows the activity needed to complete that task. A description of the task is written underneath the arrow. The length of the task is shown above it. By convention, all arrows run left to right. Arrows are also sometimes called arcs.
An example of a very simple diagram is shown below:
This shows the start event (circle 1), and the completion of the 'High Level Analysis' task (circle 2). The arrow between them shows the activity of carrying out the High Level Analysis. This activity should take 1 week.
Where one activity cannot start until another has been completed, we start the arrow for the dependent activity at the completion event circle of the previous activity. An example of this is shown below:
Here the activities of 'Select Hardware' and 'Core Module Analysis' cannot be started until 'High Level Analysis' has been completed. This diagram also brings out a number of other important points:
A different case is shown below:
Here activity 6 to 7 cannot start until the other four activities (11 to 6, 5 to 6, 4 to 6, and 8 to 6) have been completed.
Click the link below for the full circle and arrow diagram for the computer project we are using as an example.
This shows all the activities that will take place as part of the project. Notice that each event circle also has a figure in the bottom, right hand quadrant. This shows the latest finish time that's permissible for the preceeding activity if the project is to be completed in the minimum time possible. You can calculate this by starting at the last event and working backwards.The latest finish time of the preceeding event and the earliest start time of the following even will be the same for ciircles on the critical path.
You can see that event M can start any time between weeks 6 and 8. The timing of this event is not critical. Events 1 to 2, 2 to 3, 3 to 4, 4 to 5, 5 to 6 and 6 to 7 must be started and completed on time if the project is to be completed in 10 weeks. This is the 'critical path' – these activities must be very closely managed to ensure that activities are completed on time. If jobs on the critical path slip, immediate action should be taken to get the project back on schedule. Otherwise completion of the whole project will slip.
You may find that you need to complete a project earlier than your Critical Path Analysis says is possible. In this case you need to re-plan your project.
You have a number of options and would need to assess the impact of each on the project’s cost, quality and time required to complete it. For example, you could increase resource available for each project activity to bring down time spent on each but the impact of some of this would be insignificant and a more efficient way of doing this would be to look only at activities on the critical path.
As an example, it may be necessary to complete the computer project in Figure 5 in 8 weeks rather than 10 weeks. In this case you could look at using two analysts in activities 2 to 3 and 3 to 4. This would shorten the project by two weeks, but may raise the project cost – doubling resources at any stage may only improve productivity by, say, 50% as additional time may need to be spent getting the team members up to speed on what is required, coordinating tasks split between them, integrating their contributions etc.
In some situations, shortening the original critical path of a project can lead to a different series of activities becoming the critical path. For example, if activity 4 to 5 were reduced to 1 week, activities 4 to 8 and 8 to 6 would come onto the critical path.
As with Gantt Charts, in practice project managers use software tools like Microsoft Project to create CPA Charts. Not only do these ease make them easier to draw, they also make modification of plans easier and provide facilities for monitoring progress against plans.
PERT is a variation on Critical Path Analysis that takes a slightly more skeptical view of time estimates made for each project stage. To use it, estimate the shortest possible time each activity will take, the most likely length of time, and the longest time that might be taken if the activity takes longer than expected.
Use the formula below to calculate the time to use for each project stage:
shortest time + 4 x likely time + longest time
This helps to bias time estimates away from the unrealistically short time-scales normally assumed.
Critical Path Analysis is an effective and powerful method of assessing:
An effective Critical Path Analysis can make the difference between success and failure on complex projects. It can be very useful for assessing the importance of problems faced during the implementation of the plan.
PERT is a variant of Critical Path Analysis that takes a more skeptical view of the time needed to complete each project stage.
This site teaches you the skills you need for a happy and successful career; and this is just one of many tools and resources that you'll find here at Mind Tools. Click here for more, subscribe to our free newsletter, or become a member for just $1.
This ensures that you don’t lose your plan.
Please enter your username or email address and we'll send you a reminder.
Your log in details have been sent to the email account you registered with. Please check your email to reset your login details.
Please check your Inbox, and click on the link in the email from us. We can then send you the newsletter.