II.3 — Help Ensure Value-Based Delivery

II.3 · Last updated: 11/10/2026

Defining and measuring value before delivering it

II.3 — Help Ensure Value-Based Delivery is the third task in the Process domain of the 2026 ECO, a domain that carries 41% of the exam. The ECO lists six enablers for it:

• Identify value components with key stakeholders
• Prioritize work based on value and stakeholder feedback
• Assess opportunities to deliver value incrementally
• Examine the business value throughout the project
• Verify a measurement system is in place to track benefits
• Evaluate delivery options to demonstrate value

Read the list closely and you'll see that none of the items says "produce value". Every one of them is about defining value, prioritizing by it, measuring it or showing it. Most exam questions drawn from this task turn on that same point, because value can only be managed once it has been defined and measured.

The old "II.3" was about risk

II.3 is one of the numbers in the Process domain that moved in both directions. In 2021, II.3 meant assessing and managing risks. That topic is now III.5 — Plan and Manage Risk, and it sits in a different domain altogether, Business Environment. In 2026, II.3 is value-based delivery, and its predecessor was II.1, executing the project with the urgency required to deliver business value.

An older question tagged "II.3" is therefore most likely about risk. Since risk changed its domain along with its number, anyone who builds a study plan around domain weights has to account for the shift twice. The old number of this page's topic, II.1, now belongs to II.1 — Develop an Integrated Project Management Plan and Plan Delivery. The wider picture of the trap is in what changed in the 2026 PMP exam.

In PMBOK 8, value is how a project is judged

PMBOK® 8 treats value as the yardstick of a project. Under the Focus on Value principle, The Standard calls value the ultimate success indicator and driver of projects. It can be described and assessed through measurable metrics such as return on investment, and also through qualitative observations such as testimonials and societal benefits. It represents the overall worth of the project outcomes and the net benefits to stakeholders, particularly as key stakeholders see them (PMBOK® 8, Standard p.40).

The Guide puts the same idea into a single sentence. The fundamental objective of any project is to create positive value that justifies the investment and the effort undertaken (PMBOK® 8, Guide p.10).

So on the exam, "the project finished on time and within budget" doesn't count as proof of success by itself. Time and budget are constraints, and what measures success is the value the project leaves behind.

Tangible and intangible value

The book describes business value as a net quantifiable benefit, tangible or intangible, that may contribute to the health and well-being of the organization, and it illustrates the idea with a two-column figure (PMBOK® 8, Standard p.14, Figure 2-1). The tangible column holds monetary assets, productivity, profitability, stockholder equity, market share, infrastructure capabilities, utility and environmental improvements. The intangible column holds goodwill, brand recognition and trademarks, public benefit, acquired knowledge, compliance, reputation, employee well-being and environmental awareness.

The way the figure splits the environment across both columns is instructive. Environmental improvements are a measurable result, so they sit on the tangible side, whereas environmental awareness is an attitude and sits on the intangible side.

Intangible does not mean unmeasurable. The book's definition of value explicitly counts qualitative observations as a measure (PMBOK® 8, Standard p.40), which is also why the ECO gives "verify a measurement system is in place" an enabler of its own. An option that says "this benefit has no figure attached, so we can ignore it" runs straight against that enabler.

The document that measures benefits, and who owns it

In PMBOK the measurement enabler corresponds to a specific document. The benefits management plan defines the processes for creating, maximizing and sustaining the benefits a program or project provides. It describes how and when the project's benefits will be delivered and what mechanisms should be in place to measure them (PMBOK® 8, Guide p.115).

This plan reaches the project from outside. Business documents such as the business case and the benefits management plan are inputs to the project, and the sponsor is expected to supply in them the minimum information a project manager needs to start project activities (PMBOK® 8, Standard p.70). Responsibility is shared along the same lines. The project sponsor is generally accountable for developing and maintaining the business case, while the project manager provides recommendations and oversight to keep the project's success measures aligned with it (PMBOK® 8, Guide p.116).

The ECO's choice of verb fits that division of labor. The enabler asks the project manager to verify that a measurement system exists, which is a different job from building one. What is expected is to make sure such a system is actually working and, if something is missing, to bring the gap into the open.

Incremental delivery and the minimum viable product

The enabler about delivering value incrementally has a clear counterpart in the book. A minimum viable product (MVP) is a concept for defining the scope of a solution's first release to customers by identifying the fewest features or requirements that would deliver value (PMBOK® 8, Guide p.269).

The two limits in that definition have to be read together. The release carries as few features as possible, and it must still deliver value as a whole. A minimal release that delivers nothing of value is not an MVP, however small it is.

The book's example shows how this works. When little is known about customer preferences, an iterative approach built on a clear MVP, made from the minimum features collected in a backlog, can give the team rapid feedback and make it easier to adapt to changes (PMBOK® 8, Guide p.45). That is where the second condition in "prioritize work based on value and stakeholder feedback" comes from. Incremental delivery is as much about learning early as it is about shipping early.

Sometimes value means fewer features

The book sets two approaches side by side, and the difference runs in an unexpected direction (PMBOK® 8, Standard p.42). Picture a company rolling out a new internal technology system. A conventional approach would pick the product offering the most features for the price and then customize it to satisfy every stakeholder request. A value-focused approach instead aligns the project with business outcomes such as usage and adoption. According to the book, a simpler solution reached by reducing features and customizations may fit the organization's culture better and increase overall usage and satisfaction.

Adding value therefore does not always mean adding features. The same reasoning lies behind the book's rejection of gold plating and scope creep, covered in II.2 — Develop and Manage Project Scope.

Value reaches into every part of the project

One more point helps draw the boundaries of this task correctly. Value is a single task in the ECO's Process domain, yet PMBOK does not confine it to one chapter. The Standard says the Focus on Value principle, together with the principle on quality, is primarily addressed within the Governance, Scope, Risk, Schedule, Finance, and Stakeholders performance domains, which helps ensure the deliverables genuinely serve the business objectives the project is aiming for (PMBOK® 8, Standard p.38).

Six of the seven performance domains are named, so value runs through nearly the whole project. The ECO's enabler about examining business value throughout the project reflects this spread; assessing value is not something done once at the start and then filed away.

On the scope side, the concrete tool is the value breakdown structure (VBS). In this hierarchy the expected value of each deliverable is recorded as a number or a percentage, and prioritization is based on that record (PMBOK® 8, Guide p.38). The ECO's enablers about identifying value components and prioritizing work by value meet in this one tool.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p. X
• A Guide to the Project Management Body of Knowledge — cited as Guide p. X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page describes the book; it does not replace it.