September 6, 2026 · 9 min read
TL;DR: Delivery and value are different things, and the exam separates them deliberately. When benefit fails to appear, the keyed answer is to diagnose the gap, usually against the benefits management plan, not to terminate, escalate, or reassure anyone about dates. The product owner orders the backlog, and an MVP is the smallest deployable slice that still delivers real value.
An executive worries aloud that your project may not be aligned to the organization's strategic goals. You could reassure them the team will deliver on time and within budget, which is true, professional, and the wrong answer. As this bank puts it in a single line worth memorising: a perfectly delivered project that is not aligned is still waste.
Whether you can tell delivery from benefit. Delivery is hitting the plan. Benefit is the change the organization was buying, and the exam builds scenarios where those two come apart.
The 102 value-tagged questions in this bank lean agile in their instruments: 41 mention the product backlog, 29 benefits, 22 increments, 13 the minimum viable product, and 12 the business case. Financial metrics barely feature, with only four mentioning return on investment, net present value, or internal rate of return. It is a topic about ordering work by benefit, not about appraisal arithmetic.
Common trap: answering a value question with a delivery reassurance. When the concern raised is alignment, options offering on-time and on-budget delivery, a follow-up meeting, or a team performance review all answer questions nobody asked. The keyed answer is to review the project's alignment with the strategic goals, and this bank explains the rejection rather than just marking it.
Diagnose the gap before acting on it. Value that fails to show up points either at a project drifting from what the business case assumed or at assumptions that no longer hold, and only examining the alignment separates those two.
A kiosk network rollout makes the point. Transaction volumes come in far below what the business case promised, and four options follow: recommend terminating the project since the expected value is not being delivered, continue as planned and assume value appears later, adjust the objectives to match the value actually realized, or re-examine how the project aligns with business goals and identify where it needs realigning. The last one is keyed.
Each rejection teaches something. Waiting for value to materialise responds to the number by ignoring it. Terminating responds by abandoning a project whose problem has not been diagnosed. Lowering the objectives to match the shortfall is the most seductive, because it makes the metric go green while changing nothing real.
That last pattern is worth stating precisely: in every one of the five value-tagged records here where terminating the project is offered as an option, it is offered and it is never the keyed answer, even when the stem explicitly describes missing return or an intent to shut the project down. Five records is the entire population of termination-option questions in this topic rather than a sample, so treat it as a strong local pattern rather than a bank-wide law. The keyed move is consistently to diagnose first.
In the gap between specification and benefit. A product can satisfy every requirement it was given and still miss the outcome it was funded to produce, because the specification could have been wrong.
When a product owner says a finished product delivers no value despite meeting every specification, the keyed answer is to review the benefits management plan with them. That plan records what the benefit was supposed to be, which is what lets you locate where the gap actually lies: in the delivery, in the specifications, or in the product owner's expectations.
Notice what the distractors do. Terminating acts before diagnosis. Escalating to the executive board hands the diagnosis to people further from the work. Reprioritizing the backlog and asking the team to fix the issues assumes the gap is in delivery, which is one of three possibilities and not obviously the likeliest. The benefits management plan is also worth distinguishing from the business case: the business case states the investment logic, while the benefits management plan assigns a benefits owner who tracks realization after the project closes.
The smallest deployable slice of a product that still delivers real value to a customer. It is deployable, it can be measured in units of value, and it reduces risk by putting something usable in front of users early.
The word doing the work is minimum. One question asks which characteristic is not representative of an MVP, and the answer is that it adds value by including nice-to-have features, which contradicts the definition outright. Real feedback arriving before the organization commits to a large scope increment means a wrong assumption costs a small build rather than a whole release.
Applying it is a separate skill. When management expects the first iteration to give marketing a prototype to show prospective customers, the keyed answer is to identify the minimum functionality the product needs in order to be demonstrated. Splitting the backlog into phases and expanding the work breakdown structure both organize work without deciding what the demonstration requires. Asking the sponsor to prioritize hands off a judgment the project manager is there to make, and that instinct to escalate a judgment call recurs across this bank as a distractor rather than an answer.
One accountability does not move: the product owner orders the backlog. Across at least fourteen records here, wrong answers offer the project manager, the scrum master, a business analyst, or the team as substitutes for that specific decision, and none of them is keyed.
What does the exam mean by value-based delivery? Shaping and ordering work so benefit arrives early, rather than treating on-time and on-budget delivery as the goal.
What is a minimum viable product? The smallest deployable slice that still delivers real value. It excludes nice-to-haves by definition and reduces risk by producing early feedback.
The product meets every specification but delivers no value. What now? Review the benefits management plan with the product owner to locate whether the gap is in delivery, in the specifications, or in expectations.
Who orders the product backlog? The product owner. That accountability does not transfer to the project manager, scrum master, or team.
The 102 value-delivery questions in PMP Practice sit inside a bank of 2,141 re-certified against PMBOK 8 and the July 2026 Exam Content Outline, and every wrong answer carries the reasoning that makes it wrong, explained rather than just marked. Start the free 20-question sample with no card and no signup.
Related: Closing a project: the steps candidates skip · Business Environment tripled in weight · Process domain study guide · Business environment study guide
Sources: PMI — PMP Examination Content Outline, 2026 (PDF) · PMI — PMBOK Guide standards
What does the exam mean by value-based delivery?
Ordering and shaping the work so benefit arrives early and keeps arriving, rather than treating on-time and on-budget delivery as the goal. A project that delivers perfectly against its plan while missing the benefit it was funded to produce is still a failure, and the exam says so directly.
What is a minimum viable product?
The smallest deployable slice of a product that still delivers real value to a customer. It is measurable in units of value, it reduces risk by getting real feedback before a large commitment, and it deliberately excludes nice-to-have features. An option describing an MVP as adding value through nice-to-haves is contradicting the word minimum.
The product is finished and meets every specification, but delivers no value. What now?
Review the benefits management plan with the product owner. A product can satisfy every specification and still miss the benefit it was funded to produce, and the benefits management plan is the document recording what that benefit was, so it is what locates the gap.
Who orders the product backlog?
The product owner, and that accountability does not transfer. Across this bank's value-tagged questions, wrong answers regularly offer the project manager, the scrum master, a business analyst, or the team as substitutes for it.