Project Scope Statement and Work Breakdown Structure (WBS): How to Build Both

Requirements describe what users need. Scope defines what the project will actually deliver in response. Two documents turn requirements into a manageable definition of the work: the project scope statement and the work breakdown structure (WBS). Together with the WBS dictionary, they form the scope baseline, against which all later change is judged.

Product Scope vs Project Scope

Product scope covers the features and functions of the thing being built (what the portal does). Project scope covers the work needed to deliver it (analysis, design, build, test, migration, training and project management). Both matter: forgetting project scope, such as data migration or user training, is a classic cause of overruns.

The Project Scope Statement

The scope statement describes in detail the deliverables and the work required to create them. It typically contains:

  • Product scope description: the characteristics of the deliverables.
  • Deliverables: every output, such as software modules, documents, trained users and reports.
  • Acceptance criteria: conditions for the customer to accept each deliverable.
  • Exclusions: what is explicitly out of scope.
  • Constraints: fixed limits such as deadlines, technology choices or budget caps.
  • Assumptions: conditions believed true, which carry risk if wrong.

It refines the high-level scope in the project charter using the detail from requirements gathering.

What Is a WBS?

A work breakdown structure is a hierarchical decomposition of the total work into smaller, more manageable components. It is organised by deliverables, not by activities or time. The lowest level is a work package, a piece of work small enough to estimate, assign and track reliably.

The 100% Rule

The WBS must include 100 per cent of the work defined in the scope, including project management work, and not a bit more. Each level must add up to the level above. If the parent says “Customer Portal”, the children together must cover everything needed to deliver the portal. Anything not in the WBS is not part of the project, which makes it a powerful defence against scope creep.

Example WBS: Customer Support Portal

WBS codeElementLevel
1Customer Support PortalProject
1.1Project managementDeliverable group
1.1.1Plans and baselinesWork package
1.1.2Status reporting and governanceWork package
1.2Requirements and designDeliverable group
1.2.1Approved requirements documentWork package
1.2.2Architecture and UI designWork package
1.3Portal buildDeliverable group
1.3.1Ticket logging and tracking moduleWork package
1.3.2Knowledge base moduleWork package
1.3.3CRM integrationWork package
1.4TestingDeliverable group
1.4.1System and integration test resultsWork package
1.4.2User acceptance test sign-offWork package
1.5Deployment and handoverDeliverable group
1.5.1Data migrationWork package
1.5.2User training and materialsWork package
1.5.3Go-live and support handoverWork package

The numbering lets you roll up costs and effort at any level, and trace issues to a specific part of the work.

How to Build a WBS

  1. Gather inputs: charter, scope statement, requirements and lessons from similar projects.
  2. Choose the top-level structure: by phase, by major deliverable, by system component or by workstream.
  3. Decompose each branch until you reach manageable work packages.
  4. Check the 100% rule and remove overlaps between branches.
  5. Involve the team: the people doing the work know what is missing.
  6. Assign codes and owners to each work package.
  7. Write the WBS dictionary and baseline the result.

Right-Sizing Work Packages

There is no universal rule, but practical guides include the “8/80 rule” (between 8 and 80 hours of effort) or “no longer than one reporting period”. If a package takes months, you cannot tell whether it is on track; if it takes minutes, you spend more time tracking than working. In Agile projects, the equivalent is breaking epics into stories; see User Stories in Scrum.

The WBS Dictionary

The dictionary gives more detail on each work package: description, responsible person, acceptance criteria, assumptions, dependencies, estimated effort and cost, and quality requirements. It prevents different people interpreting the same label differently, such as “testing”.

What the WBS Feeds

  • Schedule: activities are defined for each work package (see Project Scheduling).
  • Estimates and budget: costs roll up from packages.
  • Resource assignments: responsibility matrices map people to packages.
  • Risk identification: reviewing the WBS prompts risk ideas for each component.
  • Scope control: changes are measured against the baseline.

Common Mistakes

  • Building the WBS from activities (“design, build, test”) in place of deliverables.
  • Omitting project management, training or migration work.
  • Decomposing some branches to great detail and leaving others vague.
  • Creating the WBS alone, without those who will do the work.
  • Skipping the “out of scope” list in the scope statement.
Key takeaways
  • The scope statement defines deliverables, acceptance criteria, exclusions, constraints and assumptions.
  • The WBS decomposes deliverables into work packages that can be estimated and tracked.
  • Apply the 100% rule: all the work, and only the work.
  • The scope statement, WBS and dictionary together form the scope baseline.

Related Lessons