A work breakdown structure is the hierarchical decomposition of project scope into deliverables and work packages. Done well, it becomes the backbone of the schedule, the cost estimate, and the resource plan. Done poorly — or skipped — it produces schedules that miss work, estimates that are wrong, and teams unclear on what they actually own.
- WBS decomposes scope into deliverables, not tasks — the schedule handles tasks
- The 100% rule: the WBS must represent 100% of the project scope — nothing added, nothing missing
- Work packages at the bottom level should be 8–80 hours of effort to estimate reliably
- The WBS dictionary defines each element in terms of scope, acceptance criteria, and responsible party
Deliverable-based vs. phase-based WBS
A deliverable-based WBS organizes work around what will be produced. A phase-based WBS organizes work around project phases (initiation, planning, execution, close). Most practitioners recommend deliverable-based because it connects more directly to scope and acceptance criteria.
Decomposition depth
Decompose to the level where work can be estimated reliably, assigned to a single responsible party, and tracked as a discrete unit of progress. Work packages at 8–80 hours are the standard guideline. Too fine-grained creates scheduling overhead; too coarse creates estimation errors.
The WBS dictionary
The WBS dictionary defines each element: description, acceptance criteria, responsible party, estimated effort, and related deliverables. It transforms the hierarchical structure from a scope summary into a project reference document.
Using the WBS to build the schedule
Once the WBS is complete, translate each work package into schedule activities, sequence them by dependency, assign resources, and estimate durations. The WBS drives the schedule — not the other way around.
Frequently asked questions
Detailed enough to estimate accurately and assign clearly. For most projects, 3–4 levels of decomposition with work packages of 8–80 hours is the right depth.
Projects above a certain complexity threshold (roughly 3+ months, multiple team members, defined budget) benefit significantly from a WBS. Simpler projects can use a task list.
The WBS defines scope. The project plan (schedule) sequences that scope into a timeline with dependencies, resources, and dates.
Request How to Build a Work Breakdown Structure (WBS)
Answer a few quick questions. We will recommend the right engagement and follow up within one business day.
Ready to put this into practice?
PMOstart provides consulting, fractional PMO leadership, templates, and tools to help you apply what you just read.