18.1 Defining Scope and Breakdown Structures
Key Takeaways
- Scope is defined in terms of outputs, outcomes, and benefits — not only the list of things the project will build.
- A product breakdown structure decomposes what will be delivered; a work breakdown structure decomposes the work to deliver it.
- A cost breakdown structure aligns cost to the same decomposition, which is what makes cost and progress comparable.
- Schedules built from a breakdown structure are far less likely to omit work than schedules written as a flat task list.
- A consistent coding structure across PBS, WBS and CBS is what allows scope, schedule, and cost to be reported against each other.
Schedule management starts with clear scope
Schedule management on the APM PMQ (learning objective 20) is not only drawing bars on a Gantt chart. It begins with defining what is to be delivered and why, decomposing that definition into manageable structures, and understanding dependencies — including links with business-as-usual (BAU) — so that time estimates and network logic are meaningful.
This section covers scope as outputs, outcomes and benefits, product, work and cost breakdown structures (PBS, WBS, CBS), and links/dependencies among activities and with BAU, plus how cost, quality, risk and scope affect the schedule.
Outputs, outcomes and benefits in scope definition
Scope definition should connect temporary project work to lasting value. Reuse the high-yield distinction from benefits management:
| Term | Meaning | Schedule relevance |
|---|---|---|
| Output | A deliverable/product the project creates (system, building, process, trained cohort) | Primary objects of PBS and acceptance; scheduled build/test/handover |
| Outcome | Change in behaviour, state, or capability when outputs are used | Often needs adoption, training, dual-run — scheduled transition work |
| Benefit | Measurable value improvement from outcomes | Realisation may continue after project; schedule must enable measurement and adoption |
If scope is written only as a task list ("install servers," "write docs"), the team can be busy without producing the products and enabling the outcomes the business case needs. Define products and acceptance criteria first, then the work and costs to create them.
Scope statement essentials
A usable scope definition typically includes:
- In-scope products and services
- Out-of-scope exclusions (to prevent assumption creep)
- Acceptance criteria and quality standards for key outputs
- Constraints and assumptions affecting delivery
- Interfaces with other projects, suppliers, and BAU
- High-level outcomes/benefits the outputs are meant to enable (traceability)
Example: Scope is not only "deliver a CRM." It is "deliver a configured CRM (output) that enables sales staff to log all opportunities within 24 hours (outcome) supporting a 10% reduction in forecast error (benefit), with exclusions for marketing automation until phase 2."
Breakdown structures: PBS, WBS, CBS
Breakdown structures turn large, ambiguous scope into hierarchical, manageable elements for planning, estimating, assignment, and control.
Product Breakdown Structure (PBS)
A PBS decomposes the products/deliverables of the project — what will exist when work is complete. Top level may be the overall product; lower levels break into components, documents, and configuration items as needed.
| PBS focus | Examples |
|---|---|
| Physical products | Building wings, equipment assemblies, hardware kits |
| System products | Application modules, data migrations, interfaces |
| Management products | Business case, PMP, test reports, training packs, handover packs |
PBS answers: What products are we creating?
Work Breakdown Structure (WBS)
A WBS decomposes the work required to deliver the products — work packages and activities that can be estimated, scheduled, resourced, and assigned. Good WBS elements are manageable, measurable, and owned.
WBS answers: What work must we do to create those products?
Cost Breakdown Structure (CBS)
A CBS structures costs (and often budgets/codes) so money can be estimated, approved, and controlled against meaningful categories — often aligned to WBS elements, PBS products, organisational cost codes, or a combination.
CBS answers: How do we organise and control the money associated with the work/products?
Relationships among PBS, WBS, and CBS
| Structure | Primary question | Relates to others by… |
|---|---|---|
| PBS | What products? | WBS work creates PBS products; costs in CBS fund that creation |
| WBS | What work? | Work packages map to products; activities feed the schedule network |
| CBS | What costs/codes? | Cost accounts map to WBS (and sometimes PBS) for earned value and budget control |
Integration rule: every significant scheduled activity should sit in the WBS and map to products in the PBS and cost accounts in the CBS. Orphan activities (scheduled but not in scope structures) and orphan products (in PBS but with no work or budget) are red flags.
Benefits / outcomes (value)
↑ enabled by
Outputs / products ←—— PBS
↑ created by
Work packages / activities ←—— WBS → Schedule network
↑ funded/controlled by
Cost accounts / budget ←—— CBS
Scenario A — misaligned structures
A programme PBS includes "data migration" as a major product, but the WBS only has development sprints and the CBS has no migration cost code. Vendors later claim migration was "assumed free." Correct practice: place migration products in the PBS, migration work packages in the WBS (extract, cleanse, trial loads, reconciliation), migration costs in the CBS, and migration activities on the schedule with test dependencies.
Building the schedule from scope structures
Once products and work are decomposed:
- Define activities from WBS work packages at the level needed for control.
- Estimate durations (and resource needs) using appropriate techniques.
- Identify dependencies and constraints.
- Build the network and identify the critical path (conceptual level below).
- Check against calendars, resource availability, and BAU windows.
- Reconcile with cost and risk (contingency, response activities, quality gates).
Which statement best describes the relationship between PBS, WBS, and CBS?