Value Breakdown Structure (VBS): Product Scope, Value, and Deliverable Prioritization
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. It is essentially a WBS with value estimates assigned to each element. The top level of the VBS includes the major deliverables that have been discussed and generated among the stakeholders. The value that each deliverable is expected to add is input into each item as either a value-based number (e.g., dollars of revenue, students taught to read, or lives saved) or a percentage of the expected total value of the project (100% if the specific deliverable is mandatory).
Why It Matters for the Exam
The VBS concept appears in PMI exam questions that test your ability to link project scope to business value and prioritize deliverables. It is frequently tested in questions about scope management, value delivery, and critical path analysis, where you must determine whether a scope element is truly mandatory or whether accelerating/removing it generates higher value.
Key Points to Remember (for the exam)
- Primary Purpose: The VBS connects project scope and intended value to the product scope that will generate that value.
- Structure: It is a hierarchical structure—top level contains major deliverables; each descending level provides increasingly detailed value estimates.
- Value Input: Each item receives either a value-based number (dollars, lives saved, students taught) or a percentage of total project value (100% for mandatory deliverables).
- Critical Path Use: When a VBS element is on the critical path, it helps assess whether a higher-value baseline exists (e.g., when the value of accelerating or removing a given VBS element might exceed the cost).
- Mandatory Deliverable Test: A scope element is truly mandatory if removing it would erase the value of the entire project (value = 100%).
- Drag Cost Estimation: Value-added estimates from the VBS can be used to estimate the drag cost of each critical path item.
- Decomposition Process: Each top-level VBS item decomposes into component subdeliverables, which are further decomposed through a WBS into project scope and activities.
Typical PMI Exam Example
A project to build a hospital has five major deliverables. The VBS shows that the "Emergency Room" deliverable is assigned 100% of the project's value. During a schedule delay, the project manager uses the VBS to determine that removing the Emergency Room would erase all project value—confirming it is mandatory. The VBS also shows that accelerating the "Pharmacy" deliverable would generate value exceeding its acceleration cost.
PMI Exam Traps
- Trap: Confusing VBS with WBS → Reality: A WBS decomposes work; a VBS is a WBS with value estimates assigned to each element, focusing on value generation.
- Trap: Thinking VBS is only for financial projects → Reality: Value can be non-monetary (students taught to read, lives saved) depending on the project.
- Trap: Assuming all deliverables have equal value → Reality: Mandatory deliverables are assigned 100% of project value; other deliverables receive percentages or value-based numbers.
- Trap: Believing VBS replaces the business case → Reality: VBS connects scope to value but does not replace the business case—it complements it by providing granular value estimates per deliverable.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Work Breakdown Structure (WBS) | Foundation for VBS | VBS = WBS with value estimates; both decompose deliverables hierarchically |
| Critical Path | Application of VBS | VBS helps assess whether accelerating/removing a critical path element generates value exceeding cost |
| Product Scope | Content of VBS | VBS connects project scope to product scope characteristics (quality, performance specifications) |
| Value Delivery System | Strategic context | VBS is a tool within the value delivery system to ensure deliverables generate intended value |
Quick Review Questions
- What is the difference between a VBS and a WBS according to PMBOK v8?
- If a deliverable is assigned 100% of the total project value in a VBS, what does this indicate about that deliverable?
- How can a VBS element on the critical path help assess whether a higher-value baseline exists?
- What types of value-based numbers can be assigned to VBS elements? Give three examples from the PMBOK v8 context.
- After top-level VBS items are defined, how are they further decomposed into project activities?
PMBOK v8 Reference
Section 2.4.2 - Value Breakdown Structure (VBS) and Product Scope