The critical path method is a technique that allows you to identify tasks that are necessary for project completion. The critical path in project management is the longest sequence of activities that must be finished on time to complete the entire project. Below, we break down the steps of how you can find the critical path for your next project.
Building out a project roadmap can help you visualize what needs to be done to reach your end goal. The critical path method helps you do exactly that. It’s a project management technique that involves mapping out key tasks or critical tasks necessary to complete a project.
Leveraging this technique allows you to manage task dependencies and set realistic timeframes. Read on to find out how the critical path method works and how you can use it with your team to optimize project timelines.
The critical path method (CPM) is a technique where you identify tasks that are necessary for project completion and determine scheduling flexibilities. A critical path in project management is the longest sequence of activities that must be finished on time in order for the entire project to be complete. Any delays in critical tasks will delay the rest of the project.
CPM revolves around discovering the most important tasks in the project timeline, identifying task dependencies, and calculating task durations.
CPM was developed in the late 1950s as a method to resolve the issue of increased costs due to inefficient scheduling. Since then, CPM has become popular for planning projects and prioritizing tasks. It helps you break down complex projects into individual tasks and gain a better understanding of the project’s flexibility.Create a critical path method template
CPM can provide valuable insight on how to plan projects, allocate resources, and schedule tasks.
Here are some reasons why you should use this method:
Improves future planning: CPM can be used to compare expectations with actual progress. The data used from current projects can inform future project plans.
Facilitates more effective resource management: CPM helps project managers prioritize tasks, giving them a better idea of how and where to deploy resources.
Helps avoid bottlenecks: Bottlenecks in projects can result in lost valuable time. Plotting out project dependencies using a network diagram, will give you a better idea of which activities can and can’t run in parallel, allowing you to schedule accordingly.
Finding the critical path involves looking at the duration of critical and non-critical tasks. Below is a breakdown of the steps with examples.
Use a work breakdown structure to list all the project activities or tasks required to produce the deliverables. The list of activities in the work breakdown structure serves as the foundation for the rest of the CPM.
For example, let’s say the marketing team is producing a new interactive blog post. Here are some tasks that might be in the work breakdown structure:
Once you have a high-level idea of everything that needs to be done, you can start identifying task dependencies.Read: 4 types of concept maps (with free templates)
Based on your work breakdown structure, determine the tasks that are dependent on one another. This will also help you identify any work that can be done in parallel with other tasks.
Here are the task dependencies based on the example above:
Task B is dependent on A
Task C is dependent on B
Tasks C and D can run in parallel
Task E is dependent on D
Task F is dependent on C, D, and E
The list of dependent tasks is referred to as an activity sequence, which will be used to determine the critical path.
The next step is to turn the work breakdown structure into a network diagram, which is a flowchart displaying the chronology of activities. Create a box for each task and use arrows to depict task dependencies.
You’ll add other time-bound components to the network diagram until you have the general project schedule figured out.
To calculate the critical path, the longest sequence of critical tasks, you first need to estimate the duration of each activity.
To estimate the duration, try:
Making educated guesses based on experience and knowledge
Estimating based on previous project data
Estimating based on industry standards
Alternatively, try using the forward pass and backward pass technique:
Forward pass: This is used to calculate early start (ES) and early finish (EF) dates by using a previously specified start date. ES is the highest EF value from immediate predecessors, whereas EF is ES + duration. The calculation starts with 0 at the ES of the first activity and proceeds through the schedule. Determining ES and EF dates allows for early allocation of resources to the project.
Backward pass: This is used to calculate late start (LS) and late finish (LF) dates. LS is LF - duration, whereas LF is the lowest LS value from immediate successors. The calculation starts with the last scheduled activity and proceeds backward through the entire schedule.
The early and late start and end dates can then be used to calculate float, or scheduling flexibility of each task.
Calculating the critical path can be done manually, but you can save time by using a critical path algorithm instead.
Step 1: Write down the start and end time next to each activity.
The first activity has a start time of 0, and the end time is the duration of the activity.
The next activity’s start time is the end time of the previous activity, and the end time is the start time plus the duration.
Do this for all the activities.
Step 2: Look at the end time of the last activity in the sequence to determine the duration of the entire sequence.
Step 3: The sequence of activities with the longest duration is the critical path.
Using the same example above, here’s what the critical path diagram might look like:
Once you have the critical path figured out, you can build the actual project schedule around it.
Float, or slack, refers to the amount of flexibility of a given task. It indicates how much the task can be delayed without impacting subsequent tasks or the project end date.
Finding the float is useful in gauging how much flexibility the project has. Float is a resource that should be used to cover project risks or unexpected issues that come up.
Critical tasks have zero float, which means their dates are set. Tasks with positive float numbers belong in the non-critical path, meaning they may be delayed without affecting the project completion date. If you’re short on time or resources, non-critical tasks may be skipped.
Calculating the float can be done with an algorithm or manually. Use the calculations from the section below to determine the total float and free float.
Here’s a breakdown of the two types of float:
Total float: This is the amount of time that an activity can be delayed from the early start date without delaying the project finish date or violating a schedule constraint. Total float = LS - ES or LF - EF
Free float: This refers to how long an activity can be delayed without impacting the following activity. There can only be free float when two or more activities share a common successor. On a network diagram, this is where activities converge. Free float = ES (next task) - EF (current task)
There are a few good reasons why project managers benefit from having a good understanding of float:
It keeps projects running on time: Monitoring a project’s total float allows you to determine whether a project is on track. The bigger the float, the more likely you’ll be able to finish early or on time.
It allows you to prioritize: By identifying activities with free float, you’ll have a better idea of which tasks should be prioritized and which ones have more flexibility to be postponed.
It’s a useful resource: Float is extra time that can be used to cover project risks or unexpected issues that come up. Knowing how much float you have allows you to choose the most effective way to use it.
CPM provides visibility into your project’s progress, allowing you to monitor tasks and their completion times. Below are some additional applications of CPM.Create a critical path method template
Though not ideal, there are times when project deadlines may be pushed up. In those situations, there are two schedule compression techniques you can use: fast tracking and crashing.
Fast tracking: Look at the critical path to determine activities that can be performed simultaneously. Running parallel processes will speed up the overall duration.
Crashing: This process involves allocating more resources to speed up activities. Before obtaining more resources, make sure that it would still be within the project scope and let the stakeholders know of any changes.
Having the critical path plotted out can help you choose the appropriate strategy to meet updated deadlines.Read: How to create project schedules to make work easier
Keep in mind that CPM doesn’t take resource availability into account. When there is a resource shortage, like an overbooked team member or lack of equipment, you can use resource leveling techniques to solve the issue.
These techniques aim to resolve resource overallocation issues and ensure that a project can be completed with the resources that are currently available.
Resource leveling works by adjusting project start and end dates, so you may have to readjust the critical path or apply this technique to activities with float.Read: If you like maximizing team impact, you’ll love resource allocation
The schedule created from CPM is subject to change since you’re working with educated estimates for activity durations. You can compare the original critical path to the actual critical path as the project runs.
This data can be used as a reference to get more accurate task duration estimates for future projects.
CPM and Project Evaluation and Review Technique (PERT) were both developed in the 1950s. PERT is used to estimate uncertainty around project activities by applying a weighted average of optimistic and pessimistic. It evaluates the time needed to complete an activity.
PERT uses three estimates to find a range for the duration of an activity:
Most likely estimate (M)
The calculation for PERT is: Estimated time = (O + 4M + P) / 6
The main difference between PERT and CPM is their level of certainty around activity durations—PERT is used to estimate the time required to complete activities, whereas CPM is used when the activity durations are already estimated.
Let’s see how the two techniques compare:
PERT manages uncertain project activities, CPM manages predictable project activities.
PERT focuses on meeting or minimizing project duration, CPM focuses on time-cost-trade offs.
PERT is a probabilistic model, CPM a deterministic model.
PERT has three estimates for each activity, CPM just one.
Differences aside, both PERT and CPM analyze the following components:
List of required tasks
Estimated duration for each task
The two techniques can be used in tandem to boost their effectiveness. You can use PERT to get more realistic estimates of task durations before proceeding to calculate the critical path and floats.
Gantt charts are horizontal bar charts that map out project activities, which can be tracked against a set timeline. Both CPM and Gantt charts show the dependencies between tasks.
Let’s go over some differences between the two tools:
Visualizes critical and non-critical paths and calculates project duration
Displayed as network diagram with linked boxes
Doesn’t show resources required
Plots activities on network diagram without timescale
Visualizes how project activities are progressing
Displayed as horizontal bar chart
Shows resources required for each activity
Plots activities on a timescale
Gantt charts can be paired with CPM to track critical paths over time to keep your project running on schedule.
CPM can be a useful asset in project management, particularly for planning tasks and managing resources. With the help of project planning tools, you’ll be able to create schedules and track projects with ease. To further increase your work efficiency, check out 12 tips to be more productive today.Create a critical path method template