Creating a critical path
Manasa Tallapaka
Ex-Amazonian|Parks Graduate Fellow|CREST COS member|AI/ML Enthusiast|Data Analyst|Geographer|Designer|Content creator|
Definition:
critical path refers to the list of required project milestones you must reach to complete the project schedule, as well as the mandatory tasks that contribute to the completion of each milestone. You can think of the critical path as a framework that tells you, the project manager, where you are, where you are headed, and when you will get there.?
Why the critical path is critical
How to create a critical path
Each project you work on will be different, but there are some general steps for creating a critical path that are applicable to most projects.
Step 1: Capture all tasks?
When you first start working on your project schedule, you will capture all of the tasks associated with the completion of the effort. Remember to use the key planning documents you have created to get you to this point, such as your work breakdown structure (WBS). The main goal in this step is to make sure that you aren’t missing a key piece of work that is required to complete your project. When creating a critical path, focus on the essential, “need to do” tasks, rather than the “nice to do” tasks that aren’t essential for the completion of the project. Here is an example of critical tasks for building the structure of a house:
Task
A) Excavation
B) Foundation
C) Framing
D) Roof
E) Plumbing
F) Heating, ventilation, and air conditioning (HVAC)
G) Electrical?
H) Insulation
I) Drywall + Paint
J) Flooring
Step 2: Set dependencies?
Now that you have captured all of your critical tasks in list form, arrange those tasks in order of completion by identifying dependencies. To determine dependencies, figure out which tasks must be completed before other tasks can start.
For example, you can’t paint the outside of a house before the house is built, so the task of framing the walls must come before the task of painting them. Identifying dependencies is key to a successful project schedule.?
To figure out dependencies for each task, ask:
Once you have answered these questions, you can list these dependencies next to your list of tasks:
Task Dependency
A) Excavation
B) Foundation
A) Excavation
C) Framing
D) Roof
领英推荐
E) Plumbing
F) HVAC
C) Framing
H) Insulation
I) Drywall + Paint
J) Flooring
Step 3: Create a network diagram
One common way to visualize the critical path is by creating a network diagram. Network diagrams, like the example below, sequence tasks in the order in which they need to be completed, based on their dependencies.
Step 4: Make time estimates
After determining tasks and dependencies, consult key stakeholders to get accurate time estimates for each task. This is a crucial step in determining your critical path. If your time estimates are significantly off, it may cause the length of your critical path to change. Time estimates can be reviewed and updated throughout the project, as necessary.?
Task Duration of Dependencies:
A) Excavation - 1 Day
B) Foundation - 3 Days
C) Framing - 15 Days
D) Roof - 3 Days
E) Plumbing - 4 Days
F) HVAC - 3 Days
G) Electrical? - 3 Days
H) Insulation - 2 Days
I) Drywall + Paint - 15 Days
J) Flooring - 7 Days
Step 5: Find the critical path?
Now that you have your estimated durations for each task, add that information to your network diagram:
If you add up the durations for all of your “essential” tasks and calculate the longest possible path, you can determine your critical path. In your calculation, only include the tasks that, if they go unfinished, will impact the project’s finish date.
In this example, if the “non-essential” tasks—like landscaping and driveway pavement—are not completed, the house structure completion date will not be impacted.?
You can also calculate the critical path using two common approaches:
1.The forward pass
2.The backward pass
These techniques are useful if you are asked to identify the earliest and latest start dates (the earliest and latest dates on which you can begin working on a task) or the slack (the amount of time that task can be delayed past its earliest start date without delaying the project).