Key Concepts
Projects exist to deliver benefits that matter to someone, and when they lose sight of that, teams stay busy delivering work not valued. This task puts value at the center of project decisions throughout delivery: identifying what value means, prioritizing the most important value first, deciding deliberately about incremental delivery, and tracking whether expected benefits are materializing.
Projects are not ends in themselves; they exist to deliver benefits that matter to someone: a sponsor, a customer, an organization, or a community. When projects lose sight of that, teams can stay busy for months delivering work that is not valued or needed.
This task puts value at the center of project decisions throughout delivery, not just at initiation. It covers identifying what value means for the project, prioritizing work to deliver the most important value first, making deliberate decisions about incremental delivery, tracking whether expected benefits are materializing, and demonstrating value to stakeholders before the project ends.
This task received a stronger emphasis in the 2026 ECO than in previous versions. We see new guidance on value metrics, incremental delivery decisions, and benefits tracking. The changes reflect how central these practices have become across all project approaches.
2.3.1 Identify Value Components with Key Stakeholders
Value analysis starts with defining what value actually means for this project. In a project management context, business value is a broad term covering quantifiable and non-quantifiable benefits derived from the project. It includes financial return, market position, environmental improvement, social benefit, and organizational capability growth. The full picture often spans several categories at once.
The main categories of business value to identify and discuss with key stakeholders include:
Financial
Financial means earning revenue, profits, or cost reductions. Some regulatory or compliance projects do not generate profit directly but are undertaken to avoid fines, business restrictions, or reputational damage. These still carry financial value in what they prevent.
Market share
Capturing a position in the market, sometimes at a short-term loss, in exchange for future benefits when that market matures or becomes more profitable.
Planet
Environmental benefits such as habitat protection, greenhouse gas reduction, or other pollution mitigation.
Social
Improvements to health, education, and social wellbeing for groups and individuals.
Grow capability
Research or development breakthroughs that expand organizational knowledge, create intellectual property, or open new options for future projects.
Business value should be defined from the customer or sponsor perspective, not the team or project manager’s perspective. Just because we think a feature is cool, impressive, difficult to create, or elegant in our own view does not mean it is any more valuable. Value is determined by the people who will use or benefit from the outcome.
Value Analysis
Value analysis is the process of examining each element of business value to understand its cost and benefit relationship. The goal is to optimize the overall value by increasing benefits and reducing costs. A useful working formula is:
Value = Benefit minus Cost
(PMI’s Project Success Report frames this as was the Value worth the Effort and Expense.)
This framing reminds us that a high-benefit feature is not automatically worth building. If the cost to develop it exceeds the value it returns, it should be reconsidered. Agile projects that prioritize backlogs purely by benefit without accounting for cost will find themselves building expensive features ahead of cheaper, equally valuable ones.
Objectives and Key Results
Some agile and hybrid projects use OKRs (Objectives and Key Results) as a goal-setting framework for defining and tracking value. The objective describes what the team is trying to achieve in qualitative terms. The key results define the specific, measurable outcomes that will confirm the objective has been reached. OKRs connect project work to strategic intent in a way that is visible and testable, making it easier for stakeholders to see whether the project is delivering what was intended.
2.3.2 Prioritize Work Based on Value and Stakeholder Feedback
Once value components have been identified, work should be sequenced to deliver the most important value as early as possible. This is not just an agile principle. On any project, delivering higher-value elements sooner reduces the exposure period and accelerates return on investment.
On predictive projects, prioritization happens during scope definition and planning. The project manager works with the sponsor and key stakeholders to identify which deliverables carry the most value and ensures the schedule sequences high-value work appropriately. Phased delivery or early milestone releases can be structured to front-load value.
Agile projects prioritize the product backlog based on business value, risk, and dependencies. The product owner is responsible for maintaining this prioritization, working continuously with stakeholders to keep the backlog ordered correctly as understanding evolves and conditions change. The result is that the team always works on the most valuable thing available. When capacity limits force trade-offs, lower-value items are deferred or removed rather than compromising the items that matter most.
Product Roadmap
A product roadmap is a high-level graphical summary of planned release components for a product or service. It provides a shared view of the direction, priorities, and delivery horizon for the project. Roadmaps are progressively elaborated as more information becomes available and can be presented in several formats: time-based views showing what is planned for each period, technology stack views organized by functional area, or release-based views showing which features are grouped into each delivery.
The figure below shows three example product roadmaps.
Example 1) Is a Now-Next-Later roadmap showing a time-based view of what the team plans to work on and deliver. In this example, the yellow cards depict user stories, but they could be features, epics or some other unit of functionality.
Example 2) shows a Technology Stack view of work for upcoming quarters. For each technology group (Web, Mobile, Backend, and Integration), their major deliverables are shown in the planned time period.
Example 3) shows a Release based roadmap with functional groups going horizontally and necessary to more optional features arranged vertically. Colored groups of stories indicate which have been selected for the first, second and third releases.
Product roadmaps are particularly valuable for communicating value sequencing to sponsors and senior stakeholders. They make the prioritization decisions visible and create a shared reference point for conversations about what gets delivered and when.
2.3.3 Assess Opportunities to Deliver Value Incrementally
One of the most powerful decisions a project manager can make is to find ways to deliver some value before the project is complete. Incremental delivery is the strategy of releasing smaller, functional deliveries throughout the project rather than one large delivery at the end.
The benefits are practical: early delivery generates real feedback from actual users, which is qualitatively different from feedback on designs or prototypes. It may create an early return on investment. It overcomes the tendency for teams to underinvest effort early in a long project, because a demo next week is more motivating than a release in twelve months. It keeps stakeholders engaged because they see progress rather than waiting.
The key question is not whether to deliver incrementally, but how to determine what constitutes a worthwhile increment.
MMF, MVP, and MBI
Three related concepts help teams define the minimum meaningful chunk of deliverable value.
Minimum Marketable Feature (MMF) is a small, self-contained feature that can be developed quickly and that delivers significant value to the user or customer. An MMF is something the customer would consider genuinely useful on its own.
Minimum Viable Product (MVP) is a version of the product with just enough functionality to test assumptions and learn what the customer actually needs. An MVP might contain no MMFs, one MMF, or several, depending on what is being tested. The purpose is learning, not full delivery. Teams use MVPs to validate approaches, technologies, and market assumptions before committing to full development.
Minimum Business Increment (MBI) is the minimum amount of change that delivers a recognizable business improvement. It was developed because some organizations objected to the word “marketable” in MMF, since not all projects produce products for sale. MBIs help teams validate whether a useful element of functionality has been delivered or a process improvement has been captured. They enable teams to build on success incrementally or adjust direction if a change did not deliver the expected benefit.
Even on predictive projects, the project manager should ask during planning whether any scope can be released earlier than the final delivery to generate value, reduce risk, or validate approaches. A phased delivery plan that brings forward the highest-value elements does not require a full agile approach. It requires the deliberate question: what is the minimum we need to deliver to get a meaningful result, and can we do that sooner?
2.3.4 Examine the Business Value Throughout the Project
Establishing project benefits at initiation is necessary but not sufficient. Benefits need to be examined actively throughout delivery to confirm the project is still on track to deliver what was justified in the business case.
Business conditions change. Markets shift. Organizational priorities evolve. A project that made clear sense at authorization may face a different landscape six months into execution. Examining business value throughout the project is what catches these changes before they result in completing something that no longer serves its original purpose.
This examination should happen at key milestones, phase gates, and review checkpoints, not only at project close. On predictive projects, stage gate reviews provide a structured opportunity to reconfirm business justification before committing to the next phase. On agile projects, the product owner is continuously accountable for the backlog’s alignment with business value, supported by regular stakeholder input at iteration reviews.
The benefits management plan is the reference document for this activity. It records the expected benefits, the timeframe in which they will be realized, the metrics used to measure them, and the person or group accountable for each benefit. Reviewing delivery progress against the benefits management plan answers the question that matters: are we still going to get what we came for?
Benefits Management Plan. A description of how and when the projects’ benefits will be obtained and measured. It typically contains sections including:
- Strategic alignment – How the project and its benefits align with the strategies of the organization and which group owns the benefits.
- Target benefit – The expected tangible and intangible business value to be achieved by the project.
- Timeframe – When the benefits will be delivered (short-term and long-term)
- Metrics – How the benefits will be measured. Both direct and indirect measures.
- Risks – Any risks associated with achieving the identified benefits.
- Assumptions – Any underlying assumptions the benefits management plan rely on.
Agile projects build value examination into the rhythm of delivery. The product owner reviews backlog priorities after each iteration to confirm that the remaining work still represents the best use of the team’s capacity. Stakeholder feedback gathered at iteration reviews provides a continuous signal about whether the product is meeting real needs. When priorities change significantly, the roadmap is updated, and the team redirects accordingly.
Organizations using agile or hybrid approaches may use a portfolio Kanban system to manage ideas through the stages: capture, evaluation, selection, sequencing, and delivery system.
Using portfolio kanban system, all ideas are welcome into the input funnel and there is no limit on the number of ideas that can be submitted. A high-level feasibility evaluation is performed, and a Go/No Go decision is made moving approved candidates into the Shortlisted Ideas category. Here a value statement is created and the understanding refined. The number of items is limited to keep workloads manageable and flowing quickly.
The next stage, Prioritize Ideas, sorts them by business value and, based on capacity, selects the highest-value ideas for delivery. They are placed in the program backlog and moved into the development stage when teams become available.
2.3.5 Verify a Measurement System Is in Place to Track Benefits
Identifying benefits without measuring them produces no accountability. A measurement system defines what will be tracked, how it will be measured, and who owns the result. Without this, it is easy for a project to complete, hand over a deliverable, and never confirm whether the promised value was actually realized.
The benefits management plan provides the measurement framework. It specifies the target benefit, the metrics to track both direct and indirect measures, the timeframe for realization, and any risks or assumptions the plan depends on.
Benefits Register
A Benefits Register records the expected benefits and their measurable indicators. It also captures the baseline performance before the project, the target after delivery, who is responsible for measuring each benefit, and when measurement occurs. The project team may not be responsible for realizing all benefits; many materialize after the project closes. Verifying the register exists and is connected to the right people is still a project responsibility.
Before the project closes, confirm that:
- Each expected benefit has a defined, measurable indicator
- A baseline measurement exists to compare against
- Someone outside the project team is named as the benefit owner
- The timing and method for post-project measurement are documented
If none of this infrastructure exists, raising it is part of delivering value-based outcomes. A project that delivers a product but leaves no way to verify the benefit has done only part of the job.
Agile teams track benefits incrementally by reviewing delivered value at each iteration review. The product owner keeps a running picture of which backlog items have delivered the expected outcomes and which have not. This ongoing tracking is more frequent and more connected to daily work than a traditional post-project benefits review.
Common financial measures used to track and evaluate project benefits include:
Return on Investment (ROI) measures the gain or loss from an investment compared to the amount invested, expressed as a percentage. A positive ROI confirms the project generated more value than it cost. A negative ROI means it did not.
Net Present Value (NPV) calculates the value of future cash flows in today’s money, accounting for inflation and the time value of money. NPV is particularly useful for comparing projects with different timeframes or different patterns of value delivery.
Internal Rate of Return (IRR) gives a single percentage figure representing the financial return rate of the project. It is used to compare the financial attractiveness of alternative investments.
Payback Period identifies when the project investment is recovered through the benefits generated. Shorter payback periods reduce financial risk and are often preferred by sponsors who need to see returns quickly.
Beyond financial measures, projects delivering product or service improvements can track value through:
Net Promoter Score (NPS) measures a customer’s willingness to recommend a product or service. Respondents score their likelihood of recommending on a scale of zero to ten. Scores of nine or ten are Promoters; scores of seven or eight are Passives; scores of six or below are Detractors. The NPS is calculated as the percentage of Promoters minus the percentage of Detractors. NPS is useful because it forces a holistic judgment: would you put your own reputation behind this product?
Feature adoption rate tracks how many users are actively using a delivered feature. A feature released but not adopted has not delivered value, regardless of whether it was built to specification.
OKR key results provide project-level measurement of whether strategic objectives are being achieved, connecting team delivery work to the outcomes that justified the project.
Agile Approach: Agile teams track value delivery through a combination of product metrics and delivery metrics. Product metrics measure outcomes: are users adopting the feature, is customer satisfaction improving, is the business problem being solved? Delivery metrics measure flow: how many items are being completed per period, how long does each item take from start to finish? Both sets matter. Delivery metrics tell you if the engine is running well. Product metrics tell you if the engine is pointed in the right direction.
2.3.6 Evaluate Delivery Options to Demonstrate Value
Not all project benefits arrive at the end of the project. Sponsors and senior stakeholders often need interim evidence that the investment is sound. Evaluating delivery options means asking what can be shown, demonstrated, or released during the project to provide that evidence.
Iteration Reviews and Agile Demos
Agile projects demonstrate new functionality at the end of every sprint or iteration. This gives stakeholders a regular view of what the team has built, what decisions were made, and what is coming next. Demonstrations provide opportunities for feedback, which may surface issues while correction is still inexpensive. They also generate confidence. Sponsors who see consistent, working delivery every two weeks have a very different level of trust than sponsors who hear progress reports but see nothing tangible until the end.
Expected Monetary Value
Expected Monetary Value (EMV) calculates the average financial outcome for future scenarios by multiplying the monetary value of an outcome by its probability. Teams can use EMV to compare delivery options by quantifying the expected return under uncertainty. EMV applies to both opportunities (positive values) and threats (negative values), making it a useful tool for evaluating risky choices about delivery sequencing.
Decision Tree Analysis
A decision tree is a branching model that maps decisions and their possible outcomes, including probabilities and financial values at each branch. Decision tree analysis helps teams evaluate options by working through the likely results of each choice and calculating the expected value of each path. This is particularly useful when choosing between delivery approaches that carry different risk and reward profiles.
As an example, imagine if PMillustrated owned a petting zoo of all the animals featured and wanted to install a vending machine to sell food for the pigs. We have a choice between buying a fancy new specialized vending machine that will be branded with custom signage and using an old drink vending machine. The custom machine is designed to handle various package sizes, but it is not guaranteed for sticky products. If we use the bottle-vending machine, we will package the pig food in bottle-shaped containers.
A new vending machine with custom graphics costs $20,000 and is guaranteed to operate or the manufacturer will issue a refund minus a restocking fee and graphics fee of $10,000. We project $60,000 of sales with a custom machine and are 80% confident it will work. Without custom graphics, we expect $40,000 in sales using the drinks vending machine and are 60% confident it will work. If it fails, we cannot return it after it has been tested with pig food. These options are shown below.
The decision tree shows the two choices, “Buy custom machine”, and “Buy drinks machine” along with the chances of success and final node values. The top node showing $40,000 is calculated from revenue $40,000 – cost of machine $20,000. The two machine options are assessed using Expected Monetary Value (outcome x probability.) Using EMV we calculate the value of the custom vending machine option at +$34,000 and the value of the vending machine option as +$33,000.
So, it would seem (from a bunch of guesses multiplied together) that buying a custom vending machine is slightly better. However, what if our 80% / 20% likelihood of success for the custom vending machine was more like 90% / 10%? We would have to redo the calculations to see what impact it had. As we would with every other variation we want to evaluate. This is where simulations are powerful.
Expected Monetary Value
Expected Monetary Value (EMV) calculates the average financial outcome for future scenarios by multiplying the monetary value of an outcome by its probability. Teams can use EMV to compare delivery options by quantifying the expected return under uncertainty. EMV applies to both opportunities (positive values) and threats (negative values), making it a useful tool for evaluating risky choices about delivery sequencing.
As an example:
If we think an opportunity may return $2 million dollars if it is realized, and there is a 50% likelihood of it occurring, then the expected monetary value (EMV) would be:
EMV = $2,000,000 x 50% = $1,000,000
EMV can be used for opportunities that have positive values and threats that have negative values. So, if we thought the threat of a project delay for the vending machine delivery would cost us $4,000 and the probability of the delay is 75%, then:
EMV = -$4,000 x 0.75 = -$3,000
EMV is often used for quantitative risk analysis and for evaluating project options or decisions in the next process discussed, Decision Tree Analysis.
Simulations
Simulation is an analysis technique where a computer model is run many times varying the input data based on input ranges, probability distributions and even probabilistic branches. A popular form of simulation is a Monte Carlo Simulation which uses random values between input ranges and re-runs a set of calculations to model many possible outcomes.
Using Monte Carlo simulation, we could run 1,000 experiments where the probability of success for our custom vending machine varied between 65% and 95% with a strong preference (probability distribution) for values in the 75% – 85% range. We could also vary the projected revenue figures for both custom and drinks vending machines.
Varying all the input values at random between our likely ranges, Monte Carlo simulation analysis in a project management tool or simple Excel spreadsheet could quickly model 50,000 different scenarios and average EVM figures for both options. This weighted average may be quite different from the single path through the decision tree we calculated by hand.
Deliverables and Tools
- Benefits Management Plan
- Product Roadmap
- Value Stream Map
- OKRs (Objectives and Key Results)
- Minimum Viable Product (MVP)
- Minimum Marketable Feature (MMF)
- Minimum Business Increment (MBI)
- Net Promoter Score (NPS)
- Decision Tree Analysis
- Expected Monetary Value (EMV)
- Monte Carlo Simulation
- Return on Investment (ROI)
- Net Present Value (NPV)
- Internal Rate of Return (IRR)
- Payback Period
Related Topics
- 2.1 Develop an integrated project management plan and plan delivery
- 2.2 Develop and manage project scope
- 2.8 Plan and manage schedule
- 2.9 Evaluate project status
- 3.1 Define and establish project governance
- 3.2 Plan and manage project compliance
- 3.5 Plan and manage risk
- 3.6 Continuous improvement
- 3.7 Support organizational change
- 3.8 Evaluate external business environment changes
- PMP Mind Map
FAQ
Why does value matter beyond delivery?
Projects exist to deliver benefits; without value at the center, teams can deliver work that is not valued or needed.
What does value-based delivery involve?
Identifying what value means, prioritizing the most important value first, deliberate decisions on incremental delivery, and tracking whether benefits materialize.
When does this apply?
Throughout delivery, not just at project initiation.
How does this task fit into the 2026 PMP exam?
Task 2.3 sits in the Process domain of the 2026 Exam Content Outline. The 2026 PMP Exam page has the domain and task breakdown and what changed in the new exam.
Congratulations! You earned the Value Based Delivery badge.