VCE Software Development U4O1 Word Scramble: Project plans, progress and effectiveness (Modules 186–198)
Name:
Date:
Class:
🔤
Word scramble
Unscramble the letters and write each key term on the line.
1
EOCSP PECER
The uncontrolled growth of a project's features beyond the original scope, which adds extra time and cost unless changes are controlled.
2
ELNORPESN SHAGNCE
When a team member leaves or is absent, their skills are lost and tasks must be reassigned, which can disrupt task allocation and delay the timeline of a project plan.
3
NHECICALT SSUSIE
Problems like bugs, tool failures or lost files that delay tasks and force changes to a project plan. Contingencies (backups, spare time) reduce their impact.
4
OERTPJC UALORNJ
A dated record of progress, decisions, problems, solutions and reasons for changes, written as development happens and kept as evidence for evaluation.
5
TGNUJISAD SASTK
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.
6
DSINGUTJA MITE EMFSRA
Changing a task's start date or duration when work takes longer or shorter than planned, then moving any dependent tasks and deadlines to match.
7
NANTNOTIAO
A short dated note added to a project plan that explains a change, giving the date and the reason, or describes how far a task has progressed.
8
EUNBRM FO GNAECSH
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.
9
ANSROE ROF GENHAC
The cause of a plan change, classed as scope creep, personnel, technical issues or poor estimates. Patterns in these causes show how effective the original plan was.
10
MITACP FO GHECANS
Judging how changes to a project plan affected completion, such as delays, dropped features and quality, and whether the project finished on time.
Answer Key
VCE Software Development U4O1 · Modules 186–198
1EOCSP PECER → scope creep — The uncontrolled growth of a project's features beyond the original scope, which adds extra time and cost unless changes are controlled.
2ELNORPESN SHAGNCE → personnel changes — When a team member leaves or is absent, their skills are lost and tasks must be reassigned, which can disrupt task allocation and delay the timeline of a project plan.
3NHECICALT SSUSIE → technical issues — Problems like bugs, tool failures or lost files that delay tasks and force changes to a project plan. Contingencies (backups, spare time) reduce their impact.
4OERTPJC UALORNJ → project journal — A dated record of progress, decisions, problems, solutions and reasons for changes, written as development happens and kept as evidence for evaluation.
5TGNUJISAD SASTK → 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.
6DSINGUTJA MITE EMFSRA → Adjusting time frames — Changing a task's start date or duration when work takes longer or shorter than planned, then moving any dependent tasks and deadlines to match.
7NANTNOTIAO → annotation — A short dated note added to a project plan that explains a change, giving the date and the reason, or describes how far a task has progressed.
8EUNBRM FO GNAECSH → 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.
9ANSROE ROF GENHAC → Reason for change — The cause of a plan change, classed as scope creep, personnel, technical issues or poor estimates. Patterns in these causes show how effective the original plan was.
10MITACP FO GHECANS → 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.