← VCE Software Development U3O2

Gantt chart: time allocation

The estimate of how long each task will take, shown on a Gantt chart as the length of its bar. Bars are measured in days or weeks and together set the total project length.

Part of: VCE Software Development - U3O2 - Analysis and Design — Module 16, VCE Data Analytics - U3O2 - Analysis and Design — Module 12

Understanding Gantt chart: time allocation in VCE Software Development U3O2

What it does: An estimate of duration is the time allocation, and it is set before the bar is drawn. The total project length comes from the time allocations on the chart, from the first bar's start to the last bar's end. Bar length shows how long the task is expected to take. This is its time allocation. Bars are drawn to scale, so a longer duration gives a longer bar. Short tasks are best shown in days. Larger projects may use weeks. Years would be far too coarse. Estimates should be realistic and based on the work involved. Giving every task the same length ignores that tasks differ.

Common mistakes: Time allocation is measured in days or weeks, not dollars. Dollars measure cost. It should be 'Task B: Code, 10 days'. Tasks done one after another have their durations added. Multiplying gives a meaningless number. It should be 'Total = Design + Build'.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Gantt chart: time allocation to a class →

This module's key terms are also in a printable crossword (Modules 12–24) and word search (Modules 2–24).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
On a Gantt chart, what does the length of a task's bar show?
The importance of the task to the clientThe estimated time allocation for that task
Matches
Build database: bar spans Week 2 to Week 4, time allocation = 1 week
↓
The bar covers Weeks 2, 3 and 4, so the time allocation should be 3 weeks, not 1 week. The bar length and the stated duration do not match.
Applying
Meanings
Term
time allocation
Meaning
The estimate of how long each task will take, shown on a Gantt chart as the length of its bar. Bars are measured in days or weeks and together set the total project length.
Practice
Analyse needs: 3 days
Testing
Gaps
Total = 3 5 = 8 days
Check Answer
Spots
1Task A: Design, 3 days
2Task B: Code, 10 dollars

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Moose' badge — Tundra Champion, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. On a Gantt chart, what does the length of a task's bar show?
A. The estimated time allocation for that task ✓
B. The importance of the task to the client
Bar length shows how long the task is expected to take. This is its time allocation.
2. Which is an example of time allocation for a task?
A. Design the user interface: 5 days ✓
B. Design the user interface: Sam is responsible
Time allocation is a duration estimate, such as 5 days. Who does the task is a different detail.
3. A task is estimated to take 10 days and another 5 days. Which bar is longer on the same scale?
A. The 10-day task ✓
B. The 5-day task
Bars are drawn to scale, so a longer duration gives a longer bar.
4. Which time unit suits a Gantt chart for a small project with short tasks?
A. Years
B. Days ✓
Short tasks are best shown in days. Larger projects may use weeks. Years would be far too coarse.
5. When estimating how long a task will take, what is the best approach?
A. Give every task the same length so the chart looks neat
B. Consider the task's complexity and the developer's experience ✓
Estimates should be realistic and based on the work involved. Giving every task the same length ignores that tasks differ.

Match the Pairs

Design screens: 3 days → A task with a time allocation of 3 days, drawn as a bar that spans 3 days on the timeline
Testing: Week 5 to Week 6 → A task allocated 2 weeks, shown as a bar covering two week columns
Estimating duration: a developer predicts how long a task will take before drawing its bar → Write login module: 4 days (estimate)
Total project length: the combined bars, from the earliest start to the latest finish, set how long the project runs → Start: Week 1, Last task ends: Week 8, Total = 8 weeks
Build database: bar spans Week 2 to Week 4, time allocation = 1 week → The bar covers Weeks 2, 3 and 4, so the time allocation should be 3 weeks, not 1 week. The bar length and the stated duration do not match.
Plan: 2 days, Code: 5 weeks, Test: 3 days → The units are mixed (days and weeks), so the time allocations cannot be compared or added to find the total project length. Use one unit such as days throughout.

Key Term

time allocation
The estimate of how long each task will take, shown on a Gantt chart as the length of its bar. Bars are measured in days or weeks and together set the total project length.

Fill in the Blanks

1. Design: 3 days Build: 5 days Total = 3 + 5 = 8 days
Hint: Type the operator used to combine the durations of tasks done one after another.
2. Bar length = task duration
Hint: Type the word for how long a task is estimated to take.
3. Test: 2 weeks Release: 1 week Total = 2 + 1 = 3 weeks
Hint: Type the total project length as a number of weeks.
4. Duration = end date - start date
Hint: Type the date that the end date is measured from to work out a bar's length.
5. Screens: 4 Time per screen: 2 days Estimate = 4 * 2 = 8 days
Hint: Type the operator used to estimate a duration from a count and a time for each item.

Spot the Error

Question 1
A Task A: Design, 3 days
B Task B: Code, 10 dollars
C Task C: Test, 4 days
Line B — Time allocation is measured in days or weeks, not dollars. Dollars measure cost. It should be 'Task B: Code, 10 days'.
Question 2
A Design = 5 days
B Build = 8 days
C Total = Design * Build
D OUTPUT Total
Line C — Tasks done one after another have their durations added. Multiplying gives a meaningless number. It should be 'Total = Design + Build'.
Question 3
A task ← 'Testing'
B duration ← 3
C bar_length ← cost
D OUTPUT bar_length
Line C — A bar's length shows the task's estimated duration, not its cost. It should be 'bar_length ← duration'.
Question 4
A duration ← -5
B start ← 1
C finish ← start + duration - 1
D OUTPUT finish
Line A — A task's estimated duration must be a positive amount of time. A negative duration can't make a bar. It should be 'duration ← 5'.
Question 5
A Task: Write report
B Estimate: 14 weeks
C Bar length: 2 weeks
Line B — The bar length must match the estimated duration. A 2 week bar means a 2 week estimate. It should be 'Estimate: 2 weeks'.

Student with a class code? Join your class →