INFO6007 Chap.3 Scope Management: WBS, RTM and Scope Creep
Scope Management: WBS, RTM and Scope Creep
Scope management connects requirements, a defined boundary, WBS decomposition, formal acceptance and governed change. The RTM preserves the line from stakeholder need to verification. This chapter develops Six scope processes, Scope management plan, Collect requirements, Requirements traceability matrix, Define scope, Work breakdown structure, Validate Scope, Control Scope, Scope creep.
Each idea is framed as a management decision: what evidence is needed, who owns the decision, which baseline or service outcome changes, and how the result is communicated.
Give every requirement an origin, rationale, deliverable, owner, verification method and status; decompose deliverables until they can be estimated and controlled. The method is deliberately connective.
Scope choices affect dependencies and estimates; resource choices affect schedule and cost; governance choices affect escalation and benefit ownership; service choices affect operating value. A strong answer names those links rather than reproducing an isolated framework.
Validation is acceptance, control is baseline monitoring and change, and activities should not replace deliverables in a deliverable-oriented WBS.
The chapter uses direction checks, boundary cases and original scenarios to make those errors visible. Where a supplied figure is reproduced third-party material, the guide rebuilds it on new dimensions.
Where an answer is independently computed from a published table, it is labelled AskSia-authored rather than attributed to the University.
For assessment, start with a one-sentence definition, apply it to the stated facts, explain the consequence for objectives or constraints, and finish with the controlled action. Quantitative work must show the formula, substituted values, result, direction and management meaning.
Qualitative work must identify the decision owner and the evidence that would change the recommendation.
Study this chapter through retrieval. Rebuild the central artefact from a blank page, test it against a changed assumption, then check it against one neighbouring plan or practice.
That routine prepares for explanations, comparisons, scenarios and calculations without inventing a past-paper format or per-question mark scheme.
What this chapter covers
- 01
Six scope processes
- 02
Scope management plan
- 03
Collect requirements
- 04
Requirements traceability matrix
- 05
Define scope
- 06
Work breakdown structure
- 07
Validate Scope
- 08
Control Scope
- 09
Scope creep
Free worked application: Scope Management: WBS, RTM and Scope Creep
- FrameIdentify the objective, decision owner and evidence available at the decision point.
- MethodApply the chapter rule and keep assumptions, units and direction words explicit.
- IntegrateTrace effects into at least one connected plan, baseline, stakeholder or service outcome.
- ActState the recommendation and the change, control or communication action that follows.
- VerifyCheck the result against the chapter trap and explain why the conclusion is reproducible.
Key terms
- Six scope processes
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Scope management plan
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Collect requirements
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Requirements traceability matrix
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Define scope
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Work breakdown structure
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
Scope Management: WBS, RTM and Scope Creep FAQ
What is the difference between Validate Scope and Control Scope?
Validate Scope obtains formal acceptance of completed deliverables. Control Scope monitors status and processes proposed changes to the scope baseline.
What is the main decision rule for Scope Management: WBS, RTM and Scope Creep?
Give every requirement an origin, rationale, deliverable, owner, verification method and status; decompose deliverables until they can be estimated and controlled.
What is the most common trap in Scope Management: WBS, RTM and Scope Creep?
Validation is acceptance, control is baseline monitoring and change, and activities should not replace deliverables in a deliverable-oriented WBS.
How should I structure a written answer on Scope Management: WBS, RTM and Scope Creep?
Define the concept, apply it to specific facts, explain the effect on an objective or constraint, identify the decision owner, and state the next controlled action.
Are the worked scenarios for Scope Management: WBS, RTM and Scope Creep official answers?
No. They are AskSia-authored learning examples derived independently from the concepts and stated inputs. They are not official questions, marking schemes or university solutions.
Exam move
Begin with the chapter map: Six scope processes, Scope management plan, Collect requirements, Requirements traceability matrix, Define scope, Work breakdown structure, Validate Scope, Control Scope, Scope creep. Write the purpose of each item in your own words and connect it to a decision, an artefact and an owner. Then rebuild the worked application without looking at the answer.
Use this governing rule: Give every requirement an origin, rationale, deliverable, owner, verification method and status; decompose deliverables until they can be estimated and controlled. Create two variations by changing one assumption, dependency, rating, probability, duration or stakeholder priority. Explain what changes and what remains stable.
Keep an error ledger headed direction, boundary, authority, precision and integration. The chapter's highest-risk mistake is: Validation is acceptance, control is baseline monitoring and change, and activities should not replace deliverables in a deliverable-oriented WBS.
For quantitative work, write symbols and units before arithmetic, keep intermediate precision visible and translate the result into under/over, ahead/behind, faster/cheaper or selected/not selected as appropriate. For qualitative work, write claim, scenario evidence, causal reasoning and controlled action. Finish by checking one neighbouring plan or practice.
Review operational assessment details on Canvas; this learning chapter does not invent dates, a viva rubric, past-paper questions or a per-question university mark scheme.
Working through Scope Management: WBS, RTM and Scope Creep in INFO6007? Sia is AskSia’s AI Project Management tutor — ask any INFO6007 Scope Management: WBS, RTM and Scope Creep 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.
