← VCE Software Development U4O1

Annotating a project plan

A short dated note added to a project plan that explains a change, giving the date and the reason, or describes how far a task has progressed.

Part of: VCE Software Development - U4O1 - development and evaluation — Module 194

Understanding Annotating a project plan in VCE Software Development U4O1

What it does: The note shows the date (05/09) and the reason (client added a feature), as the concept says. The dated note describes progress by saying how much is complete and what remains. A good annotation includes a date and the reason for the change. 'Testing is late' gives neither. Annotations are short notes added to the plan. They explain what happened and why, and they do not replace the plan. The date shows when the change or progress update happened, so it can be compared with the timeline. Sickness explains why the task was changed. A progress explanation would say how much of the task is done.

Common mistakes: An annotation must include the date it was written. The note has a reason but no date, so nobody can tell when the change happened. It should be 'Note 12 May: Late, API down'. An annotation that explains a change must give the reason for it. This note has a date and says the task moved, but not why. It should be 'Note 3 Jun: Moved, Sam is ill'.

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 Annotating a project plan to a class →

This module's key terms are also in a printable crossword (Modules 186–198) and word search (Modules 172–198).

Take this worksheet further — free with Cloodit

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

Learning
Duo
Which is a proper annotation on a project plan?
12 May: Testing moved back 3 days because the login bug took longer to fix.Testing is late.
Matches
Task 3 delayed
↓
There is no date and no reason, so the note does not explain when or why the plan changed.
Applying
Meanings
Term
annotation
Meaning
A short dated note added to a project plan that explains a change, giving the date and the reason, or describes how far a task has progressed.
Practice
Task 4: Build login screen
Testing
Gaps
: 14/05 Task 3 moved, API key late
Check Answer
Spots
1Task 4: Build login screen
2Note: Late, API down

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

The 'Horned Lizard' badge — Bug Squasher, 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. Which is a proper annotation on a project plan?
A. 12 May: Testing moved back 3 days because the login bug took longer to fix. ✓
B. Testing is late.
A good annotation includes a date and the reason for the change. 'Testing is late' gives neither.
2. What is the main purpose of an annotation on a project plan?
A. To replace the Gantt chart with a list of tasks
B. To explain a change or describe how far a task has progressed ✓
Annotations are short notes added to the plan. They explain what happened and why, and they do not replace the plan.
3. Which detail makes an annotation easier to use later when reviewing the plan?
A. The date the note was written ✓
B. The name of the font used on the chart
The date shows when the change or progress update happened, so it can be compared with the timeline.
4. A task was extended by two days because a team member was sick. Which part of the annotation is this?
A. The reason for the change ✓
B. The explanation of progress
Sickness explains why the task was changed. A progress explanation would say how much of the task is done.
5. Which annotation explains the progress of a task?
A. 20 June: GUI design deleted from the plan.
B. 20 June: GUI design 70% complete; the buttons and labels are finished, the menus are still to do. ✓
A progress annotation says how far the task has got and what remains. Deleting a task is a change, not a progress update.

Match the Pairs

12/08: Task 4 moved back 3 days - tester was sick → An annotation recording a change: it gives the date and the reason the task was rescheduled.
20/08: Testing 60% complete, on track → An annotation explaining the progress of a task: the date and how far the task has got.
A good annotation on a change includes the date and the reason for the change → 05/09: Design phase extended 2 days - client added new feature
An annotation can explain progress by stating the date and how much of a task is done → 18/09: Coding 80% done - login screen finished, reports left
Task 3 delayed → There is no date and no reason, so the note does not explain when or why the plan changed.
Went well - 25/07 → The note is vague: it does not say which task or how far it has progressed.

Key Term

annotation
A short dated note added to a project plan that explains a change, giving the date and the reason, or describes how far a task has progressed.

Fill in the Blanks

1. Annotation: 14/05 Task 3 moved, API key late
Hint: Type the word for a short dated note added to a project plan.
2. Date: 14/05/2025 Change: Testing moved to 21/05 Reason: Tester was ill
Hint: Type the label that records when the note was written.
3. Date: 14/05/2025 Change: Login screen added to scope Reason: Client requested extra feature
Hint: Type the label that explains why the change was made.
4. Date: 20/05/2025 Task: Build menu Progress: 60% done, buttons still to code
Hint: Type the label that describes how far the task has got.
5. Date: 02/06/2025 Change: Deadline moved from 10/06 to 17/06 Reason: Server access delayed
Hint: Type the label that states what was altered in the plan.

Spot the Error

Question 1
A Task 4: Build login screen
B Note: Late, API down
C Status: In progress
Line B — An annotation must include the date it was written. The note has a reason but no date, so nobody can tell when the change happened. It should be 'Note 12 May: Late, API down'.
Question 2
A Task 6: Write test cases
B Note 3 Jun: Task moved
C Status: Not started
Line B — An annotation that explains a change must give the reason for it. This note has a date and says the task moved, but not why. It should be 'Note 3 Jun: Moved, Sam is ill'.
Question 3
A Task 2: Code the menu
B Due: 8 Jun
C Note 5 Jun: Going well
Line C — An annotation about progress must explain how far the task has progressed. 'Going well' is vague. It should give a measurable detail such as '60% done, on time'.
Question 4
A Task 5: Fix save bug
B Due: 20 Jun
C Note 18 Jun: 2d late, hard bug
Line C — The annotation date does not match its content. 18 Jun is before the 20 Jun due date, so the task cannot be 2 days late. The date should be 22 Jun.
Question 5
A Note 31 Jun: Added, bug found
B Task 8: Retest the login form
C Status: Not started
Line A — The date in the annotation is not a real date, because June only has 30 days. A dated note must have a valid date, such as 9 Jun.

Student with a class code? Join your class →