GSOE9820 · Engineering Project Management
Project Scope and the Work Breakdown Structure
This is the spine of the course and the whole of the individual Task 1 (5%, CLO 2): a purpose statement under 30 words, a WBS to work-package level, and a scope statement under 100 words with constraints. The single most-tested judgement is whether a WBS decomposes by deliverables (nouns) covering 100% of scope, rather than by schedule phases — and the same scope discipline underpins the Task 2 PMP and the recall questions on the final quiz.
What this chapter covers
- 01The project inputs (Objectives, Deliverables, Requirements, Constraints) define the "what"; Scope answers the "how"
- 02Step 1 — Purpose statement (the WHY): the goal + strategic reason, under 30 words
- 03Step 2 — Scope statement (the WHAT): deliverables + related work + boundaries, constraints mandatory, under 100 words
- 04Step 3 — Work Breakdown Structure: deliverable-oriented decomposition to work-package level
- 05The 100% rule: child elements sum to exactly the parent — no more, no less
- 06WBS elements are nouns (deliverables); only Activities under a work package are verbs
- 07Deliverable-oriented vs process/schedule-oriented WBS — the right-vs-wrong judgement
- 08WBS hierarchy: Project → Deliverable → Subdeliverable → Work Package (→ Activities); control/cost accounts
Judge two candidate WBSs: deliverable-oriented vs process-oriented
- +1State the test. A WBS must decompose by deliverables (nouns) and cover 100% of scope — the "what" — not by schedule phases (the "how/when"). Apply the four checks: covers 100%? shows deliverable→sub-deliverable relationship? clearly the "what" not the process? not a schedule?
- +1Assess WBS-2. Its Level-2 boxes — Design, Procurement, Installation, Testing, Handover — are process phases in schedule order (verbs/stages), so it is really a schedule, not a deliverable decomposition. It fails the "what, not process" and "not a schedule" checks.
- +1Assess WBS-1. Its Level-2 boxes — Charging Hardware, Software & Payments, Civil & Electrical Works, Commissioning & Training, plus Project Management — are deliverables (nouns) that partition the scope into components and, taken together, cover 100% of the work. It passes all four checks.
- +1Verdict and fix. Choose WBS-1. To take it to work-package level, decompose each deliverable further (e.g. 1.2 Charging Hardware → 1.2.1 Chargers, 1.2.2 Mounting & Enclosures, 1.2.3 Metering), keeping every node a noun and each branch at least three levels deep, and confirm the children still sum to 100% of the parent.
Key terms
- Scope
- The solution to the problem the project frames — it answers the "how", given the objectives, deliverables, requirements and constraints that define the "what". Formulating scope is the principal creative effort of the project and requires domain knowledge (CLO 2).
- Purpose statement
- A short statement (under 30 words in Task 1) of the goal and the organisational strategy the deliverables serve — the WHY. A strong purpose states the benefit and its strategic link, not just the technical output.
- Scope statement
- A statement (under 100 words in Task 1) of the end result and the work to deliver it, with clear boundaries and mandatory constraints (budget, deadline, exclusions) — the WHAT. It must be consistent with the purpose and the WBS.
- Work Breakdown Structure (WBS)
- A hierarchical, deliverable-oriented decomposition of the total scope (100%) down to work-package level. Every element is a noun; it defines the "what", not the schedule.
- 100% rule
- The WBS must capture all of the deliverables and only those — child elements sum to exactly 100% of their parent. Missing a required deliverable, or padding with redundant management branches, breaks the rule.
- Work package
- The lowest WBS element: identifiable, assignable work whose cost and schedule can be estimated and controlled. Below it, work is decomposed into Activities (verbs) for scheduling.
Project Scope and the Work Breakdown Structure FAQ
What exactly does Task 1 ask for?
Three artefacts for your chosen brief: a purpose statement under 30 words (the WHY, tied to strategy), a WBS diagram decomposed to work-package level, and a scope statement under 100 words that must include constraints (budget, deadline, boundaries). It is an individual submission worth 5% (CLO 2), and it is graded on whether the purpose conveys why, the WBS is built correctly (100% rule, nouns, not a schedule), and the scope names deliverables, related work and clear boundaries consistent with the WBS and purpose.
What is the single biggest WBS mistake?
Organising the WBS by schedule phases (Design → Build → Test → Handover) instead of by deliverables. That produces a timeline, not a deliverable decomposition, and fails the core test. Other common defects are using verbs where nouns belong, padding Project Management into a "plan to make a plan," over-splitting leaves that should be merged, and omitting a required deliverable (which breaks the 100% rule).
Why must the scope statement include constraints?
Because constraints (a budget cap, a deadline, standards, explicit exclusions) are what make scope bounded and measurable — without them the statement describes a deliverable but not a controllable project. The course rule is explicit: the scope statement must include constraints, and near-all of its text should be about scope rather than product attributes.
How do purpose, scope and WBS fit together?
They are one consistent set: the purpose says why (strategy), the scope statement says what and within what limits, and the WBS decomposes that scope into deliverables covering 100% of the work. If the WBS contains something not implied by the scope statement — or omits something the scope promises — they are inconsistent, which the rubric penalises.
Exam move
Drill the three-step scope process on fresh fictitious briefs until it is fast: a purpose under 30 words that states the benefit and its strategic link; a scope statement under 100 words that names deliverables, related work, boundaries and constraints; and a WBS decomposed to work-package level. Practise the right-vs-wrong WBS judgement most of all, because it is the course's most-tested skill — draft one deliverable-oriented and one process-oriented WBS for the same project and grade each against the four checks (100%? deliverable relationship? the "what"? not a schedule?). Make two rules automatic: every WBS element is a noun (only Activities are verbs), and children sum to exactly 100% of the parent. Keep a short catalogue of WBS defects (verbs, schedule phases, PM padding, over-specific leaves, omissions, flowchart connectors) for spot-the-error quiz items. When a WBS feels off, check whether its Level-2 boxes read like a timeline. Ask Sia to plant defects in a WBS and have you find and fix them.
Working through Project Scope and the Work Breakdown Structure in GSOE9820? Sia is AskSia’s AI Business and Economics tutor — ask any GSOE9820 Project Scope and the Work Breakdown Structure question and get a clear, step-by-step explanation grounded in how GSOE9820 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
