Pert chart
A PERT (Program Evaluation and Review Technique) chart is a project management tool that visualizes the tasks required to complete a project, their dependencies, and the time each task requires. Unlike Gantt charts that show work over time, PERT charts emphasize the relationships between tasks - which must finish before others can start - and identify the critical path that determines minimum project duration.
Why it matters
Complex projects fail not because individual tasks are difficult but because dependencies between tasks aren't understood. A delay in one task cascades through dependent work, causing deadline misses that seem to come from nowhere. PERT charts make these dependencies visible.
By identifying the critical path - the longest chain of dependent tasks - PERT analysis shows where delays matter most and where slack exists. This knowledge enables better resource allocation, more realistic scheduling, and earlier warning when projects are at risk.
How pert charts work
A PERT chart is a network diagram where nodes represent milestones or events, and arrows represent tasks with associated durations.
Events are points in time when tasks complete. They have no duration; they simply mark transitions.
Tasks are the work connecting events. Each task has an estimated duration and shows which event must complete before it can begin.
Dependencies are the arrows showing which tasks must complete before others can start. These relationships are the core insight PERT provides.
The resulting diagram shows all possible paths through the project, making it possible to analyze which sequences of work determine overall timeline.
Time estimation in pert
PERT uses three time estimates for each task to account for uncertainty:
These combine into an expected time using the formula:
Expected Time = (O + 4M + P) / 6
This weighted average acknowledges uncertainty while producing a single usable estimate. The formula weights the most likely estimate heavily while allowing extreme scenarios to influence the result.
Critical path analysis
The critical path is the longest sequence of dependent tasks through the project. It determines the minimum project duration because shortening any other path doesn't help - the project can't finish faster than its longest chain of dependencies.
Identifying the critical path reveals:
Pert vs. gantt charts
Both tools serve project planning but emphasize different aspects.
PERT charts excel at showing task relationships and identifying the critical path. They answer "what depends on what?" and "where are the bottlenecks?"
Gantt charts excel at showing work over time and resource allocation. They answer "what happens when?" and "who is working on what?"
Many project managers use both: PERT for initial planning and dependency analysis, Gantt for ongoing tracking and communication.
Creating a pert chart
Building a PERT chart follows a structured process.
List all tasks required to complete the project. Break work into meaningful chunks - too granular creates noise; too coarse hides dependencies.
Identify dependencies for each task. What must complete before this task can begin? Be explicit about every predecessor.
Estimate durations using the three-point method (optimistic, most likely, pessimistic) for each task.
Draw the network with events as nodes and tasks as arrows. Ensure every task connects properly to its predecessors and successors.
Calculate the critical path by finding the longest path through the network. Tools automate this, but understanding the logic helps interpret results.
Limitations of pert
PERT has constraints that inform when and how to use it.
Estimation accuracy depends on the quality of time estimates. If optimistic, pessimistic, and most likely times are poorly estimated, the analysis is unreliable.
Static dependencies may not reflect reality. In software development especially, dependencies often change as work proceeds. PERT charts need updating to remain useful.
Complexity at scale makes large PERT charts difficult to read and maintain. For very large projects, hierarchical approaches or specialized tools become necessary.
Resource constraints aren't directly modeled. PERT assumes unlimited resources; in practice, the same people work on multiple tasks, creating constraints the chart doesn't show.
Pert in agile environments
Agile methods typically don't use PERT charts, favoring flexible backlogs over detailed upfront planning. However, PERT thinking remains valuable.
Dependency awareness matters even in sprints. Understanding which stories block others helps prioritize effectively.
Release planning for fixed-deadline projects benefits from critical path analysis even when individual sprints remain flexible.
Integration milestones in larger programs have dependencies that PERT can illuminate even when component teams work in agile sprints.
The tool can complement agile methods without replacing them - applied where long-horizon planning is necessary while leaving near-term work to more flexible approaches.
