PERT (program evaluation and review technique) was developed for the US Navy in the late 1950s for the Polaris missile programme. A PERT chart is a network diagram: tasks and events connected by arrows that show what depends on what. Its other half is a way of estimating: each task gets an optimistic, a most likely and a pessimistic duration, and the expected time is a weighted average of the three.
The Gantt chart, named after Henry Gantt, who designed and popularised it in the 1910s, is a bar chart against a calendar. Each task is a bar showing when it starts and how long it takes. Modern Gantt charts also draw the dependency arrows, which is why the two are often confused. The difference is in what each is best at: the PERT chart for working out the logic and the uncertainty, the Gantt chart for running the schedule.
The same plan as a Gantt chart
The six tasks above with their expected times as durations. Requirements feed both design and content; build follows design; testing waits for both build and content.
| Task | Days | Waits for | Starts | Ends | Slack |
|---|---|---|---|---|---|
| A. Requirements | 4 | — | Day 1 | Day 4 | 0 (critical) |
| B. Design | 6 | A | Day 5 | Day 10 | 0 (critical) |
| C. Build | 10 | B | Day 11 | Day 20 | 0 (critical) |
| D. Content | 5 | A | Day 5 | Day 9 | 11 days |
| E. Test | 4 | C, D | Day 21 | Day 24 | 0 (critical) |
| F. Launch | 1 | E | Day 25 | Day 25 | 0 (critical) |
The project finishes on day 25. Critical path: A → B → C → E → F.
Content (D) has eleven days of slack, so its wide pessimistic estimate does not threaten the launch date. Design and build are both on the critical path and both have long tails: that is where the schedule risk is, and where to put the effort to reduce it.
Opens with the same links and parallel paths as above, and no account.
The differences at a glance
| PERT chart | Gantt chart | |
|---|---|---|
| Shape | Network diagram: boxes or nodes joined by arrows | Bars on a timeline, one row per task |
| Shows best | Dependencies and the paths through the project | Dates, durations, overlap and progress |
| Time | Expected durations, not drawn to scale | Drawn to scale against a calendar |
| Estimates | Three-point estimate per task (optimistic, most likely, pessimistic) | One duration per task |
| Best used for | Planning a new project with uncertain durations | Scheduling, tracking and sharing the plan |
The three-point PERT estimate
For each task, ask for three numbers: optimistic (O, if everything goes right), most likely (M) and pessimistic (P, if the likely problems happen). The expected time weights the most likely value four times. The spread between optimistic and pessimistic gives a measure of how uncertain the task is.
Expected time TE = (O + 4M + P) / 6
Standard deviation SD = (P - O) / 6
Path uncertainty SD(path) = square root of the sum of SD^2 for each task on the pathWorked example: PERT estimates for a small launch
Design and build have long pessimistic tails, so their expected times are a day or more above the most likely value. The Gantt chart below uses the expected times as durations.
Along the critical path (A, B, C, E, F) the standard deviations are about 0.7, 1.7, 2, 1.3 and 0 days. Squared and added they come to 9, so the path's standard deviation is 3 days. If the task times are roughly independent, that gives a range of about 22 to 28 days (one standard deviation either side of 25) to report instead of a single date.
| Task | Optimistic | Most likely | Pessimistic | Expected (TE) |
|---|---|---|---|---|
| A. Requirements | 2 | 4 | 6 | 4 |
| B. Design | 3 | 5 | 13 | 6 |
| C. Build | 6 | 9 | 18 | 10 |
| D. Content | 2 | 4 | 12 | 5 |
| E. Test | 2 | 3 | 10 | 4 |
| F. Launch | 1 | 1 | 1 | 1 |
Turning a PERT network into a Gantt chart
The network and the Gantt chart are two views of one set of tasks and links, so you do not need to draw both by hand. Enter each task with its expected time as the duration and link it to the tasks it waits for; the Gantt chart lays the bars out on the calendar and highlights the critical path. The critical path calculator on this site does the forward and backward pass and shows each task's slack, and opens the result as a Gantt chart.
Keep the three estimates somewhere you can find them, such as in the task notes. When a pessimistic case starts to happen, you know how far the date could move before you redo the plan.
Frequently asked questions
- What is the main difference between a PERT chart and a Gantt chart?
- A PERT chart is a network diagram that shows how tasks depend on each other and estimates their durations with three values. A Gantt chart draws each task as a bar on a calendar, so it shows when work happens and how it overlaps.
- Is PERT better than a Gantt chart?
- They answer different questions. Use PERT estimating and a network view to work out the logic and the uncertainty of a new plan, then a Gantt chart to schedule, track and share it. Most teams end up running the project from the Gantt chart.
- How do you calculate a PERT estimate?
- Expected time = (optimistic + 4 x most likely + pessimistic) / 6. For example, 2, 4 and 6 days give (2 + 16 + 6) / 6 = 4 days.
- Is the critical path method the same as PERT?
- They are closely related. Both find the longest path through a network of dependent tasks. CPM uses one duration per task; PERT uses three-point estimates and adds a measure of uncertainty.
- Can I make a PERT chart in gantt-chart.io?
- gantt-chart.io draws the plan as a Gantt chart with dependency arrows and the critical path, not as a separate network diagram. Enter PERT expected times as the durations to get the schedule; the critical path calculator shows the slack for each task.
Sources
Related
Try it on your own plan
Paste a task list on the homepage and get a live Gantt chart with dependencies and a critical path. No account needed to try.