This guide covers everything you need to know about the work breakdown structure in PMBOK 8. The WBS is the hierarchical decomposition of the total project scope into manageable components — it is the foundational planning tool that organizes all project work into a structured, comprehensive framework from which schedules, budgets, and resource plans are built.
What Is the Work Breakdown Structure?
The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total project scope by breaking the project into progressively smaller components until the work is represented at the work package level — the lowest level at which work can be reliably estimated, scheduled, assigned, and controlled.
The WBS is governed by the 100% rule: the sum of all work at any level of the hierarchy must equal 100% of the work at the level above it. This rule prevents both gaps (work that exists but is not in the WBS) and overlaps (work that appears in multiple WBS elements and gets counted twice). Every piece of project work must appear in the WBS — if it is not in the WBS, it is not authorized project work.
The WBS is a deliverable-oriented structure, not a process-oriented one. Each element represents a deliverable or component to be produced, not an activity to be performed. Activities are derived from WBS work packages during schedule development.
Work Breakdown Structure in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the work breakdown structure belongs to the Scope Performance Domain and is produced during the Develop Scope Structure process. Along with the project scope statement and WBS dictionary, the WBS is one of the three components of the scope baseline.
The WBS feeds into the project schedule (each work package becomes a scheduling activity), cost estimation (each work package receives a cost estimate), and resource planning (each work package requires resource assignment). It is the foundational planning artifact from which all other planning outputs are derived.
Key Elements of the Work Breakdown Structure
A well-structured WBS typically includes:
- Level 1 — Project — the total project at the top level
- Level 2 — Major Deliverables or Phases — the primary project components (WBS elements 1.1, 1.2, etc.)
- Level 3 and below — Work Packages — the lowest level of decomposition, where work can be reliably estimated and assigned
- WBS Codes — unique alphanumeric identifiers for each element
- 100% Coverage — all project scope represented without gaps or overlaps
Work Breakdown Structure Example — Project Phoenix
The Project Phoenix WBS had four levels. Level 1 was “Project Phoenix — TechCorp Website Launch.” Level 2 contained six elements: 1.1 Project Management, 1.2 Requirements and Design, 1.3 Development, 1.4 Infrastructure, 1.5 Testing and QA, and 1.6 Launch and Transition. Level 3 decomposed each element into work packages — 1.3 Development split into 1.3.1 Frontend Development, 1.3.2 Backend Development, 1.3.3 CMS Configuration, and 1.3.4 Third-Party Integrations.
The WBS contained 23 work packages at Level 3, with four work packages decomposed to Level 4 for the most complex development tasks. The 100% rule was verified during WBS review by cross-checking every work package against the project scope statement. The WBS was the direct input to the activity list, which expanded each work package into 2-5 schedulable activities, producing the 67-activity schedule. The WBS also drove the cost estimation — each work package received a bottom-up estimate that aggregated into the $62,102 total project estimate.
You can download the complete filled-in example below — it shows exactly how the WBS was built for a real project.
Download Free Work Breakdown Structure Template and Example
We have prepared two free resources to help you build a work breakdown structure for your own projects:
- Download the Work Breakdown Structure Template — PMBOK 8 (blank, ready to fill in)
- Download the Work Breakdown Structure Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Work Breakdown Structure — Best Practices and Common Mistakes
Apply the 100% rule rigorously — after completing the WBS, review it against the scope statement to confirm nothing is missing. Decompose work packages to the level where they can be reliably estimated — too high (80+ hours) and estimates are unreliable; too low (under 8 hours) and management overhead outweighs the control benefit. Build the WBS collaboratively with the team: the people who will do the work will identify scope elements the project manager would miss.
The work breakdown structure is most effective when it is the shared reference for all project planning conversations. Teams that skip or rush WBS development often discover mid-project that significant work was never planned, estimated, or budgeted.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Project Management