How do you guarantee a project finishes by its deadline when multiple tasks depend on each other? This is the central problem that scheduling and critical path analysis solve. For the CompTIA Project+ (PK0-005) exam, understanding how to build a schedule, identify which tasks are truly critical, and use visual tools like Gantt charts is essential because it tests your ability to plan and control project timelines without relying on guesswork.
Jump to a section
A simple way to picture Scheduling and Critical Path
A dinner party is a project with a strict deadline: guests arrive at 7 PM. The menu includes a roast chicken, roasted vegetables, a salad, and a dessert that needs to chill for four hours. The chicken must roast for 90 minutes and rest for 15 minutes before carving. The vegetables roast for 45 minutes. The dessert must be made and in the fridge by 3 PM. The salad is assembled in five minutes just before serving.
There is one oven. The chicken and vegetables cannot cook at the same time because they need different temperatures. Therefore, the chicken must go in first. After 45 minutes, the vegetables can go in the fridge to wait. The chicken finishes at 6:45 PM, rests until 7:00 PM, and the vegetables roast from 6:45 to 7:30 PM, which is too late. This is a schedule failure.
The critical path runs through the chicken (90 minutes roast + 15 minutes rest = 105 minutes), meaning everything that depends on the chicken being done—like carving and serving—is on the critical path. The dessert chilling is also on the critical path because it needs four hours and must start by 3 PM. The salad has float: it can be made at 6:55 PM without delaying the meal. The vegetables, however, create a delay because they must follow the chicken. The project manager (you) must adjust the schedule: parboil the vegetables so they only need 20 minutes, or start them earlier in a second oven. The critical path dictates that any delay in the chicken or dessert shifts the whole meal backward. This is exactly how project scheduling works with dependencies and critical path analysis.
Scheduling is the process of converting a project plan into a timeline. It answers the question: who does what, when, and for how long? The most common output is a schedule, which lists all tasks, their durations, their start and finish dates, and the people or resources assigned to them. Without a schedule, a project is just a wish list.
The Critical Path Method (CPM) is a mathematical algorithm used to identify the longest sequence of dependent tasks in a project. It calculates the shortest possible time to complete the entire project. To understand CPM, you must first understand a few core concepts:
Task: A single piece of work with a clear start and end, such as 'Write login page' or 'Install server'.
Duration: The amount of working time needed to complete a task, typically measured in hours, days, or weeks.
Dependency: A logical relationship between two tasks. The most common type is 'finish-to-start', meaning Task B cannot start until Task A finishes. For example, you cannot test software until it has been developed.
Milestone: A zero-duration marker representing a significant event, like 'Project kick-off' or 'Go-live decision'. Milestones have no work attached and act as checkpoints.
Float (or Slack): The amount of time a task can be delayed without affecting the project end date. Tasks on the critical path have zero float.
Early Start / Early Finish: The earliest possible start and finish dates for a task, assuming all predecessors finish as early as possible.
Late Start / Late Finish: The latest possible start and finish dates without delaying the project finish date.
The CPM algorithm works in two passes. The forward pass calculates the earliest dates each task can start and finish, working from the beginning of the project to the end. The backward pass calculates the latest dates each task can start and finish, working from the end of the project back to the beginning. The difference between the early and late dates is the float.
Why does the critical path matter? Because any delay on a critical path task directly delays the entire project. If a non-critical task slips, it might consume some of its float but not necessarily push the finish date. Project managers focus their attention on critical path tasks because they are the highest risk.
A Gantt chart is a visual bar chart that shows tasks as horizontal bars on a timeline. The length of each bar represents the task duration. Dependencies are shown as arrows linking bars. Gantt charts are easy to read and are the most common scheduling tool used in project management software like Microsoft Project, Jira, or Trello. They replace earlier manual methods like whiteboards or spreadsheets because they update automatically when dates change.
Before Gantt charts and CPM, managers often used simple task lists or wall charts. They had no reliable way to see how a delay in one area would ripple through the project. CPM introduced mathematical rigour, and Gantt charts made that rigour visually accessible. Today, most project scheduling software runs the critical path calculation automatically, but the CompTIA Project+ exam expects you to understand the logic so you can interpret the results when the tool flags a problem.
A common beginner mistake is confusing 'critical path' with 'most important tasks'. The critical path is the longest path, not necessarily the one with the most business value. A highly visible but easily accomplished task might have huge float, while a boring documentation task could be on the critical path if everything else depends on it.
In summary, scheduling transforms the plan into a workable timeline, CPM identifies which tasks must be protected from delay, and Gantt charts visualise the entire schedule in a way that stakeholders can understand at a glance.
Identify All Tasks and Milestones
Break the project down into individual pieces of work (tasks) and significant checkpoints (milestones). For example, 'Install server' is a task; 'Server installed' is a milestone. This step creates the work breakdown structure (WBS) that feeds into the schedule.
Sequence Tasks with Dependencies
Determine the logical order of tasks. Ask: which tasks must finish before others can start? For a software project, 'Write code' must finish before 'Test code'. Draw these relationships as a network diagram. This step is crucial because it builds the structure that the critical path calculation will use.
Estimate Task Durations
Assign a realistic duration to each task based on past experience, expert judgement, or historical data. Duration includes only working time, not calendar time. For example, 'Write login module' might be 5 days. Accurate estimates are essential because incorrect durations lead to wrong critical path identification.
Perform the Forward Pass
Calculate the earliest start and earliest finish for every task by moving from the project start to the end. For each task, its early start is the latest early finish of all its predecessors. This step reveals the earliest possible date the project can finish.
Perform the Backward Pass
Calculate the latest start and latest finish for every task by moving from the project end backward. For each task, its late finish is the earliest late start of all its successors. This step reveals how much each task can slip without delaying the project.
Calculate Float and Identify the Critical Path
Subtract early start from late start (or early finish from late finish) for each task. If the result is zero, the task is on the critical path. The path(s) with zero float is the critical path. This is the final step that tells the project manager where to focus attention.
An IT project manager at a medium-sized company is tasked with rolling out a new customer relationship management (CRM) system. The project has a fixed go-live date in 12 weeks because the old CRM contract expires that day. The PM must create a schedule, identify the critical path, and manage it so the deadline is met.
Step 1: The PM lists every task, from hardware procurement to data migration to user training. She estimates durations: server installation (2 weeks), software configuration (3 weeks), data cleansing (4 weeks), data migration (1 week), user acceptance testing (2 weeks), and training (1 week). She identifies dependencies: data migration cannot start until data cleansing is complete; user acceptance testing cannot start until data migration is complete; training cannot start until testing ends. Server installation and software configuration can run in parallel.
Step 2: She creates the network diagram (the logic map of dependencies) either by hand or in software. She runs the forward and backward pass to calculate early and late dates. The critical path turns out to be: data cleansing (4 weeks) -> data migration (1 week) -> user acceptance testing (2 weeks) -> training (1 week). Total: 8 weeks. The server installation and software configuration path is 5 weeks, so it has 3 weeks of float.
Step 3: The PM focuses on the critical path. She assigns her best data analyst to data cleansing and negotiates a backup if that person is sick. She monitors the critical path tasks daily in her Gantt chart. Meanwhile, she allows the server team to use its float to try a new automated configuration tool.
Step 4: Midway through, data cleansing falls one week behind because the legacy data is messier than expected. Because this task is on the critical path, the entire project is now at risk of finishing one week late. The PM must take corrective action: she adds a second data analyst to work on the weekend (crashing) or reduces the scope of data cleansing (fast tracking). She updates the schedule, and the new finish date is pushed back unless she can recover.
What does the PM actually do differently because she understands the critical path? She prioritises her meetings and reviews around critical tasks. She communicates the risk to stakeholders with clarity: 'If data cleansing slips further, the go-live date will move.' She does not worry about the server team's progress because they have float. She uses the Gantt chart in the weekly status meeting to show the current progress against the baseline.
In the real world, the job title of the person doing this work might be 'Project Manager', 'Programme Manager', or 'Delivery Lead'. They use tools like Microsoft Project, Smartsheet, Jira (with plugins), or even spreadsheets if the project is small. The CompTIA Project+ exam tests whether you can identify which tasks are on the critical path given a simple network diagram, and what action to take when a critical task is delayed.
The PK0-005 exam tests scheduling and critical path heavily. You can expect 5-10 questions on this topic, spread across multiple-choice and scenario-based items. The exam objectives list: 'Explain schedule development, including tools like Gantt charts and the critical path method (CPM).' What does that actually mean for you?
Question types you will see:
Direct definition questions: 'Which of the following best describes the critical path?'
Calculation questions: 'Given the following task durations and dependencies, what is the duration of the critical path?' You will be given a table or small network diagram.
Scenario questions: 'A task on the critical path is delayed by three days. What is the impact on the project?' The answer is always: the project finish date is delayed by three days (unless float exists elsewhere, but by definition it does not on the critical path).
Tool questions: 'Which tool is used to display tasks as bars on a timeline?' Answer: Gantt chart.
Dependency questions: 'Which dependency type means Task B cannot start until Task A finishes?' Answer: Finish-to-Start.
Traps to watch for:
The exam will try to confuse you by showing a path that looks long but actually has float because tasks are in parallel. Always calculate the longest path through the network, not the sum of all task durations.
They might ask 'What is the total float of a task on the critical path?' The answer is zero. Beginners often think float is always positive or that critical path tasks have some buffer. They do not.
They might give you a Gantt chart and ask which tasks are on the critical path. Look for the bars that, if shifted right, would push the final milestone. Bars with no slack (they touch the next dependency arrow directly) are critical.
Be careful with the term 'lag'. Lag is a deliberate delay between tasks (e.g., waiting for paint to dry). Lag does not mean the task is on the critical path; it just adds duration.
Concepts they love to test:
Definition of critical path: the longest path through the project network.
Float (slack) calculation: Late Finish minus Early Finish, or Late Start minus Early Start.
Forward pass and backward pass logic. You might be asked to calculate the early start of a task given its predecessors.
The difference between finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependencies. The most common tested is finish-to-start.
The relationship between critical path and risk: tasks on the critical path are the highest risk to the project schedule.
Corrective actions: crashing (adding resources to a critical task to shorten its duration) and fast tracking (starting a task earlier by performing it in parallel with its predecessor, which increases risk).
Key definitions to memorise:
Critical Path: The sequence of tasks that determines the project's shortest possible completion time.
Float / Slack: The time a task can be delayed without affecting the project finish date.
Gantt Chart: A visual timeline showing tasks as horizontal bars.
Milestone: A zero-duration marker indicating a key event.
The critical path is the longest sequence of dependent tasks and determines the shortest possible project duration.
Tasks on the critical path have zero float: any delay in these tasks directly delays the project finish date.
Float (or slack) is the amount of time a task can be delayed without affecting the project end date.
Gantt charts visualise the project schedule as horizontal bars on a timeline, making dependencies and progress easy to see.
The two common corrective actions for critical path delays are crashing (adding resources) and fast tracking (overlapping tasks).
A milestone is a zero-duration marker used to signify a key event or decision point, not a task with work.
Dependencies define the logical order of tasks; the most common type is finish-to-start, where one task must finish before the next begins.
The critical path can change during the project if actual durations differ from estimates or if tasks finish early or late.
These come up on the exam all the time. Here's how to tell them apart.
Critical Path
Has zero float; any delay directly pushes the project end date
Is the longest sequence of dependent tasks
Project managers must monitor these tasks most closely
Non-Critical Path
Has positive float; small delays may not affect the end date
Is a shorter sequence or has parallel buffers
Project managers can assign less experienced staff here without high risk
Finish-to-Start Dependency
Task B cannot start until Task A finishes
The most common dependency type in projects
Example: 'Build car' finishes before 'Paint car' starts
Start-to-Start Dependency
Task B can start as soon as Task A starts
Often used for overlapping phases
Example: 'Write chapter 1' and 'Edit chapter 1' can start simultaneously
Forward Pass
Moves from project start to project end
Calculates earliest start and earliest finish
Determines the earliest possible project completion date
Backward Pass
Moves from project end back to project start
Calculates latest start and latest finish
Determines how much each task can slip without delaying the project
Gantt Chart
Shows tasks as horizontal bars on a timeline
Best for communicating schedule progress to stakeholders
Easy to see task durations and overlaps
Network Diagram (PERT Chart)
Shows tasks as nodes (boxes) connected by arrows
Best for showing logical dependencies and analysing the critical path
Does not include a time scale by default
Mistake
The critical path is the list of tasks that are most important to the business or customer.
Correct
The critical path is determined by the longest sequence of dependent tasks, not by business priority. A low-priority administrative task can be on the critical path if everything else depends on it.
Beginners confuse importance with criticality because the word 'critical' in everyday language means 'extremely important'. In project management, it has a specific technical meaning related to time dependency.
Mistake
If a task has a long duration, it is automatically on the critical path.
Correct
A long-duration task can have float if it runs in parallel with an even longer chain of tasks. Only the path with the greatest total duration is the critical path.
People intuitively think that big tasks dominate the schedule, but parallel paths can make a shorter task critical if all other paths are shorter.
Mistake
Once a schedule is built, the critical path never changes.
Correct
As the project progresses, actual durations may differ from estimates, and task completions or delays can shift the critical path. It must be recalculated regularly.
Beginners treat the schedule as a static document, but project management is dynamic. The exam emphasises monitoring and controlling, which includes recalculating the critical path.
Mistake
All tasks on the critical path have zero float, so they cannot be delayed at all.
Correct
Critical path tasks have zero float in the baseline schedule, but if you add resources (crashing) or change the sequence (fast tracking), you can reduce their duration or overlap them. They are not immune to management action.
This misconception arises from a rigid interpretation of 'zero float'. The exam tests corrective actions that can be taken on critical tasks.
Mistake
Gantt charts are the same as network diagrams.
Correct
A Gantt chart shows tasks as bars on a timeline with dependencies as arrows, while a network diagram (PERT chart) shows tasks as boxes in a logical flow without a fixed timeline. They are different tools for different purposes.
Both are scheduling visuals, but beginners think all visual project charts are the same. The exam distinguishes between them.
Mistake
The critical path method can only be used for large, complex projects.
Correct
CPM can be used on any project with at least a few dependent tasks, including small IT rollouts, event planning, or software feature development. Its value scales with complexity but it is not exclusive to large projects.
Beginners assume mathematical methods are only for big corporate projects, but the PK0-005 exam includes small scenarios where CPM still applies.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Float and slack are the same thing: the amount of time a task can be delayed without affecting the project finish date. They are used interchangeably in project management and on the PK0-005 exam.
Yes, a project can have multiple critical paths. If two or more sequences of dependent tasks have the same longest duration, they are all critical. This increases project risk because any delay on any of those paths impacts the finish date.
Look for the sequence of tasks that, if any of them is delayed, would push the final milestone outward. Identify the chain of tasks where each task's bar touches the next task's dependency arrow with no gap. Those tasks have zero float and form the critical path.
If you add resources (crashing) to a critical path task, you may shorten its duration, which could shorten the overall project duration and potentially change the critical path. Non-critical tasks may become critical if they now have the longest duration.
No, the PK0-005 exam expects you to understand the logic and be able to perform simple calculations manually. In the real world, project managers use software, but the exam tests your conceptual understanding, not your proficiency with tools.
No. The schedule baseline is the approved version of the entire schedule, including all tasks, dependencies, and the critical path. The critical path is just one part of that baseline. The baseline is used to measure performance; the critical path identifies risk.
You've finished Scheduling and Critical Path. Continue through the PK0-005 study guide to build a complete picture of the exam.
Done with this chapter?