Annotating a project plan

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

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.

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

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

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

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.

Match the Pairs

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

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

Definitions

annotation

Fill in the Blanks

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

__________: 14/05 Task 3 moved, API key late

____: 14/05/2025 Change: Testing moved to 21/05 Reason: Tester was ill

Date: 14/05/2025 Change: Login screen added to scope ______: Client requested extra feature

Date: 20/05/2025 Task: Build menu ________: 60% done, buttons still to code

Date: 02/06/2025 ______: Deadline moved from 10/06 to 17/06 Reason: Server access delayed

Spot the Error

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

Question 1

A Task 4: Build login screen

B Note: Late, API down

C Status: In progress

Question 2

A Task 6: Write test cases

B Note 3 Jun: Task moved

C Status: Not started

Question 3

A Task 2: Code the menu

B Due: 8 Jun

C Note 5 Jun: Going well

Question 4

A Task 5: Fix save bug

B Due: 20 Jun

C Note 18 Jun: 2d late, hard bug

Question 5

A Note 31 Jun: Added, bug found

B Task 8: Retest the login form

C Status: Not started

Answer Key

Annotating a project plan

Section A: Quick Questions

A — 12 May: Testing moved back 3 days because the login bug took longer to fix.

B — To explain a change or describe how far a task has progressed

A — The date the note was written

A — The reason for the change

B — 20 June: GUI design 70% complete; the buttons and labels are finished, the menus are still to do.

Section B: 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.

Section C: Definitions

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.

Section D: Fill in the Blanks

Annotation: 14/05 Task 3 moved, API key late

Date: 14/05/2025
Change: Testing moved to 21/05
Reason: Tester was ill

Date: 14/05/2025
Change: Login screen added to scope
Reason: Client requested extra feature

Date: 20/05/2025
Task: Build menu
Progress: 60% done, buttons still to code

Date: 02/06/2025
Change: Deadline moved from 10/06 to 17/06
Reason: Server access delayed

Section E: Spot the Error

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'.

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'.

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'.

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.

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.