← VCE Data Analytics U4O1

Adjusting tasks in a project plan

Adding, removing, reordering or reassigning tasks when a project changes, and recording each change in the plan so the plan stays accurate and up to date.

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

Understanding Adjusting tasks in a project plan in VCE Data Analytics U4O1

What it does: The arrow shows the task was reassigned from Sam to Priya, so the plan records who is now responsible. Marking the status as Complete records progress in the plan, so the plan matches the real state of the project. When scope grows, a new task is added and the change is recorded so the plan stays accurate and up to date. Tasks that are no longer needed are removed and the removal is recorded. Leaving them in makes the plan misleading. Reordering tasks fixes dependencies. A task that relies on clean data cannot start until the cleaning is done. Reassigning responsibility keeps work moving. The new name must be recorded so everyone knows who is responsible.

Common mistakes: The code adds Test with append(), so the change log must say 'Added task: Test'. A log entry that says 'Removed' makes the plan record inaccurate. To remove a task from the plan you use remove(). append() adds another Survey task at the end, which contradicts the log entry. It should be tasks.remove("Survey").

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 Adjusting tasks in 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 client asks for an extra chart on the dashboard after the plan was approved. What should the project manager do with the plan?
Add a new task for the chart and record the change in the planBuild the chart without updating the plan
Matches
Task 5 moved before Task 3, but the plan still lists Task 3 first.
↓
The order of tasks changed but the plan was not updated, so it no longer shows the real sequence of work.
Applying
Meanings
Term
Adjusting tasks
Meaning
Adding, removing, reordering or reassigning tasks when a project changes, and recording each change in the plan so the plan stays accurate and up to date.
Practice
Change log
Testing
Gaps
"Test formulas" AFTER "Build charts"
Check Answer
Spots
2tasks.append("Test")
3log = ["Removed task: Test"]

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

The 'Star Fox' badge — Frozen Master, 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 client asks for an extra chart on the dashboard after the plan was approved. What should the project manager do with the plan?
A. Build the chart without updating the plan
B. Add a new task for the chart and record the change in the plan ✓
When scope grows, a new task is added and the change is recorded so the plan stays accurate and up to date.
2. The client decides they no longer need the pie chart. Which action keeps the plan accurate?
A. Remove the pie chart task and note why it was removed ✓
B. Leave the task in the plan and just ignore it
Tasks that are no longer needed are removed and the removal is recorded. Leaving them in makes the plan misleading.
3. Data cleaning is taking longer than expected, so the formulas cannot be built yet. What change to the plan is needed?
A. Keep the original order and start the formulas anyway
B. Change the order of tasks so dependent tasks start after cleaning is finished ✓
Reordering tasks fixes dependencies. A task that relies on clean data cannot start until the cleaning is done.
4. Sam is away sick for a week and was responsible for testing the formulas. What is the best adjustment?
A. Reassign the testing task to another team member and record it ✓
B. Leave Sam's name on the task and wait for the deadline to pass
Reassigning responsibility keeps work moving. The new name must be recorded so everyone knows who is responsible.
5. Which is the best way to mark a finished task in a project plan?
A. Update its status to complete, with the date it was finished ✓
B. Delete the task from the plan
Completed tasks stay in the plan marked as complete. Deleting them removes the record of progress.

Match the Pairs

Task 6: Test dashboard | ADDED 12 Mar → A new task was added to the plan because the project changed, and the date of the change was recorded.
Task 4: Survey users | REMOVED 15 Mar → A task that is no longer needed was taken out of the plan, and the removal was recorded.
When responsibility moves to another team member, the plan is updated to show the new owner and the change. → Task 3: Clean data | Owner: Sam -> Priya
When a task is finished, the plan is updated so everyone can see its status and the project stays up to date. → Task 2: Build charts | Status: Complete
Task 5 moved before Task 3, but the plan still lists Task 3 first. → The order of tasks changed but the plan was not updated, so it no longer shows the real sequence of work.
Task 7 was removed from the project, but it is still in the plan with no note. → The removal was not recorded in the plan, so the plan is out of date and misleads the team.

Key Term

Adjusting tasks
Adding, removing, reordering or reassigning tasks when a project changes, and recording each change in the plan so the plan stays accurate and up to date.

Fill in the Blanks

1. ADD "Test formulas" AFTER "Build charts" LOG "Task added: scope grew"
Hint: Type the command that puts a new task into the plan.
2. REMOVE "Survey staff" LOG "Task removed: no longer needed"
Hint: Type the command that deletes a task the project no longer needs.
3. MOVE "Test charts" BEFORE "Publish report" LOG "Order changed"
Hint: Type the keyword that sets where the task now sits relative to another task.
4. ASSIGN "Build charts" TO "Mia" LOG "Task reassigned to Mia"
Hint: Type the command that changes who is responsible for a task.
5. MARK "Clean data" AS COMPLETE LOG "Clean data finished"
Hint: Type the status word that shows a task has been finished.

Spot the Error

Question 1
A tasks = ["Plan", "Build"]
B tasks.append("Test")
C log = ["Removed task: Test"]
Line C — The code adds Test with append(), so the change log must say 'Added task: Test'. A log entry that says 'Removed' makes the plan record inaccurate.
Question 2
A tasks = ["Plan", "Survey", "Build"]
B tasks.append("Survey")
C log = ["Removed task: Survey"]
Line B — To remove a task from the plan you use remove(). append() adds another Survey task at the end, which contradicts the log entry. It should be tasks.remove("Survey").
Question 3
A tasks = ["Plan", "Build", "Test"]
B tasks.insert(3, "Survey")
C log = ["Survey placed at position 2"]
Line B — Index 1 is position 2 in the list, so Survey sits after Plan. Index 3 puts it at the end, so the plan and the log would not match. It should be tasks.insert(1, "Survey").
Question 4
A owner = {"Build" "Sam"}
B owner["Build"] = "Priya"
C log = ["Build reassigned to Priya"]
Line A — A dictionary needs a colon between each key and its value. The line should be owner = {"Build": "Sam"} so the task has an owner that can then be reassigned.
Question 5
A status = {"Plan": "In progress"}
B status["Plan"] == "Complete"
C log = ["Plan marked complete"]
Line B — A double equals sign compares values and does not change anything, so the task is never marked complete. Use a single = to assign: status["Plan"] = "Complete".

Student with a class code? Join your class →