# Work Breakdown Structure

A hierarchical decomposition of the project’s total scope into manageable deliverables and work packages that can be estimated, assigned, scheduled, and controlled.

- Type: artifact
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/work-breakdown-structure/>)

## What it means

A work breakdown structure, or WBS, organizes the complete authorized project scope into progressively smaller components. It is commonly deliverable-oriented: upper levels describe major outcomes or phases, while the lowest useful level contains work packages that can be planned and owned. A WBS explains what work is included, not the chronological order in which activities occur.

## Why it matters

Breaking scope into a shared hierarchy reduces omissions, double counting, and hidden work. The resulting work packages provide a consistent basis for estimating cost and duration, assigning accountability, building schedules, identifying risks, and measuring performance. The structure also makes scope changes traceable because teams can locate the affected deliverable and its dependent plans.

## When to use it

Develop a WBS after high-level scope and deliverables are understood but before detailed scheduling and budgeting. It is useful for predictive, iterative, and hybrid delivery whenever several teams or suppliers need a common scope model. Refine near-term work more deeply than uncertain work in distant phases.

## How it works

1. Confirm the authorized objectives, scope boundaries, deliverables, constraints, and acceptance expectations.
2. Choose a decomposition logic, such as product components, outcomes, phases, locations, or a deliberate combination.
3. Break each branch into mutually understandable components until work can be estimated, assigned, and controlled.
4. Document each work package in a WBS dictionary with scope, owner, assumptions, interfaces, and acceptance criteria.
5. Check that the hierarchy covers all project scope without adding unauthorized work, then baseline and maintain it.

## A practical example

For a customer-support platform rollout, the top level includes configured software, migrated data, operating procedures, training, and deployment. The migration branch is decomposed into data mapping, cleansing, trial migration, reconciliation, and production migration. Each work package has an owner and acceptance criteria before activities are sequenced in the schedule.

## Where it breaks

Decomposition can imply certainty that does not exist and may create administrative overhead when taken too far. A WBS does not show dependencies, timing, resource contention, or workflow by itself. Organizing around departments can reinforce silos, while omitting enabling work such as security review, adoption, or transition support leaves the plan incomplete.

## Common mistakes

- Treating the WBS as a chronological task list or Gantt chart.
- Decomposing inconsistently so branches overlap or omit authorized scope.
- Creating work packages without clear outputs, ownership, or acceptance criteria.
- Failing to update dependent estimates and schedules after approved scope changes.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/work-breakdown-structure/#visualization-work-breakdown-structure>)

## Sources

1. [Practice Standard for Work Breakdown Structures, Third Edition](<https://www.pmi.org/standards/work-breakdown-structures-third-edition>) — Project Management Institute · Professional standard overview
2. [Earned Value Management System: EIA-748](<https://www.energy.gov/media/212832>) — U.S. Department of Energy · Government project-controls guidance
3. [GAO Schedule Assessment Guide: Best Practices for Project Schedules](<https://www.gao.gov/products/gao-16-89g>) — U.S. Government Accountability Office · Government best-practice guide

## Related topics

- [Project Charter](<https://wiki.soroush.uk/topic/project-charter/>)
- [Gantt Chart](<https://wiki.soroush.uk/topic/gantt-chart/>)
- [Earned Value Management](<https://wiki.soroush.uk/topic/earned-value-management/>)
