Adjusting tasks in a project plan

Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.

Adjusting tasks in a project plan

Name:
Date:
Class:

Quick Questions

Shade in the A or B circle for each question.

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

Match the Pairs

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

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

Definitions

Adjusting tasks

Fill in the Blanks

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

1.
___ "Test formulas" AFTER "Build charts" LOG "Task added: scope grew"
2.
______ "Survey staff" LOG "Task removed: no longer needed"
3.
MOVE "Test charts" ______ "Publish report" LOG "Order changed"
4.
______ "Build charts" TO "Mia" LOG "Task reassigned to Mia"
5.
MARK "Clean data" AS ________ LOG "Clean data finished"

Spot the Error

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

Question 1
A tasks = ["Plan", "Build"]
B tasks.append("Test")
C log = ["Removed task: Test"]
Question 2
A tasks = ["Plan", "Survey", "Build"]
B tasks.append("Survey")
C log = ["Removed task: Survey"]
Question 3
A tasks = ["Plan", "Build", "Test"]
B tasks.insert(3, "Survey")
C log = ["Survey placed at position 2"]
Question 4
A owner = {"Build" "Sam"}
B owner["Build"] = "Priya"
C log = ["Build reassigned to Priya"]
Question 5
A status = {"Plan": "In progress"}
B status["Plan"] == "Complete"
C log = ["Plan marked complete"]

Answer Key

Adjusting tasks in a project plan
Section A: Quick Questions
Q1
B — Add a new task for the chart and record the change in the plan
Q2
A — Remove the pie chart task and note why it was removed
Q3
B — Change the order of tasks so dependent tasks start after cleaning is finished
Q4
A — Reassign the testing task to another team member and record it
Q5
A — Update its status to complete, with the date it was finished
Section B: Match the Pairs
Q1
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.
Q2
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.
Q3
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
Q4
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
Q5
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.
Q6
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.
Section C: Definitions
Q1
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.
Section D: Fill in the Blanks
Q1
ADD "Test formulas" AFTER "Build charts" LOG "Task added: scope grew"
Q2
REMOVE "Survey staff" LOG "Task removed: no longer needed"
Q3
MOVE "Test charts" BEFORE "Publish report" LOG "Order changed"
Q4
ASSIGN "Build charts" TO "Mia" LOG "Task reassigned to Mia"
Q5
MARK "Clean data" AS COMPLETE LOG "Clean data finished"
Section E: Spot the Error
Q1
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.
Q2
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").
Q3
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").
Q4
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.
Q5
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".