Value Delivery System in Project Management
PMBOK v8 Definition
Value is something of worth, importance, or usefulness created when project outcomes produce benefits. Benefits are positive effects realized by the organization, while disbenefits are negative consequences or losses. Because all projects are investments, their expected value—whether financial or nonfinancial—should meet or exceed target thresholds to justify the investment. A value delivery system works most effectively when information and feedback are shared consistently among all components, keeping the system aligned with strategy and attuned to the environment.
Why It Matters for the Exam
The concept of value appears frequently in PMI exam questions about project justification, benefits realization, and strategic alignment. You will encounter it in scenario-based questions asking whether a project should continue, what constitutes success, and how to evaluate long-term performance versus short-term outputs.
Key Points to Remember (for the exam)
- Value Definition: Value is something of worth, importance, or usefulness—can be financial (NPV) or nonfinancial (social benefits, customer satisfaction)
- Value Chain: Outcomes → Benefits (positive) or Disbenefits (negative) → Value
- Project Justification: Expected value must meet or exceed target thresholds to justify investment
- Strategic Alignment: Value delivery requires consistent information and feedback among all components
- Value Expression: Includes financial contributions, social benefits, and customer-perceived benefits
- Investment Perspective: All projects are investments requiring value greater than what is invested
- Alternative Comparison: Projects must often exceed what alternative investment options offer
Typical PMI Exam Example
A company invests in a new software system. The project produces the software (output), which improves customer response time (outcome). This improvement generates higher customer retention (benefit). The net financial gain minus implementation costs represents the project's value. The project sponsor asks whether this value justifies the initial investment compared to other potential investments.
PMI Exam Traps
-
Trap: Confusing outputs with outcomes Reality: Outputs are deliverables (products, services, results); outcomes are long-term effects or changes generated by deliverables
-
Trap: Thinking only financial value matters Reality: Value includes nonfinancial elements like social benefits, customer satisfaction, and strategic alignment
-
Trap: Assuming benefits are always positive Reality: Projects can create disbenefits (negative consequences or losses) alongside benefits
-
Trap: Equating benefits with value directly Reality: Benefits create value, but value represents the overall worth considering both benefits and disbenefits
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Benefits Management Plan | Documents value delivery | Describes how and when benefits will be delivered and measured |
| Business Case | Provides value justification | Contains target benefits, strategic alignment, and expected value thresholds |
| NPV (Net Present Value) | Financial value measure | Financial value may be expressed as NPV in target benefits |
| Strategic Alignment | Value requirement | Project value must align with business strategies of the organization |
Quick Review Questions
-
What is the difference between a benefit and value according to PMBOK v8?
-
A project delivers a new manufacturing process that increases production speed but causes higher defect rates. How should this be classified in terms of outcomes?
-
Why must a project's expected value meet or exceed target thresholds?
-
What three elements are essential for a value delivery system to work effectively?
-
How can value be expressed beyond financial terms?
PMBOK v8 Reference
Section 1.2 - Value Delivery System