Decomposed Work Packages: Tailoring Decomposition Levels for Deliverables

PMBOK v8 Definition

Work packages are the lowest level of work decomposition in the Work Breakdown Structure (WBS). According to PMBOK v8, "the work for some deliverables should be decomposed only to the next level, while others may require additional levels of decomposition." This means decomposition is not a uniform process—project teams apply progressive elaboration, decomposing deliverables to varying levels of detail based on complexity, risk, and management needs, until the work is defined as manageable work packages.

Why It Matters for the Exam

The PMI exam frequently tests the concept that decomposition is not standardized across all deliverables. Questions appear in the Planning Process Group, specifically within Scope Management, asking candidates to identify when to stop decomposition or recognize that different work packages require different levels of detail. This concept is tested in situational questions where you must determine the appropriate decomposition approach for specific deliverables.

Key Points to Remember (for the exam)

• Decomposition is not uniform: Different deliverables require different levels of decomposition—some stop at the next level, others need additional breakdown
• Work package definition: The lowest level of the WBS where work is assigned, managed, and tracked
• Progressive elaboration rule: Decomposition continues until the work can be reliably estimated, assigned, and managed
• Common confusion: Thinking all deliverables must be decomposed to the same level—reality is they vary based on complexity and risk
• Stop condition: Decomposition stops when the work package is manageable, assignable, and estimable
• Key tool: Decomposition technique (not just a process, but a tool applied within Create WBS)
• Main output: Work packages (deliverables decomposed to manageable components)

Typical PMI Exam Example

A project manager is creating the WBS for a software product release. The "User Interface Design" deliverable is well-understood and can be decomposed to work packages in one level. However, the "Security Authentication Module" is complex and high-risk, requiring decomposition into three additional levels. The project manager correctly applies different levels of decomposition based on deliverable complexity.

PMI Exam Traps

• Trap: Assuming all WBS elements must be decomposed to the same number of levels

  • Reality: PMBOK v8 explicitly states decomposition varies—some deliverables need only one level, others need more

• Trap: Confusing work packages with activities

  • Reality: Work packages are deliverable-oriented (WBS level); activities are action-oriented (schedule level)

• Trap: Stopping decomposition too early because the deliverable seems simple

  • Reality: Even simple deliverables need decomposition until work is manageable—check estimation and assignment feasibility

• Trap: Thinking decomposition is a one-time activity

  • Reality: Decomposition is iterative (progressive elaboration) and can be refined as more information becomes available

Important PMI Connections

Quick Review Questions

1. A project has 10 deliverables. The "Database Design" deliverable is decomposed to 4 levels, while "User Manual" is decomposed to only 2 levels. Is this approach valid according to PMBOK v8?

2. What is the primary condition that determines when decomposition of a deliverable should stop?

3. During WBS creation, the project team realizes a work package is still too large to estimate accurately. What should the team do?

4. A PMP candidate states that "all WBS elements must be decomposed to the same level of detail." Is this statement correct?

5. What is the relationship between work packages and the scope baseline in PMBOK v8?

PMBOK v8 Reference

Section 5 – Tools and Techniques (Create WBS process) The standard states: "the work for some deliverables should be decomposed only to the next level, while others may require additional levels of decomposition. As the work is decomposed..." This appears in the Tools and Techniques section of the Scope Management knowledge area, within the Planning Process Group.