Value Breakdown Structure Decomposition into Subdeliverables and Work Packages

PMBOK v8 Definition

The Value Breakdown Structure (VBS) is a hierarchical structure that connects the project scope and its intended value to the product scope that will generate that value. Each item at the top of the VBS can then be decomposed into its component subdeliverables, which in turn are decomposed through a Work Breakdown Structure (WBS) into the project scope and activities to create the valued items in the VBS. The VBS is essentially a WBS with value estimates assigned to each element.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about scope management, value delivery, and the integration of value with work decomposition. Questions typically test your understanding of how the VBS connects value expectations to the WBS, and how value estimates at the VBS level drive prioritization of deliverables and work packages. Expect scenario-based questions where you must identify the correct sequence: VBS → WBS → project scope → activities.

Key Points to Remember (for the exam)

• Primary Function: The VBS connects project scope and intended value to product scope that generates that value
• Top Level Content: Major deliverables discussed and generated among stakeholders
• Value Input Requirement: Each VBS item must include a value estimate as either a value-based number (e.g., dollars of revenue, students taught to read, lives saved) or a percentage of expected total project value
• Mandatory Deliverables: If a deliverable is mandatory, its value is 100% of expected total project value
• Decomposition Sequence: VBS top items → component subdeliverables → WBS decomposition → project scope → activities
• Practical Uses of Value Estimates: Prioritize deliverables and their work, estimate drag cost of each critical path item
• Key Distinction: VBS focuses on value of deliverables; WBS focuses on work to create deliverables

Typical PMI Exam Example

A project to build a hospital has a VBS top-level deliverable "Emergency Department" with a value estimate of $2M in annual revenue. This deliverable is decomposed into subdeliverables (triage area, treatment rooms, equipment). Each subdeliverable is further decomposed through the WBS into work packages (install electrical, pour concrete, purchase monitors). The value estimate at the VBS level helps prioritize which work packages receive resources first.

PMI Exam Traps

• Trap: Confusing VBS with WBS as the same document

  • Reality: VBS is a WBS with value estimates assigned to each element; they are related but distinct

• Trap: Thinking value estimates are optional or subjective

  • Reality: Value estimates are required inputs into each VBS item as either a number or percentage

• Trap: Assuming VBS decomposition stops at the top level

  • Reality: Each top-level VBS item is decomposed into subdeliverables, then through WBS into project scope

• Trap: Believing value estimates only serve prioritization

  • Reality: Value estimates also serve to estimate drag cost of each critical path item

Important PMI Connections

Quick Review Questions

1. What is the correct sequence for decomposing value from the VBS level down to project activities?

2. A mandatory deliverable in the VBS should receive what percentage of expected total project value?

3. What two specific purposes do VBS value estimates serve according to PMBOK v8?

4. How does the VBS differ from a standard WBS in terms of content?

5. When decomposing VBS items, what comes after "component subdeliverables" in the sequence?

PMBOK v8 Reference

Section 5.4 - Creating the Work Breakdown Structure (Value Breakdown Structure subsection)