← VCE Data Analytics U4O1

Reviewing the number of changes made to a project plan

The number of changes made to a project plan, tallied from its annotations. Few changes suggest the plan matched the work well; many suggest it did not.

Part of: VCE Data Analytics - U4O1 - Development and Evaluation — Module 103

Understanding Reviewing the number of changes made to a project plan in VCE Data Analytics U4O1

What it does: Dividing the number of change notes by the number of tasks gives the share of the plan that changed. The formula compares the change count with a limit and returns Many or Few, a first judgement of how well the plan matched the work. Annotations record each change made and why, so you tally changes by counting the annotations. Few changes suggest the original plan was realistic and the tasks and time frames were estimated well. Grouping by type (tasks added, tasks removed, deadlines moved) shows which part of the plan was weakest. COUNTA counts non-empty cells, so each annotated change adds one to the total.

Common mistakes: The for loop that tallies each annotation is missing its colon. It should be 'for note in notes:'. The share of tasks that changed is found by dividing changes by tasks, not multiplying. It should be 'ratio = changes / tasks'.

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 Reviewing the number of changes made to a project plan to a class →

This module's key terms are also in a printable crossword (Modules 85–105) and word search (Modules 63–105).

Take this worksheet further — free with Cloodit

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

Learning
Duo
A student wants a first measure of how well their original plan matched the work. What should they count?
The number of changes made to the planThe number of pages in the final report
Matches
=COUNT(C2:C20)
↓
COUNT only counts numbers. The annotations are text, so the result is 0 and the change count is wrong. Use COUNTA.
Applying
Meanings
Term
change count
Meaning
The number of changes made to a project plan, tallied from its annotations. Few changes suggest the plan matched the work well; many suggest it did not.
Practice
changeCount ← 0
Testing
Gaps
=(B2:B20)
Check Answer
Spots
1changes = 0
2for note in notes

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

The 'Blobfish' badge — Pressure Handler, 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. A student wants a first measure of how well their original plan matched the work. What should they count?
A. The number of changes made to the plan ✓
B. The number of pages in the final report
The change count is a first measure of plan quality. It shows how often the plan had to be altered once the work began.
2. Where can you find the changes to tally in a project plan?
A. In the annotations added to the plan ✓
B. In the title of the plan
Annotations record each change made and why, so you tally changes by counting the annotations.
3. A plan ended up with only 2 changes over 8 weeks. What does this suggest?
A. The plan matched the work poorly
B. The plan matched the work well ✓
Few changes suggest the original plan was realistic and the tasks and time frames were estimated well.
4. A plan ended up with 15 changes over 8 weeks. What does this suggest?
A. The original plan did not match the work well ✓
B. The original plan was perfect
Many changes suggest that the tasks or time frames were not estimated well at the start.
5. Which is a good way to group changes when reviewing a plan?
A. By the colour of the annotation text
B. By type, such as task changes and time frame changes ✓
Grouping by type (tasks added, tasks removed, deadlines moved) shows which part of the plan was weakest.

Match the Pairs

=COUNTA(C2:C20) → Tallies the change notes recorded in the annotation column to give the change count
=COUNTIF(D2:D20,"Task") → Counts only the changes of type Task, grouping the changes by type
Show what share of the plan's tasks needed a change, to judge many vs few changes → =COUNTA(C2:C20)/COUNTA(A2:A20)
Label the plan as having many or few changes using a set limit → =IF(COUNTA(C2:C20)>5,"Many","Few")
=COUNT(C2:C20) → COUNT only counts numbers. The annotations are text, so the result is 0 and the change count is wrong. Use COUNTA.
=COUNTIF(D2:D20,Time frame) → The text criterion is missing quotation marks, so the formula errors. It should be "Time frame".

Key Term

change count
The number of changes made to a project plan, tallied from its annotations. Few changes suggest the plan matched the work well; many suggest it did not.

Fill in the Blanks

1. =COUNTA(B2:B20)
Hint: Type the function that counts non-empty cells, tallying the annotations in the change log column.
2. =COUNTIF(C2:C20,"Time")
Hint: Type the function that counts only the cells matching a condition, to tally one type of change.
3. changes = ["Task", "Time", "Task"] print(len(changes))
Hint: Type the built-in function that returns how many items are in a list, giving the change count.
4. =IF(D2>5,"Many","Few")
Hint: Type the function that picks one of two results depending on a test, to label the change count as many or few.
5. counts = {"Time": 3, "Task": 2} print(sum(counts.values()))
Hint: Type the built-in function that adds up numbers, to total the changes grouped by type.

Spot the Error

Question 1
A changes = 0
B for note in notes
C changes += 1
D print(changes)
Line B — The for loop that tallies each annotation is missing its colon. It should be 'for note in notes:'.
Question 2
A changes = 5
B tasks = 20
C ratio = changes * tasks
D print(ratio)
Line C — The share of tasks that changed is found by dividing changes by tasks, not multiplying. It should be 'ratio = changes / tasks'.
Question 3
A changes = 0
B for note in notes:
C changes += 1
D print("Total:", chages)
Line D — The variable name is misspelt, so Python cannot find it. It should print the tally variable 'changes'.
Question 4
A Changes = 0
B if changes < 3:
C print('Few changes')
D else:
E print('Many changes')
Line A — Python is case sensitive, so 'Changes' is a different name from 'changes' used on the next line. The tally should start as 'changes = 0'.
Question 5
A changes = 12
B if changes > 10:
C print('Plan was weak')
Line B — The comparison is the wrong way round for the message. Many changes (12 is more than 10) suggest a weak plan, and the program should check 'if changes > 10:'. Wait: the correct line is 'if changes > 10:', so the broken line checks the opposite.

Student with a class code? Join your class →