Developing the Project Work Breakdown Structure
Before you schedule anything, break down the work. The WBS is the deliverable-oriented backbone that organizes all of a project's scope — the foundation the schedule, budget, and reporting all hang from. Build it once, build it well, and every control system lines up. Built on AACE 33R-15.
What a WBS is — and what it isn't
The key word is deliverable-oriented. A WBS is organized around what is produced (the foundations, the steel frame, the MEP systems) — not around activities ("excavate", "pour") and not around the org chart. Activities and schedule come later, decomposed from the work packages (Lesson 1).
Levels, branches, and work packages
A WBS is a tree. The top is the whole project; each level breaks the level above into its component deliverables; the leaves are work packages — small enough to estimate, schedule, assign, and control.
The rules that keep a WBS sound
- The 100% rule — each level captures all of the scope of the level above — no more, no less. Children sum to the parent. This is the single most important WBS rule.
- Mutually exclusive — no overlap between elements: a piece of work belongs to exactly one WBS element, or you'll double-count cost and progress.
- Deliverable / outcome-oriented — name elements as nouns (things produced), not verbs (activities). "Foundations", not "Pouring".
- Decompose to a controllable level — stop breaking down when a work package is small enough to estimate, schedule, assign, and track — not before, not into infinity.
- Unique coding — every element gets a unique WBS code (1.2.1). That code is the address cost, schedule, and reports all use to roll up consistently.
The WBS dictionary
The tree shows the structure; the WBS dictionary defines what each element actually means. For every element it records the scope description, deliverables, boundaries (what's in and what's out), and often the responsible party and associated cost account. It's what stops two people interpreting "1.3 MEP & fit-out" differently.
| The WBS gives you… | The dictionary adds… |
|---|---|
| The hierarchy and codes | A scope statement for each element |
| Where an element sits | What's included and explicitly excluded |
| The roll-up structure | Responsible party, cost account, assumptions |
Ten things to remember
- The WBS is a deliverable-oriented decomposition of all project scope — built first.
- It's organized by what's produced (nouns), not by activities (verbs) or the org chart.
- The lowest level is the work package — where activities (Lesson 1) are decomposed.
- The 100% rule: children sum to the parent — all scope, no overlap.
- Elements are mutually exclusive — each piece of work belongs to exactly one element.
- Decompose to a controllable level — small enough to estimate, schedule, assign, track.
- Every element gets a unique code — the shared address for roll-ups.
- Choose the organizing logic first (area, system, phase) to match how the project is managed.
- The WBS dictionary defines each element — scope, boundaries, owner, cost account.
- One WBS underpins schedule, cost, responsibility and reporting — it's why the numbers reconcile.
Glossary
- 100% rule
- Each level captures all the scope of the level above — children sum to the parent.
- Deliverable-oriented
- Organized around outputs (nouns), not activities or the org chart.
- OBS / RAM
- Organizational Breakdown Structure / Responsibility Assignment Matrix — maps WBS to owners.
- WBS
- A deliverable-oriented hierarchical decomposition of total project scope.
- WBS code
- The unique identifier (e.g. 1.2.1) used to roll up cost, schedule, and reports.
- WBS dictionary
- Definitions of each element — scope, boundaries, owner, cost account.
- WBS element
- Any node in the WBS tree, with a unique code.
- Work package
- The lowest WBS level — decomposed into activities for scheduling.