Assessing project plan effectiveness: number of changes

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. A Gantt chart had 20 tasks and needed only 2 changes during the project. What does this suggest about the plan?

A It was likely ineffective because it was changed at all

B It was likely effective because few changes were needed

2. Which is the first step when using the number of changes to assess a plan's effectiveness?

A Count the changes made during the project

B Count the number of team members

3. Plan A: 4 changes in a 40-task plan. Plan B: 4 changes in a 8-task plan. Which plan was likely more effective?

A Plan A, because 4 changes is a small share of 40 tasks

B Plan B, because the plans had the same number of changes

4. Why compare the number of changes with the total number of tasks in the plan?

A It shows how fast the programmer types code

B It shows how big the changes were relative to the plan's size

5. A project had 10 tasks and 8 changes were made. What is the best conclusion?

A The plan was probably not very effective as it needed many changes

B The plan was very effective as it was updated often

Match the Pairs

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

Left column		Right column
1changes = 3		ACounts how many changes were made to the plan during the project
2change_rate = changes / total_tasks		BThe count of changes must be compared with the size of the plan. 10 changes in a 100-task plan is a lower rate than 3 changes in a 5-task plan.
3A plan with only a few changes compared with its size was likely more effective		Cif change_rate < 0.2: print("Plan was effective")
4Count each change made to the plan during the project		DCompares the number of changes with the size of the plan
5A plan with 10 changes is always less effective than a plan with 3 changes, whatever its size.		Echanges = changes + 1
6A plan with many changes was likely more effective because the team adapted.		FMany changes usually suggest the original plan was less effective, because it needed a lot of fixing. Few changes suggests a more effective plan.

Definitions

number of changes

Fill in the Blanks

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

log = ["moved task 4", "new task"] changes = ___(log)

total = 20 changes = 5 ratio = changes _ total

log = [] log.______("moved task 4")

total = 20 changes = 5 percent = changes / total * ___

if changes _ 3: print("Likely an effective plan")

Spot the Error

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

Question 1

A changes = ["add", "drop"]

B n_changes = changes.len()

C n_tasks = 20

D ratio = n_changes / n_tasks

E print(ratio)

Question 2

A n_changes = 3

B n_tasks = 24

C ratio = n_changes / n_tasks

D print("Ratio: {ratio}")

Question 3

A tasks = [True, False, True]

B changes = 0

C for changed in tasks

D if changed:

E changes += 1

Question 4

A n_changes = "2"

B n_tasks = 40

C if n_changes / n_tasks < 0.1:

D print("Few changes")

Question 5

A changes_log = ["add", "move"]

B n_changes = len(changes_log)

C if n_changes >= 3:

D print("Effective plan")

Answer Key

Assessing project plan effectiveness: number of changes

Section A: Quick Questions

B — It was likely effective because few changes were needed

A — Count the changes made during the project

A — Plan A, because 4 changes is a small share of 40 tasks

B — It shows how big the changes were relative to the plan's size

A — The plan was probably not very effective as it needed many changes

Section B: Match the Pairs

changes = 3 → Counts how many changes were made to the plan during the project

change_rate = changes / total_tasks → Compares the number of changes with the size of the plan

A plan with only a few changes compared with its size was likely more effective → if change_rate < 0.2: print("Plan was effective")

Count each change made to the plan during the project → changes = changes + 1

A plan with 10 changes is always less effective than a plan with 3 changes, whatever its size. → The count of changes must be compared with the size of the plan. 10 changes in a 100-task plan is a lower rate than 3 changes in a 5-task plan.

A plan with many changes was likely more effective because the team adapted. → Many changes usually suggest the original plan was less effective, because it needed a lot of fixing. Few changes suggests a more effective plan.

Section C: Definitions

number of changes — A plan that needed few changes was likely more effective. Count the changes made during the project and compare that count with the size of the plan, such as its total tasks.

Section D: Fill in the Blanks

log = ["moved task 4", "new task"]
changes = len(log)

total = 20
changes = 5
ratio = changes / total

log = []
log.append("moved task 4")

total = 20
changes = 5
percent = changes / total * 100

if changes < 3:
    print("Likely an effective plan")

Section E: Spot the Error

B — len() is a built-in function, not a list method. To count the changes made during the project, write len(changes).

D — Without the f prefix, Python prints the text {ratio} literally instead of the change ratio. It should be print(f"Ratio: {ratio}").

C — A for loop header must end with a colon. Without it the program has a syntax error and cannot count the changed tasks.

A — The count is stored as a string, so dividing it by n_tasks causes a TypeError. The number of changes should be the integer 2.

C — The logic is reversed. A plan with few changes is likely more effective, so the test should be n_changes <= 3, not >= 3.