FIT5057 Chap.2 Scope Management
Scope Management
Scope Management converts stakeholder needs into requirements, deliverables, work packages and acceptance evidence. This chapter shows how a requirements traceability matrix, scope statement and work breakdown structure form one control system.
You will practise drawing exclusions, applying the one hundred percent rule, distinguishing clarification from scope change, and tracing an approved change into every affected baseline rather than updating one document in isolation. Requirements become useful when their source, owner, priority and acceptance condition are visible.
The scope statement then defines what is included and explicitly excluded, while the WBS decomposes approved deliverables into manageable work packages. A traceability matrix lets the project manager move in both directions: from a need to its test, or from a work package back to its reason for existing.
The chapter's original examples expose unsupported features, mixed activity and deliverable levels, and changes that are incorrectly labelled as clarifications. You will learn to evaluate schedule, cost, quality, resource and risk effects before seeking authority.
This approach supports assessed artefacts because the RTM, scope statement, WBS and later schedule should preserve the same boundary and identifiers rather than becoming separate templates. Bidirectional tracing makes silent boundary drift easier to detect.
What this chapter covers
- 01
Functional and non-functional requirements
- 02
Requirements sources, owners and priorities
- 03
Scope inclusions, exclusions and assumptions
- 04
Requirements traceability matrices
- 05
Work breakdown structures and work packages
- 06
Change requests and baseline control
Worked example · free
Repair a broken traceability chain
- +1Confirm that online payment has no approved requirement or acceptance criterion in the current baseline.
- +2Remove it from planned work or raise a change request that identifies value and all schedule, cost, quality and risk effects.
- +2If approved, update the requirement, RTM, scope statement, WBS, schedule and acceptance evidence together.
Key terms
- Requirement
- A capability or condition that the solution or project work must satisfy for an identified source.
- Scope Statement
- The approved description of deliverables, boundaries, exclusions, assumptions and constraints for the project.
- Work Package
- A manageable WBS component that can be estimated, assigned, scheduled and controlled.
- Acceptance Criterion
- An observable condition used to decide whether a requirement or deliverable has been met.
Scope Management FAQ
What does a requirements traceability matrix do?
It links each need or requirement to its source, owner, priority, deliverable and acceptance evidence. The links help the team detect missing work, unsupported features and the downstream effects of a proposed change.
How is a WBS different from a schedule?
A WBS decomposes approved deliverables into manageable work packages. A schedule derives activities from that work, estimates timing and sequences dependencies. The WBS answers what work exists; the schedule explains when and in what order it occurs.
When does a clarification become a scope change?
A clarification explains an existing approved requirement. A scope change adds, removes or alters a deliverable, boundary or acceptance condition. If the intended outcome changes, assess the effects and obtain authority before updating the baseline.
How do I check the one hundred percent rule?
Choose a WBS parent and ask whether its children together represent all approved work at that level without adding unrelated work. Repeat the test down each branch, then compare leaf work packages with the RTM and explicit exclusions.
Assessment move
Choose one fictional feature and trace it from stakeholder need to requirement, deliverable, WBS work package and acceptance criterion. Add an explicit exclusion, then test whether every WBS leaf has an approved reason to exist. Practise classifying requests as clarification, correction or change. For a true change, list the schedule, cost, quality, resource and risk effects before naming the decision owner.
This makes scope control an applied reasoning exercise rather than a vocabulary list. Create identifiers for three requirements and carry them into a small RTM. Attach one deliverable, one acceptance test and one WBS branch to each requirement, then deliberately add an unsupported work package and diagnose it.
Check the one hundred percent rule at each parent: children should fully represent the parent without importing work from outside the approved boundary. Write a brief WBS dictionary entry with owner, assumptions and completion rule so you can see what the diagram alone omits. For change control practice, introduce a stakeholder request after baselining and prepare a one-paragraph recommendation.
State the intended value, the affected traceability links, the consequences for schedule, cost, quality and risk, and the role with approval authority. After the decision, list every artefact that must change. End by sampling identifiers in both directions, from need to acceptance and from work package back to source. This catches drift before presentation polishing hides it.
Working through Scope Management in FIT5057? Sia is AskSia’s AI Project Management tutor — ask any FIT5057 Scope Management question and get a clear, step-by-step explanation grounded in how FIT5057 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.