Gantt chart: sequencing tasks

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Sequencing on a Gantt chart means...

A Listing tasks alphabetically by name

B Putting tasks in the order they must happen

2. Task B needs Task A to be finished first. Where does B's bar start on the chart?

A At the same start point as A

B After A's bar ends

3. Two tasks do not depend on each other and the team has enough people. How can they be shown?

A As parallel tasks with overlapping bars

B One after the other, with no overlap

4. Which task order makes sense when sequencing a software project?

A Gather requirements, then design, then build

B Build, then design, then gather requirements

5. On a Gantt chart, what does the position of a task's bar tell you?

A When the task starts and ends

B How important the task is

Match the Pairs

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

Left column		Right column
1Task A: Week 1-2, Task B: Week 3-4		AThe tasks are in the wrong order. Code is written before the design exists, but design must come first and finish before coding starts.
2Task C: Week 1-3, Task D: Week 1-3		BSequential tasks: Task B starts only after Task A finishes, so the bars sit one after the other on the chart.
3A task that depends on another must start after the task it depends on has finished		CDesign interface: Week 2-4, Write data dictionary: Week 2-4
4Independent tasks can be placed in parallel to save project time		DTask B starts in Week 2 while Task A is still running, so the bars overlap. B depends on A's output and should start in Week 4 after A ends.
5Write code: Week 1-3, Design solution: Week 4-5		ETest software: starts Week 5, after Code software ends Week 4
6Task A: Week 1-3, Task B: Week 2-4 (B needs A's finished output)		FParallel tasks: C and D start in the same week and overlap, so they run at the same time.

Definitions

Sequencing

Fill in the Blanks

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

Design: Day 1-3 Code: Day 4-8 Code starts after ______ ends

Task A: Day 1-4 Task B: Day 1-3 A and B run in ________

Design: start Day 1, end Day 3 Code: start Day _, after Design ends

Plan: Day 1-2 Design: Day 3-5 Plan is sequenced ______ Design

A: Day 1-4, B: Day 1-3 Task C needs A and B done first C starts Day _ at the earliest

Spot the Error

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

Question 1

A Plan: wk 2-1

B Design: wk 3-4 after Plan

C Code: wk 5-8 after Design

Question 2

A Interview: wk 1-2

B Survey: wk 1-2 parallel

C Analyse: wk 1-2 after both

D Report: wk 5 after Analyse

Question 3

A Design: wk 1-2

B Code: wk 3-5 after Design

C Test: wk 6-7 after Code

D Release: wk 5 after Test

Question 4

A Login: wk 3-5

B Reports: wk 6-8 parallel

C Test: wk 6-7 after both

Question 5

A Needs: wk 1-2 after SRS

B SRS: wk 3-4 after Needs

C Design: wk 5-6 after SRS

Answer Key

Gantt chart: sequencing tasks

Section A: Quick Questions

B — Putting tasks in the order they must happen

B — After A's bar ends

A — As parallel tasks with overlapping bars

A — Gather requirements, then design, then build

A — When the task starts and ends

Section B: Match the Pairs

Task A: Week 1-2, Task B: Week 3-4 → Sequential tasks: Task B starts only after Task A finishes, so the bars sit one after the other on the chart.

Task C: Week 1-3, Task D: Week 1-3 → Parallel tasks: C and D start in the same week and overlap, so they run at the same time.

A task that depends on another must start after the task it depends on has finished → Test software: starts Week 5, after Code software ends Week 4

Independent tasks can be placed in parallel to save project time → Design interface: Week 2-4, Write data dictionary: Week 2-4

Write code: Week 1-3, Design solution: Week 4-5 → The tasks are in the wrong order. Code is written before the design exists, but design must come first and finish before coding starts.

Task A: Week 1-3, Task B: Week 2-4 (B needs A's finished output) → Task B starts in Week 2 while Task A is still running, so the bars overlap. B depends on A's output and should start in Week 4 after A ends.

Section C: Definitions

Sequencing — Putting tasks in the order they must happen on a Gantt chart. Tasks that depend on others start after them, while independent tasks can run in parallel (at the same time).

Section D: Fill in the Blanks

Design: Day 1-3
Code: Day 4-8
Code starts after Design ends

Task A: Day 1-4
Task B: Day 1-3
A and B run in parallel

Design: start Day 1, end Day 3
Code: start Day 4, after Design ends

Plan: Day 1-2
Design: Day 3-5
Plan is sequenced before Design

A: Day 1-4, B: Day 1-3
Task C needs A and B done first
C starts Day 5 at the earliest

Section E: Spot the Error

A — A task's end position cannot come before its start position on the chart. Plan should run from week 1 to week 2, so the line should be 'Plan: wk 1-2'.

C — Analyse depends on both the interview and the survey, so it cannot start until they finish. It should start in week 3: 'Analyse: wk 3-4 after both'.

D — Release depends on Test, which runs until week 7. Starting in week 5 puts it before its predecessor ends. It should start after Test, in week 8.

B — Parallel tasks run at the same time, so their bars must overlap. Reports should be weeks 3-5, level with Login. Weeks 6-8 would make it a later task, not a parallel one.

A — The first task has no predecessor, and SRS already depends on Needs. Making Needs wait for SRS creates a circular dependency. The line should be 'Needs: wk 1-2'.