Value Well Intended: Maximizing Project Value for Portfolio Decisions

PMBOK v8 Definition

Value, also referred to as project value, is the ultimate success indicator and driver of projects. Value represents the overall worth of the project outcomes and the net benefits to stakeholders, and can be described using measurable metrics (such as return on investment) or qualitative observations (such as testimonials and societal benefits). A reliable evaluation of value should consider the entire context and life cycle of the project as well as its expected payback period, which may extend well beyond project closeout.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about portfolio management, project selection, and go/no-go decisions. You will see it tested in situational questions where you must determine whether a project should continue or be terminated based on its value contribution, and in questions linking value to business objectives and benefits realization.

Key Points to Remember (for the exam)

Ultimate Success Indicator: Value is the ultimate success indicator and driver of projects—not deliverables, scope completion, or schedule adherence.
Portfolio Decision Input: Project value provides key data for portfolio management so that decisions can be made on which projects to select or continue based on their value contribution.
Lifecycle Consideration: A reliable evaluation of value must consider the entire context and life cycle of the project, including payback periods that extend well beyond project closeout.
Short-Term and Long-Term: Value contribution can be short term or long term and may be intertwined with operational activities, making it challenging to isolate.
Program-Level Evaluation: When a project is part of a program, evaluating value at the program level is necessary to properly direct the project.
Quantitative and Qualitative: Value can be assessed using measurable metrics (ROI) OR qualitative observations (testimonials, societal benefits).
Outcomes Over Deliverables: Shifting focus from deliverables to intended outcomes allows project teams to deliver on the project's vision or purpose, rather than merely creating a specific deliverable.

Typical PMI Exam Example

A project team has delivered all required software features on time and within budget. However, customer productivity has not improved. The portfolio review board is considering whether to continue funding the project. What should the board evaluate?

Correct answer: Evaluate whether the project is delivering the intended value and outcomes, not just the deliverables. Value is the ultimate success indicator, and deliverables may not fully achieve the project's vision or purpose.

PMI Exam Traps

Trap: Confusing value with scope completion → Reality: Value is the ultimate success indicator; completing scope does not guarantee value delivery.
Trap: Believing value is only measured at project closeout → Reality: Value can be realized throughout the project, at the end of the project, or following project completion.
Trap: Thinking value is only quantitative (ROI) → Reality: Value can be described using measurable metrics OR qualitative observations such as testimonials and societal benefits.
Trap: Assuming value is isolated to the project level → Reality: When a project is part of a program, evaluating value at the program level is necessary to properly direct the project.

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Business Case	Input to value evaluation	The business case defines expected value; if misalignment persists, terminate the effort
Portfolio Management	Uses value data for decisions	Project value provides key data for selecting or continuing projects
Benefits Realization	Complements value focus	Value and the benefits that contribute to it can be defined in quantitative/qualitative terms
Risk Management	Supports value optimization	Optimizing workflows with acceptable risk exposure maximizes value per investment

Quick Review Questions

What is the ultimate success indicator and driver of projects according to PMBOK v8?
When evaluating project value, what time periods must be considered beyond project closeout?
If a project is part of a program, at what level should value be evaluated to properly direct the project?
Can value be assessed using qualitative observations? If so, provide an example from PMBOK v8.
What should a project team do if there is persistent misalignment between the project and its intended value?

PMBOK v8 Reference

Section 3.4 - Focus on Value Section 3.4.1 - Project Impact