Constructing a Gantt chart for a project

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. What is the first step when building a Gantt chart?

A Mark the critical path on the timeline

B List all the tasks the project needs

2. Which gives a task its bar length on a Gantt chart?

A Its dependency on other tasks

B Its estimated duration

3. Task B can't start until Task A finishes. What is this called?

A A dependency (A is a predecessor of B)

B A milestone

4. In a Gantt chart, how should a dependent task be drawn?

A Starting after the task it depends on finishes

B Starting on the same day as every other task

5. Which describes the critical path?

A The longest chain of dependent tasks, which sets the minimum project time

B The shortest chain of tasks, which can be skipped if time runs short

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1Task: Build login screen \| Duration: 3 days \| Depends on: Design mock-up		AThe tasks are ordered without considering dependencies. Testing is placed before Coding even though it depends on the code existing.
2Critical path: A -> C -> E (12 days)		BA task list entry that gives the task a name, an estimated duration and the earlier task it depends on, ready to be turned into a bar on the Gantt chart
3Adding a dependency: Task C cannot start until Task B has finished (finish-to-start)		CMilestone: Prototype approved \| Duration: 0 days \| Date: Day 15
4Marking a milestone: a zero-duration point showing a key deliverable is complete		DThe longest chain of dependent tasks on the chart, marked to show which tasks cannot be delayed without delaying the whole project
5Task list: Testing (5 days), Coding (10 days). Chart order: Testing starts Day 1, Coding starts Day 6		EThe critical path is the longest sequence of dependent tasks, not the shortest task. Tasks with float are not on it.
6Critical path = the task with the shortest duration on the chart		FTask C \| Start: after Task B ends \| Depends on: B

Definitions

Gantt chart

Fill in the Blanks

Complete each line of code by filling in the missing parts.

Task A: Analyse needs | ________: 3 days

A: Analyse needs (3 days) B: Design screens (2 days) B __________ A: start B after A ends

_________: Design signed off, 0 days

Critical path = _______ chain of tasks

Path A-B-D: 3 + 2 + 4 = 9 days Path A-C-D: 3 + 1 + 4 = 8 days Critical path: A, _, D

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A A: Plan, 3d, after none

B B: Design, 4d, after C

C C: Build, 6d, after B

Question 2

A Step 1: Draw the bars

B Step 2: Estimate durations

C Step 3: Order by dependency

D Step 4: Mark the critical path

Question 3

A A: Plan, 2d, after none

B B: Code, 5d, after A

C B starts on day 2

D B ends on day 7

Question 4

A A 2d, B 3d (after A)

B C 1d (after A)

C D 2d (after B and C)

D Critical path: A, C, D

Question 5

A Milestone: Prototype approved

B Shape: diamond

C Placed: end of Design phase

D Duration: 5d

Answer Key

Constructing a Gantt chart for a project

Section A: Quick Questions

B — List all the tasks the project needs

B — Its estimated duration

A — A dependency (A is a predecessor of B)

A — Starting after the task it depends on finishes

A — The longest chain of dependent tasks, which sets the minimum project time

Section B: Match the Pairs

Task: Build login screen | Duration: 3 days | Depends on: Design mock-up → A task list entry that gives the task a name, an estimated duration and the earlier task it depends on, ready to be turned into a bar on the Gantt chart

Critical path: A -> C -> E (12 days) → The longest chain of dependent tasks on the chart, marked to show which tasks cannot be delayed without delaying the whole project

Adding a dependency: Task C cannot start until Task B has finished (finish-to-start) → Task C | Start: after Task B ends | Depends on: B

Marking a milestone: a zero-duration point showing a key deliverable is complete → Milestone: Prototype approved | Duration: 0 days | Date: Day 15

Task list: Testing (5 days), Coding (10 days). Chart order: Testing starts Day 1, Coding starts Day 6 → The tasks are ordered without considering dependencies. Testing is placed before Coding even though it depends on the code existing.

Critical path = the task with the shortest duration on the chart → The critical path is the longest sequence of dependent tasks, not the shortest task. Tasks with float are not on it.

Section C: Definitions

Gantt chart — A bar chart built by listing tasks, estimating durations, ordering them by dependency, then marking milestones and the critical path on a timeline.

Section D: Fill in the Blanks

Task A: Analyse needs | Duration: 3 days

A: Analyse needs (3 days)
B: Design screens (2 days)
B depends on A: start B after A ends

Milestone: Design signed off, 0 days

Critical path = longest chain of tasks

Path A-B-D: 3 + 2 + 4 = 9 days
Path A-C-D: 3 + 1 + 4 = 8 days
Critical path: A, B, D

Section E: Spot the Error

B — Task C depends on B, so B cannot also depend on C. That makes a circular dependency. B should come after A.

A — The first step is to list every task. Bars cannot be drawn until the tasks, durations and dependencies are known.

C — A runs on days 1 and 2 and B depends on A. B must start on day 3, which also makes it end on day 7.

B — A, C, D is the longest path only if C takes 5d (9 days in total). With 1d, path A, B, D would be critical.

D — A milestone marks a point in time, not work. It has a duration of 0d.