Work Breakdown Structure Builder
Build a deliverable-oriented Work Breakdown Structure step by step, decompose project scope into manageable components and work packages, apply the 100% rule, and connect work packages to WBS dictionary information.
Decompose the Total Project Scope into Manageable Deliverables and Work Packages.
A Work Breakdown Structure is a hierarchical decomposition of the total scope of work to be carried out by the project team. The hierarchy moves from the project or major deliverable through progressively smaller components until the work is sufficiently defined and manageable.
- Start with the complete project scope at the root.
- Decompose by major deliverables or other appropriate scope components.
- Continue decomposition only as far as needed for effective planning and control.
- Identify work packages at the lowest level selected for management.
- Apply the 100% rule: child elements collectively represent the full scope of their parent.
- Use WBS codes and a WBS dictionary to clarify scope boundaries and package content.
Work Breakdown Structure Builder — Step by Step
Complete each locked stage before the next unlocks. Every reveal visibly changes the WBS dashboard.
Define the Project Scope
Customer Service Digital Platform WBS
The project root is shown before major deliverables are decomposed.
Focus Mode opens the guided workbench as a dedicated learning overlay while keeping the current learning stage and WBS dashboard together. Dashboard Full Screen expands only the WBS dashboard. Exiting Dashboard Full Screen returns to Focus Mode when Focus Mode is active. Zoom affects only the WBS dashboard.
WBS Elements and Dictionary Summary
The register mirrors the guided decomposition and progressively reveals codes, parent elements, work-package status and dictionary information.
| WBS Code | WBS Element | Parent | Level | Work Package? | Dictionary Summary |
|---|
Add a Work Package to a Deliverable
Experiment Mode is isolated from the guided example. Select a Level-2 deliverable, enter a new work-package name, and add it to an experimental copy of the WBS.
Quick Knowledge Check
Core WBS Principles
| Concept | Meaning | Practical Test |
|---|---|---|
| Hierarchical decomposition | Progressively subdivide total project scope into smaller components | Does each child clearly belong to one parent? |
| 100% rule | Children collectively represent 100% of the scope of their parent | Is anything missing or duplicated? |
| Work package | Lowest WBS component selected for estimating, ownership and control | Is it manageable without unnecessary further decomposition? |
| WBS code | Hierarchical identifier for each WBS element | Can the element's parent and level be read from its code? |
| WBS dictionary | Supporting information that defines the content and boundaries of WBS elements | Are scope, acceptance, ownership or assumptions clear enough to avoid ambiguity? |
Decompose only as far as needed for effective estimating, ownership and control; apply the 100% rule to protect scope completeness; and use WBS codes and the WBS dictionary to make package boundaries and management information explicit. The WBS structures scope—it does not sequence the schedule.