A Program Evaluation Review Technique (PERT) chart is a visual project‑planning tool that maps the sequence of tasks required to complete a project, shows task dependencies, and helps estimate the project’s minimum completion time. Tasks or events are shown as nodes (often circles or rectangles) and are connected by arrows that indicate the required order of work. PERT is particularly useful when task durations are uncertain because it explicitly uses multiple time estimates for each activity (optimistic, most likely, pessimistic) to build probabilistic time estimates for the project.
Quick facts
– Origin: Developed in the 1950s by the U.S. Navy for the Polaris missile program.
– Primary focus: Task dependencies and timing under uncertainty (not cost or resources).
– Common pairing: PERT for planning and identifying the critical path; Gantt charts for scheduling and monitoring execution.
Sources: Investopedia; Program Evaluation and Review Technique (PERT) overview.
Main components of a PERT chart
– Nodes/Events/Milestones: Represent task start or completion points.
– Arrows/Activities/Vectors: Show tasks and the sequence between nodes; usually labelled with time estimates.
– Dependencies: The arrows reveal predecessor-successor relationships (which tasks must finish before others start).
– Critical path: The longest sequence of dependent tasks; defines the minimum overall project duration.
– Dummy activities (optional): Dashed or dotted arrows used only to preserve correct dependency logic without an actual task.
How PERT works (conceptual overview)
1. Break the project into discrete activities and identify dependencies.
2. For each activity, estimate three time values:
• Optimistic (O): shortest possible time (if everything goes well).
• Most likely (M): best estimate under normal conditions.
• Pessimistic (P): longest reasonable time (if problems occur).
3. Compute the expected time (TE) for each activity using the standard PERT formula:
TE = (O + 4M + P) / 6
(This gives a weighted average placing more weight on the most likely duration.)
4. Use those expected times to compute earliest and latest start/finish times for each node, identify slack/float, and find the critical path (no slack).
Practical, step‑by‑step guide to create a PERT chart
1. Define the project scope and deliverables: Clarify the end result and major milestones.
2. List activities: Decompose the project into individual tasks needed to reach milestones. Keep tasks at a manageable granularity.
3. Determine dependencies: For each task, identify predecessors and whether the relationship is Finish‑to‑Start, Start‑to‑Start, etc. (PERT generally uses Finish‑to‑Start).
4. Estimate durations with three values (O, M, P) for each activity. Gather input from subject‑matter experts or historical data.
5. Calculate expected times: TE = (O + 4M + P) / 6 for each activity.
6. Draw the network:
• Place a start node, draw arrows for activities to subsequent nodes until you reach the end node.
• Use dummy activities only when needed to maintain correct dependencies.
7. Perform forward pass to compute earliest start (ES) and earliest finish (EF) for all nodes using TE values.
8. Perform backward pass to compute latest finish (LF) and latest start (LS) for all nodes.
9. Compute slack/float = LS − ES (or LF − EF). Tasks with zero slack lie on the critical path.
10. Identify the critical path(s) and project duration (sum of TE along the critical path).
11. Validate with stakeholders; adjust task definitions or estimates if necessary.
12. Maintain and update the PERT chart as actual durations become known—recompute critical path and slack.
Interpreting a PERT chart — key outputs
– Project duration estimate: the length of the critical path using expected times.
– Critical activities: tasks on the critical path; delays here delay the overall project.
– Slack/float: how long noncritical tasks can slip without affecting the project finish date.
– Risk insights: tasks with large differences between optimistic and pessimistic estimates signal high uncertainty and may need contingency planning.
Example (simple, conceptual)
Suppose three activities A → B → C, where:
– A: O=2, M=4, P=8 → TE = (2 + 4*4 + 8)/6 = (2 + 16 + 8)/6 = 26/6 ≈ 4.33 days
– B: O=3, M=3, P=5 → TE = (3 + 12 + 5)/6 = 20/6 ≈ 3.33 days
– C: O=1, M=2, P=3 → TE = (1 + 8 + 3)/6 = 12/6 = 2 days
Project duration ≈ 4.33 + 3.33 + 2 = 9.66 days (critical path is A→B→C if no parallel tasks).
Advantages of PERT charts
– Emphasizes dependencies and sequence logic, making it easier to identify potential bottlenecks.
– Incorporates uncertainty through three-point estimating and produces probabilistic time estimates.
– Useful for complex projects with many interdependent tasks and uncertain durations.
– Encourages cross‑functional input and clarifies responsibility for tasks.
Disadvantages and limitations
– Produces time-focused analysis; does not directly show costs or resource allocations.
– Quality of the chart depends on the quality of the input estimates; subjective or biased estimates degrade usefulness.
– Can become complex and hard to read for very large projects without software.
– Time‑consuming to build and maintain—requires updates when estimates or task structure change.
PERT chart vs. Gantt chart — when to use which
– PERT charts: Best during project planning when identifying dependencies and estimating overall duration under uncertainty. Helpful to determine critical path and areas of risk.
– Gantt charts: Best for execution and monitoring because they show calendar dates, durations as bars, resource assignments, and progress over time. Many teams plan with PERT (for logic and critical path) and then convert to a Gantt for tracking and reporting.
Fast fact: Early Gantt charts did not show dependencies; modern Gantt tools typically do.
Tools and templates
– Manual: Paper or whiteboard for small projects.
– Excel: Build nodes and arrows manually or use templates—OK for basic charts.
– Specialized tools: Microsoft Project, Lucidchart, Primavera, Smartsheet—these support network diagrams, calculation of floats, and critical path analysis.
– Many tools can convert between network diagrams (PERT/CPM) and Gantt timelines.
Practical tips for making PERT effective
– Involve those doing the work when estimating O/M/P to reduce bias.
– Use historical data where possible to refine estimates.
– Limit task granularity—too many tiny tasks make the chart unwieldy; too few make it inaccurate.
– Recalculate and revalidate the network after any change in scope, resources, or actual task durations.
– Combine PERT with resource leveling and a Gantt chart when moving from planning to execution.
When to choose PERT over Gantt
– Use PERT when task durations are uncertain and you need probabilistic timing and a clear view of dependencies. Use Gantt when you need a calendarized schedule with resource assignments and progress tracking.
The bottom line
A PERT chart is a powerful planning tool for mapping task dependencies, estimating project duration under uncertainty, and identifying the critical path. It helps teams focus on where delays matter most and which tasks require contingency planning. To get real value from PERT, use rigorous three‑point estimating, involve subject experts, and update the network as actual progress and new information arrive. Many teams combine PERT for planning and critical‑path analysis with Gantt charts for execution and stakeholder reporting.
Sources
– Investopedia — “Program Evaluation Review Technique (PERT) Chart” (source URL provided).
– Program Evaluation and Review Technique — Wikipedia (for standard PERT expected time formula and historical context).