Three printable worksheets that build from foundations to mastery — or build your own from any module’s questions.
Drawing Gantt charts from EST values · Reading schedules · Crashing the critical path
A project manager has completed all the critical path calculations. She knows which activities are critical and which have float. Now she needs to present the schedule visually to her team.
Before reading on — how might you represent the start time and duration of each activity on a single diagram? What information would be most useful to show?
A Gantt chart translates the numerical results of a CPA (EST values, durations, float) into a visual bar chart that is easy for teams to follow.
Project data (from Lesson 9 Worked Example 2):
| Activity | Dur | EST | Float | Bar: start → end | Float window |
|---|---|---|---|---|---|
| A | 2 | 0 | 0 | 0 → 2 | None (critical) |
| B | 4 | 2 | 0 | 2 → 6 | None (critical) |
| C | 3 | 2 | 4 | 2 → 5 | 5 → 9 (4 days) |
| D | 5 | 6 | 0 | 6 → 11 | None (critical) |
| E | 2 | 5 | 4 | 5 → 7 | 7 → 11 (4 days) |
On the Gantt chart, A, B, D are solid (critical); C and E have dashed float windows after their bars. The chart spans from 0 to 11 on the horizontal axis.
In the HSC, you may be given a Gantt chart and asked to extract information. Key things to read:
A Gantt chart shows: Activity G has a bar from day 3 to day 8 followed by a dashed window from day 8 to day 11.
How many workers needed simultaneously? If at day 5, activities A (0→7), G (3→8), and H (2→6) are all running, you need at least 3 workers at that time.
Crashing means reducing the duration of one or more activities by adding extra resources (more workers, overtime, better equipment) — at extra cost. The goal is to shorten the project's minimum completion time.
Project: Critical path A(5) → B(4) → D(3) = 12 days. Non-critical: C(3) with float 4.
Crash data:
| Activity | Normal dur | Crash time | Max crash | On critical path? |
|---|---|---|---|---|
| A | 5 | 3 | 2 | Yes |
| B | 4 | 4 | 0 | Yes |
| C | 3 | 2 | 1 | No (float=4) |
| D | 3 | 1 | 2 | Yes |
Maximum project reduction:
Check non-critical path: C has float 4. After crashing A by 2 and D by 2 (total 4 days saved), the critical path is now 8 days. Non-critical path through C = 3 + 3 = 6 ≤ 8. ✓ Still not critical.
Maximum reduction = 4 days. New minimum project duration = 8 days.
A project has the following CPA results:
| Activity | EST | Duration | Float |
|---|---|---|---|
| P | 0 | 4 | 0 |
| Q | 4 | 3 | 2 |
| R | 4 | 5 | 0 |
| S | 9 | 2 | 0 |
A construction project has critical path: Foundation (6 days) → Frame (5 days) → Roof (4 days) = 15 days. A parallel non-critical path has 3 days of float.
Crash data: Foundation can be crashed by 2 days; Frame cannot be crashed; Roof can be crashed by 1 day.
Q1. On a Gantt chart, the length of a solid bar represents the activity's:
Q2. Crashing a non-critical activity will:
Q3. Activity H has EST = 5, duration = 4, and float = 3. On the Gantt chart, the float window extends from day:
Q4. A project has critical path duration 14 days. Activity X (critical, normal duration 6 days) can be crashed to 4 days. Activity Y (non-critical, float = 3) cannot be crashed. After crashing X, the project duration is:
Q5. A Gantt chart shows activity J starting at day 2 with a bar ending at day 7 and a dashed window ending at day 10. The float for J is:
SAQ 1. A Gantt chart for a project shows: Activity A (bar 0→6), Activity B (bar 3→8 + float window 8→10), Activity C (bar 0→4 + float window 4→6), Activity D (bar 8→10). Identify the critical path activities and state the minimum project duration. Calculate the float for activities B and C.
SAQ 2. Explain why a project manager should only crash critical path activities if the goal is to reduce project completion time. Use the concept of float in your answer.
Q1 → D (Duration) — Bar length = duration of the activity.
Q2 → B — Crashing a non-critical activity does not affect project time; it only increases the activity's float.
Q3 → B (9 to 12) — Bar runs from EST=5 to EST+dur=9. Float window runs from 9 to 9+3=12.
Q4 → C (12) — Crash X by 2 days: 14 − 2 = 12. Check: non-critical path had float 3, so it doesn't become critical (its length ≤ 12).
Q5 → D (3) — Bar ends day 7, float window ends day 10. Float = 10 − 7 = 3.
SAQ 1: Activities without float windows: A (0→6) and D (8→10) are critical. Float for B = 10 − 8 = 2 days. Float for C = 6 − 4 = 2 days. Critical path: A → D (noting B starts at 3, during A; D starts when A ends at 6... then 8→10). Actually: A ends 6, D starts 8 — there's a gap. Check: if A is critical (bar 0→6, no float) and D is critical (8→10, no float), the critical path must include an activity 6→8. In the given description, B starts at 3 (not 6) and has float. So the critical path is A (0→6) + (implied activity 6→8 not shown or D actually starts at 6). Minimum project duration = 10 days (D finishes at 10, no float).
SAQ 2: Non-critical activities have float — they can be delayed by up to their float value without affecting project completion. So shortening a non-critical activity just increases its float; the project's minimum time (set by the critical path) is unchanged. Only by shortening a critical path activity — one with zero float — does the critical path length decrease and thus the project completion time decrease.
A Gantt chart is the answer. Each activity gets a horizontal bar: start at its EST, length equal to its duration. Non-critical activities get a dashed extension showing their float window. This lets the team immediately see which activities can be rescheduled (those with float) and which cannot (critical activities). For resource planning, the chart also shows which days have the most activities running in parallel, helping to spread worker demand evenly.
You can now draw and read Gantt charts, show float windows, and analyse crashing decisions on the critical path.