Assessing project plan effectiveness: impact of changes

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. A team added a new feature mid-project, which pushed the final delivery back two weeks. How should this be recorded when assessing the plan?

A As a change with no impact on the project

B As a change that caused a delay to completion

2. Which statement best describes judging the impact of changes on a project plan?

A Counting how many lines of code were written

B Judging how changes affected completion, including delays, dropped features and quality

3. A project was due on 30 September and was handed over on 30 September, even though two tasks were rescheduled. What is the impact on completion?

A Completed on time, so the changes had little negative impact

B Completed late, so the changes failed

4. Because of a technical issue, the team removed the search feature from the final solution. How is this impact described?

A A dropped feature that reduces how much of the solution was delivered

B A delay that has no effect on the features delivered

5. Which result suggests the changes had a LARGE negative impact on the plan?

A The project finished three weeks late with two features dropped

B The project finished on time with all features working

Match the Pairs

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

Left column		Right column
1Planned finish: 12 Sep \| Actual finish: 26 Sep		AThe project finished 14 days late, so a change caused a delay and the plan did not achieve completion on time.
2Features planned: 8 \| Features delivered: 6		BThe delay was ignored. Finishing late is an impact of changes and means the project was not completed on time.
3To judge the impact of a delay, subtract the planned finish date from the actual finish date to get the days late.		Cdays_late = actual_finish - planned_finish
4To judge the impact of dropped features, work out the percentage of planned features that were delivered.		Dcompletion = delivered / planned * 100
5Finished 2 weeks late, but all tasks were done, so the changes had no impact.		EQuality was ignored. Cutting testing to meet the deadline may have lowered the quality of the solution.
6Finished on time after cutting testing, so the changes only had a good impact.		FTwo features were dropped, so the solution is less complete than planned.

Definitions

impact of changes

Fill in the Blanks

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

delay = actual _ planned

late = actual _ planned

__ delay > 0: print("Project was late")

planned = ["login", "search", "reports"] done = ["login", "search"] dropped = ___(planned) - len(done)

status = "Late" if delay > 0 ____ "On time"

Spot the Error

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

Question 1

A planned = 30

B actual = 38

C delay = planned - actual

D print("Delay:", delay)

Question 2

A planned = 10

B dropped = "3"

C built = planned - dropped

D print(built, "features built")

Question 3

A planned = 20

B built = 15

C pct = planned / built * 100

D print(pct, "% complete")

Question 4

A planned = 40

B actual = 52

C delay = actual - planned

D if delay > 0

E print("Finished late")

Question 5

A dropped = 2

B if dropped = 0:

C print("Scope reduced")

D else:

E print("Full scope")

Answer Key

Assessing project plan effectiveness: impact of changes

Section A: Quick Questions

B — As a change that caused a delay to completion

B — Judging how changes affected completion, including delays, dropped features and quality

A — Completed on time, so the changes had little negative impact

A — A dropped feature that reduces how much of the solution was delivered

A — The project finished three weeks late with two features dropped

Section B: Match the Pairs

Planned finish: 12 Sep | Actual finish: 26 Sep → The project finished 14 days late, so a change caused a delay and the plan did not achieve completion on time.

Features planned: 8 | Features delivered: 6 → Two features were dropped, so the solution is less complete than planned.

To judge the impact of a delay, subtract the planned finish date from the actual finish date to get the days late. → days_late = actual_finish - planned_finish

To judge the impact of dropped features, work out the percentage of planned features that were delivered. → completion = delivered / planned * 100

Finished 2 weeks late, but all tasks were done, so the changes had no impact. → The delay was ignored. Finishing late is an impact of changes and means the project was not completed on time.

Finished on time after cutting testing, so the changes only had a good impact. → Quality was ignored. Cutting testing to meet the deadline may have lowered the quality of the solution.

Section C: Definitions

impact of changes — Judging how changes to a project plan affected completion, such as delays, dropped features and quality, and whether the project finished on time.

Section D: Fill in the Blanks

delay = actual - planned

late = actual > planned

if delay > 0:
    print("Project was late")

planned = ["login", "search", "reports"]
done = ["login", "search"]
dropped = len(planned) - len(done)

status = "Late" if delay > 0 else "On time"

Section E: Spot the Error

C — The subtraction is the wrong way round, so a late project gives a negative delay. It should be delay = actual - planned.

B — The number of dropped features is stored as a string, so planned - dropped causes a TypeError. It should be dropped = 3.

C — Completion is the features built divided by the features planned. The division is inverted, so the percentage is wrong. It should be built / planned * 100.

D — An if statement must end with a colon. It should be if delay > 0:.

B — A single = assigns a value. A condition needs a comparison operator. To detect dropped features it should be if dropped > 0:.