Value Breakdown Structure (VBS): Scope Decomposition with Value Estimates

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. A VBS is a WBS with value estimates assigned to each element. The top level of the VBS should include the major deliverables that have been discussed and generated among the stakeholders, with each deliverable assigned 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.

Why It Matters for the Exam

The VBS appears in PMI exam questions testing your ability to distinguish scope management tools and to determine whether a scope element is truly mandatory. Questions typically present a scenario where you must decide between using a WBS, VBS, or other breakdown structure, or ask you to calculate or interpret the value impact of removing a work package from the project scope.

Key Points to Remember (for the exam)

• Definition: A VBS is a WBS with value estimates assigned to each element; it is not a replacement for the WBS but an enhancement
• Primary Purpose: Determines whether a given scope element is truly mandatory—removing that element would erase the value of the entire project
• Value Assignment: Each item receives either a value-based number (dollars, lives saved, etc.) or a percentage of expected total project value (100% if mandatory)
• Critical Path Application: When a VBS element is on the critical path, it helps assess whether a higher-value baseline may exist (e.g., when accelerating or removing an element might exceed its cost)
• Mandatory Element Test: If a deliverable is assigned 100% of project value, removing it eliminates all project value—it is mandatory
• Decomposition Process: Each top-level VBS item decomposes into subdeliverables, which are further decomposed through a WBS into project scope and activities
• Drag Cost Estimation: Value-added estimates can be used to estimate the drag cost of each critical path item

Typical PMI Exam Example

A construction project has a VBS showing the "Foundation" deliverable assigned 100% of total project value. During execution, a stakeholder proposes removing the foundation to reduce costs. The project manager explains that removing the foundation would erase the entire value of the project because it is a mandatory scope element, as shown by the VBS.

PMI Exam Traps

• Trap: Confusing VBS with WBS Reality: WBS decomposes work; VBS adds value estimates to each WBS element—they are complementary, not interchangeable

• Trap: Assuming VBS replaces scope baseline components Reality: VBS is an additional tool; the scope baseline still includes project scope statement, WBS, and WBS dictionary

• Trap: Thinking VBS only applies to financial projects Reality: Value can be non-financial (students taught, lives saved); the VBS works for any project type

• Trap: Believing all VBS elements must total 100% Reality: Only mandatory elements are assigned 100%; other elements receive proportional value estimates

Important PMI Connections

Quick Review Questions

1. A project manager assigns 100% value to the "Regulatory Compliance" deliverable in the VBS. What does this indicate about the deliverable's necessity?

2. During what type of analysis would a VBS element on the critical path help determine if a higher-value baseline exists?

3. What is the key difference between a VBS and a standard WBS in terms of the information assigned to each element?

4. A project has a VBS with revenue-based value estimates. One deliverable is valued at $50,000 out of a total $500,000 project value. Is this deliverable mandatory? Why or why not?

5. How does the VBS decomposition process relate to the WBS decomposition process?

PMBOK v8 Reference

Section 2.3.2.3 - Value Breakdown Structure (VBS)