Work Breakdown Structure

A work breakdown structure (WBS) is a deliverable-oriented decomposition of a project into smaller, manageable pieces — the single most important planning tool because everything else (schedule, budget, responsibilities) hangs off it.

A work breakdown structure is a hierarchical breakdown of the total scope of work into progressively smaller components. The top level is the project itself; each level below decomposes deliverables into sub-deliverables, ending in work packages — units small enough to estimate, assign and control. A well-formed WBS obeys the 100% rule: the children of any node together represent 100% of that node’s scope, no more and no less. Crucially, a WBS describes deliverables (nouns — "trained staff", "test report"), not activities (verbs).

Also known as: WBS.

Why it matters

The WBS turns a vague, intimidating project into a finite, countable list of things to produce. It is the foundation for estimating (you cost work packages, not the whole project at once), for scheduling (activities are derived from work packages), for assigning responsibility, and for measuring progress. It also prevents scope creep: if a piece of work is not in the WBS, it is not in the project, and adding it becomes a visible decision rather than a quiet drift.

When to use it

Build a WBS during planning, after the scope statement is agreed and before you sequence activities or estimate cost. Any project complex enough to need a schedule needs a WBS first. It is equally useful in predictive/waterfall projects and as a scope backbone even in hybrid delivery.

How to use it

1. Start from the final deliverables in the scope statement — these are your level-2 elements.
2. Decompose each deliverable into the sub-deliverables required to produce it.
3. Keep decomposing until each work package can be reliably estimated (a common rule of thumb: 8–80 hours of effort).
4. Apply the 100% rule at every level — the children must sum to the parent, with no gaps or overlaps.
5. Assign a unique code to each element (1, 1.1, 1.1.1) and capture the details in a WBS dictionary.

Example

For "Company Website" the WBS might be: 1 Website → 1.1 Design (1.1.1 Wireframes, 1.1.2 Visual design), 1.2 Content (1.2.1 Copywriting, 1.2.2 Images), 1.3 Build (1.3.1 Front end, 1.3.2 CMS), 1.4 Testing, 1.5 Launch. Each leaf is a work package that one owner can estimate and deliver.

Template

A WBS template provides the numbered tree plus a WBS dictionary with, per work package: a code, a name, a description, the responsible owner, acceptance criteria, an estimate and any dependencies.

Browse templates →

Tools

Formula

Related topics

FAQs

Alternatives

• Product Backlog — the Agile equivalent, an ordered list of features rather than a fixed tree
• Product Breakdown Structure (PBS) — decomposes the product’s components rather than the work
• Mind map — a looser, non-100%-rule way to explore scope