← VCE Software Development U4O1

Adjusting tasks in a project plan

Changing a project plan's tasks by adding, removing, reordering or reassigning them when circumstances change, so the plan stays realistic and the project stays on track.

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

Understanding Adjusting tasks in a project plan in VCE Software Development U4O1

What it does: The task is deleted from the plan because circumstances changed and the feature is no longer required. Reordering changes the sequence of tasks so dependencies are respected and the project stays on track. When requirements change, add a task so the work is scheduled, resourced and tracked in the plan. The work is still needed, so it is reassigned. Deleting it would leave the project incomplete. Adding a fix task and reordering later work responds to the problem. Removing testing hides issues rather than solving them. Reassigning changes who is responsible for an existing task. Adding creates a brand new task.

Common mistakes: insert() takes the index first, then the new task. To add a Review task at position 1, write tasks.insert(1, "Review"). Round brackets make a tuple, and tuples cannot be changed, so remove() fails. A plan whose tasks may be cut should be a list: ["Plan", "Build", "Test"].

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 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
A client requests a new login feature halfway through development. What is the best adjustment to the project plan?
Leave the plan unchanged and fit it in somehowAdd a new task for the login feature to the plan
Matches
Team member leaves -> keep the plan unchanged and hope the tasks get done
↓
The plan was not adjusted. Tasks should be reassigned to other team members so the work still gets done.
Applying
Meanings
Term
adjusting tasks
Meaning
Changing a project plan's tasks by adding, removing, reordering or reassigning them when circumstances change, so the plan stays realistic and the project stays on track.
Practice
ADD "Fix login bug" TO plan
Testing
Gaps
plan.("Add login screen")
Check Answer
Spots
2tasks.append("Test")
3tasks.insert("Review", 1)

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 requests a new login feature halfway through development. What is the best adjustment to the project plan?
A. Leave the plan unchanged and fit it in somehow
B. Add a new task for the login feature to the plan ✓
When requirements change, add a task so the work is scheduled, resourced and tracked in the plan.
2. The team decides a planned animation feature is no longer needed. What should happen to its task?
A. Keep the task so the plan never changes
B. Remove the task from the plan ✓
Removing tasks that are no longer required keeps the plan realistic and frees time for other work.
3. A team member is away sick for two weeks and their database task is due soon. What is the best adjustment?
A. Reassign the task to another available team member ✓
B. Delete the task from the plan
The work is still needed, so it is reassigned. Deleting it would leave the project incomplete.
4. True or false: A project plan should never be changed once it has been approved.
A. False: tasks are adjusted when circumstances change ✓
B. True: changing a plan means the project has failed
Plans are living documents. Adjusting tasks keeps the project on track when circumstances change.
5. Testing finds a serious bug in the search function. Which adjustment is most suitable?
A. Add a task to fix the bug and reorder later tasks if needed ✓
B. Remove the testing task so the bug is not found again
Adding a fix task and reordering later work responds to the problem. Removing testing hides issues rather than solving them.

Match the Pairs

Add task: Write user guide (2 days, Sam) → A new task is added to the plan because a need was found that the original plan did not cover
Reassign task: Test login (Mia -> Jo) → An existing task is given to a different team member so the work can still be completed on time
Removing a task that is no longer needed keeps the plan realistic and frees up time and people → Remove task: Build reports page (client dropped feature)
Tasks can be reordered so a delayed task no longer holds up work that depends on it → Move task: Design database before Code login page
Team member leaves -> keep the plan unchanged and hope the tasks get done → The plan was not adjusted. Tasks should be reassigned to other team members so the work still gets done.
Scope grows by 3 features -> add the tasks but leave all deadlines as they are → Tasks were added without adjusting time frames or reassigning people, so the plan is no longer realistic.

Key Term

adjusting tasks
Changing a project plan's tasks by adding, removing, reordering or reassigning them when circumstances change, so the plan stays realistic and the project stays on track.

Fill in the Blanks

1. plan.append("Add login screen")
Hint: Type the list method that adds a new task to the end of the plan.
2. plan.remove("Write help page")
Hint: Type the list method that deletes a named task that is no longer needed.
3. owner = {"Test login": "Sam"} owner["Test login"] = "Mia"
Hint: Type the dictionary variable name used to reassign the task to a new person.
4. plan.insert(0, "Fix login bug")
Hint: Type the list method that places an urgent task at a chosen position, so the order changes.
5. if "Docs" in plan: plan.remove("Docs")
Hint: Type the keyword that checks the task exists in the plan before removing it.

Spot the Error

Question 1
A tasks = ["Design", "Code"]
B tasks.append("Test")
C tasks.insert("Review", 1)
D print(tasks)
Line C — insert() takes the index first, then the new task. To add a Review task at position 1, write tasks.insert(1, "Review").
Question 2
A tasks = ("Plan", "Build", "Test")
B tasks.remove("Build")
C print(tasks)
Line A — Round brackets make a tuple, and tuples cannot be changed, so remove() fails. A plan whose tasks may be cut should be a list: ["Plan", "Build", "Test"].
Question 3
A owners = {"Test": "Sam"}
B owners["Test"] == "Priya"
C print(owners["Test"])
Line B — == only compares values, so the task is never reassigned. Use a single = to assign: owners["Test"] = "Priya".
Question 4
A tasks = ["Plan", "Code", "Demo"]
B cut = tasks.pop("Demo")
C print("Cut:", cut)
D print(tasks)
Line B — pop() removes a task by its index, not by its name. Use tasks.pop(2) to remove Demo, or tasks.remove("Demo") to remove by value.
Question 5
A plan = {"Code": "Sam", "Test": "Sam"}
B for task in plan.items():
C if plan[task] == "Sam":
D plan[task] = "Ava"
Line B — items() gives (task, owner) pairs, so plan[task] would look up a tuple and fail. To reassign Sam's tasks, loop over the task names with: for task in plan:

Student with a class code? Join your class →