When to use it
A useful fit
Use it to check scope completeness, estimate deliverables or agree work-package ownership.
Know the limits
Do not mistake a detailed tree for a validated scope. Keep uncertain future work at an appropriate level until it can be defined.
How to use it
- Start from the agreed outcomes, deliverables and exclusions.
- Break down the work until each package can be understood, assigned and checked.
- Check for gaps and overlaps, including management and integration work, then describe acceptance conditions.
Worked example
A portal project initially lists only screens and integrations. A scope review adds data migration, support preparation and user acceptance. Each package receives an owner and a definition of completion before the estimate is rolled up.
Illustrative scenario by fannarmaximus; not an official exam question.
Common pitfalls
A list of technical components may omit training, migration, acceptance and operational handover.
Attribution & sources
WBS is a shared project-management technique. The series cites Gregory Haugan’s treatment of scope completeness. No single inventor is claimed here.
The citations below identify authoritative references for this topic. They do not imply endorsement or reproduce the bodies’ competence lists.
- Haugan, G. T. (2002). Effective Work Breakdown Structures. Project Management Essential Library. Vienna, VA: Management Concepts. ISBN 9781567261356.
- Project Management Institute (2025). A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Eighth Edition, and The Standard for Project Management. Newtown Square, PA: PMI®. ISBN 9781628258295.