Practice Standard for Work Breakdown Structures— Third Edition

PMBOK v8 Definition

The Practice Standard for Work Breakdown Structures—Third Edition provides the foundational guidelines for creating, decomposing, and applying a Work Breakdown Structure (WBS) in project management. A WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. This standard is part of the Scope Management knowledge area and applies across all process groups where scope definition and decomposition occur.

Why It Matters for the Exam

The WBS appears frequently on the PMI exam because it is the cornerstone of scope definition, cost estimation, and schedule development. Questions test your ability to distinguish the WBS from other planning artifacts, understand its decomposition rules, and recognize its role in preventing scope creep. Expect scenario-based questions asking which artifact defines all project work or how to properly decompose scope.

Key Points to Remember (for the exam)

• Primary Purpose: The WBS defines 100% of the project scope—anything not in the WBS is out of scope
• Decomposition Rule: Each descending level represents an increasingly detailed definition of project work; the lowest level is the work package
• Work Package: The smallest deliverable in the WBS that can be estimated, scheduled, managed, and monitored
• WBS Dictionary: A companion document that provides detailed information about each WBS component, including deliverables, activities, and acceptance criteria
• 100% Rule: The sum of all work at each WBS level must equal 100% of the work represented at the parent level
• Decomposition and: The standard explicitly links decomposition to work package estimation (page 143 reference)
• Hierarchical Chart: The WBS is commonly represented as a hierarchical chart (page 171 reference), but can also be presented in outline or tabular form

Typical PMI Exam Example

A project manager is defining the scope of a new software development project. The sponsor asks for a complete list of all deliverables that will be produced. Which artifact should the project manager create to ensure all project work is captured?

Answer: The Work Breakdown Structure (WBS), because it decomposes the total scope into manageable work packages that collectively represent 100% of the project work.

PMI Exam Traps

• Trap: Confusing the WBS with the project schedule Reality: The WBS defines what work will be done (scope), not when it will be done (schedule)

• Trap: Thinking the WBS lists activities Reality: The WBS contains deliverables and work packages, not activities—activities are derived from work packages during schedule development

• Trap: Believing the WBS must be created before requirements Reality: Requirements are collected first; the WBS is created after requirements are approved and scope is defined

• Trap: Assuming the WBS is only for large projects Reality: The WBS is valuable for projects of any size and is a standard practice across all project management methodologies

Important PMI Connections

Quick Review Questions

1. What is the smallest level in the WBS that can be estimated and managed?

2. According to the 100% rule, what must be true about the sum of work at each WBS level?

3. Which document provides detailed information about each WBS component, including deliverables and acceptance criteria?

4. What is the relationship between the WBS and the project schedule?

5. How does decomposition relate to work package estimation in the WBS standard?

PMBOK v8 Reference

Section: Practice Standard for Work Breakdown Structures—Third Edition (PMI, 2019) — referenced in PMBOK v8 as a key supporting standard for Scope Management