Create WBS
The act of breaking project deliverables and the work required into smaller, controllable pieces so they can be estimated, scheduled, and managed.
Key Points
- Produces a hierarchical Work Breakdown Structure focused on deliverables; the lowest level is a work package.
- Uses decomposition and stops when work packages are clear enough to plan, estimate, and control.
- Applies the 100% rule to capture the entire scope with no gaps or overlap.
- Key outputs include the WBS, WBS dictionary, and updates to the scope baseline and related documents.
Example
A project to develop a mobile app is decomposed into deliverables such as Requirements, Design, Development, Testing, and Release. Each deliverable is further split (e.g., Development into Front-end, Back-end, and Integration), and then into work packages like "Implement login API" or "Build onboarding UI" that can be estimated and assigned.
PMP Example Question
Which activity best represents the Create WBS process?
- Breaking deliverables into hierarchical work packages to form the scope baseline.
- Sequencing activities to build the project schedule network diagram.
- Identifying stakeholders and documenting their expectations.
- Estimating durations for each defined activity.
Correct Answer: A — Decomposing deliverables into work packages
Explanation: Create WBS focuses on deliverable-oriented decomposition to produce the WBS and related components of the scope baseline, not on sequencing, stakeholder identification, or duration estimating.