INFO6007 Chap.3 Scope Management: Boundaries, WBS and Control
Scope Management: Boundaries, WBS and Control
This chapter converts objectives into deliverables, inclusions, exclusions, assumptions and measurable acceptance criteria. A deliverable oriented Work Breakdown Structure defines the total scope and supports estimation, ownership and control. Validation accepts completed deliverables, while change control prevents additional work from entering the baseline without an authorised decision about consequences.
Product scope describes the features and functions of the solution, while project scope includes all work needed to deliver, transition and close it. The WBS decomposes that work until packages can be estimated and assigned, and the dictionary carries detail that a diagram cannot. Traceability shows which stakeholder need, requirement, deliverable and test belong together.
This exposes orphan requirements and outputs with no stated value. Validation asks an authorised stakeholder to accept completed work against evidence. Control defines a requested change, assesses effects across schedule, cost, resources, risk, quality, procurement and operations, and records whether it is approved, rejected, exchanged or deferred. Controlled change is not scope creep; work entering without that route is.
What this chapter covers
- 01
Scope management approach
- 02
Scope statement and exclusions
- 03
Acceptance criteria
- 04
Deliverable decomposition
- 05
WBS dictionary
- 06
Scope validation
- 07
Change requests and scope creep
- 08
Decompose the total project boundary into complete non-overlapping deliverables that satisfy the one hundred percent rule
- 09
Stop decomposition where a work package can be estimated, owned, scheduled and verified without prescribing needless implementation detail
- 10
Trace each requirement to its source, objective, deliverable and acceptance evidence so proposed changes expose downstream impact
- 11
Distinguish formal validation of completed deliverables from ongoing control of the authorised scope baseline
- 12
Evaluate benefit, effort, schedule, quality, risk and operational effects before an authorised body decides a change request
- 13
Record exclusions and assumptions explicitly so stakeholders cannot silently redefine the approved project boundary
Worked example · free
Assess a predictive analytics request
- +1Record the requested output and reason.
- +1Define acceptance and data needs.
- +1Assess schedule, cost, privacy, quality and resource effects.
- +1Present add, swap or defer options to authority.
- +1Update every affected baseline only after approval.
Key terms
- Scope statement
- The detailed description of deliverables, boundaries, assumptions and acceptance conditions.
- WBS dictionary
- Supporting detail for WBS components, including descriptions, owners, assumptions and acceptance information.
- Scope creep
- Uncontrolled expansion of project scope without corresponding approval and baseline updates.
Scope Management: Boundaries, WBS and Control FAQ
What makes a good WBS?
It is deliverable oriented, complete against the approved scope, decomposed to manageable work packages and supported by a dictionary. Each unit appears once and children fully represent the parent.
Is every scope change scope creep?
No. A formally assessed, authorised and rebaselined change is controlled scope management. Scope creep is expansion that enters work without transparent impact analysis and approval evidence.
What is the difference between validation and control?
Validation obtains formal acceptance of completed deliverables. Control monitors the approved baseline, evaluates proposed changes and maintains consistency when an authorised decision alters the scope baseline.
Exam move
Study scope as a boundary and evidence system. Begin with a one paragraph scope statement for an original IT project. State the product, major deliverables, inclusions, exclusions, assumptions, constraints and acceptance approach. Rewrite vague exclusions until they prevent a realistic misunderstanding. Next transform the statement into a deliverable oriented Work Breakdown Structure.
Each parent should be fully represented by its children, each item should appear only once, and decomposition should continue until a work package can be estimated, assigned and controlled. Keep activities such as meeting or coding out of a deliverable hierarchy unless the project deliberately defines an activity based structure.
Add a WBS dictionary entry for several work packages with description, owner, assumptions, dependencies and acceptance. Then create a small traceability view linking stakeholder needs to requirements, deliverables and tests. Use it to find one orphan requirement and one deliverable with no stated need. Practise validation separately from control. Validation reviews completed deliverables and obtains formal acceptance.
Control monitors the baseline and routes proposed changes through definition, impact analysis and authority. For every request, ask what output is being added or modified, what acceptance evidence proves it, and how schedule, cost, resources, quality, risk, procurement, benefits and operations change. Present options such as add with more time and money, swap lower value scope or defer to another release.
Do not call every change scope creep. An assessed, authorised and rebaselined change is controlled management; scope creep is work entering without that decision. Strengthen acceptance criteria by writing measurable results rather than activities. Conduct user testing describes work, while a stated user group completing a defined journey within a threshold describes evidence.
On the notes sheet, keep the parent child completeness rule, the one place rule, the validation versus control distinction and the change impact checklist. In a case answer, draw a clear line from boundary to deliverable to acceptance and then to the authority that may alter it.
Working through Scope Management: Boundaries, WBS and Control in INFO6007? Sia is AskSia’s AI Project Management tutor — ask any INFO6007 Scope Management: Boundaries, WBS and Control question and get a clear, step-by-step explanation grounded in how INFO6007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.