100%

Process - Task 3 of 10

Day 11: Value-Based Delivery

About 4.1% of the exam content - about 90 minutes - 14 practice questions

0:00 / --:--

Reading

Finishing on time and on budget is not the same as succeeding. A ramp built perfectly to spec at a house the family moved out of six months ago delivered zero value. This task is about keeping the project pointed at the benefit it was funded to produce: knowing what value means for this project, delivering it as early as the work allows, measuring whether it actually showed up, and being willing to change course when it does not.

The output to outcome to benefit chain Three stacked boxes. Box one, output: the ramp is built exactly to spec, on schedule and on budget. Box two, outcome: the resident enters and exits the home safely and independently. Box three, benefit: the resident ages in place longer, and institutional care cost is avoided. A rotated side note reads "only outcome and benefit prove value." A closing line notes that a minimum viable product or minimum business increment releases the smallest slice of this chain that already delivers a benefit, rather than waiting for the whole scope. OUTPUT The ramp is built exactly to spec, on schedule and on budget OUTCOME The resident enters and exits the home safely and independently BENEFIT Resident ages in place longer; institutional care cost avoided Only outcome and benefit prove value MVP / MBI: release the smallest slice of this chain that already delivers a benefit, do not wait for the whole scope to finish.
An output does not guarantee an outcome, and an outcome does not guarantee a lasting benefit. GCHS tracks all three, not just the first.

Where value comes from: the business case

The business case is the document that justifies the project: the problem or opportunity, the options considered, the recommended option, the expected benefits, the cost, and the assumptions behind all of it. It is created before the project, usually by the sponsor or a business analyst, and it is a key input to the charter. It is not a static document: the PM should revisit it when major assumptions change. If a GCHS weatherization program was justified by an assumed 30% utility savings and pilot data shows 8%, the business case itself has to be re-examined. Continuing to execute flawlessly against a broken justification is the failure mode this task exists to prevent.

The benefits management plan is the companion document: what benefits, when they will be realized, how they will be measured, who owns them after the project ends, and how they will be sustained. Many benefits appear only after closure: a home is modified in March, and the outcome "resident remains housed and independent for two more years" is measured long after the crew has left. Somebody in the organization has to own that measurement, and that assignment belongs in the benefits management plan.

Key points
  • Business case: why the project is worth doing; revisit when assumptions change
  • Benefits management plan: what benefits, when, how measured, who owns them after closure
  • Outputs (a ramp) lead to outcomes (safe independent entry) lead to benefits (aging in place, avoided facility cost)
  • Delivering outputs on schedule proves nothing about benefits: measure the outcome

MVP, MBI, and incremental value

A minimum viable product (MVP) is the smallest version of the product that delivers real value to users and generates usable feedback. It is not a rough draft or an unfinished product: it must genuinely work. For a GCHS intake system, an MVP might handle only storm-damage referrals, ignoring every other program, but handle them fully and reliably.

A minimum business increment (MBI) is the smallest chunk of work that delivers measurable value to the organization once released. MVP is oriented toward learning and validating; MBI is oriented toward realizing value. Both push in the same direction: stop waiting for everything to be finished before anything becomes useful.

This is why incremental delivery matters financially. Value delivered in month three starts producing benefit in month three. Twelve months of work delivered on the last day carries twelve months of risk that the need changed, funding lapsed, or the assumption was wrong. Frequent delivery is a risk-reduction strategy as much as a customer-satisfaction one.

ConceptWhat it meansPrimary purpose
MVPSmallest genuinely usable version of the productValidate assumptions, gather real feedback
MBISmallest release that delivers measurable business valueStart realizing benefits sooner
IncrementA working, usable addition produced in an iterationContinuous progress toward the whole
PrototypeA model used to elicit feedback; may not be usableClarify requirements, not deliver value

Measuring value

You should recognize the standard financial selection measures, because sponsors use them and the exam references them.

  • Net present value (NPV): the value of future cash flows discounted to today's dollars. Higher is better; a positive NPV means the project is worth doing. Given a choice, pick the higher NPV.
  • Internal rate of return (IRR): the discount rate at which NPV equals zero. Higher is better.
  • Payback period: how long until the investment is recovered. Shorter is better, but it ignores everything after payback, which is why it is a weak measure on its own.
  • Benefit-cost ratio (BCR): benefits divided by costs. Greater than 1 is favorable.
  • Return on investment (ROI): net gain relative to cost, expressed as a percentage.
  • Opportunity cost: the value of the option you gave up by choosing this project. If you choose a project worth 120,000 dollars over one worth 90,000, the opportunity cost is 90,000.
  • Sunk cost: money already spent and unrecoverable. It must be ignored in go/no-go decisions. "We have already spent 200,000 dollars so we cannot stop now" is always the wrong reasoning.

Nonprofit value is not only financial. GCHS measures homes made accessible, days of avoided institutional care, residents remaining housed after twelve months, and energy burden reduced. Define the measure up front. A value metric invented at closure to fit whatever happened is not a measure, it is a story.

Sunk cost and the exam

Any answer that justifies continuing a project because of money already spent is wrong. Any answer that evaluates the decision on remaining cost versus remaining benefit is on the right track. The correct question is never "how much have we invested?" but "given where we are today, is the remaining work worth the remaining cost?"

Keeping value visible during delivery

Several practices keep a project honest about value:

  • Order the backlog by value, not by convenience or technical sequence, subject to real dependencies and risk. WSJF and similar techniques make this explicit.
  • Demonstrate working results frequently. An iteration review with real users beats a status report every time: status reports show effort, demos show value.
  • Track value metrics alongside cost and schedule. Earned value tells you whether you are spending as planned; it does not tell you whether what you built matters.
  • Use kanban and cycle time where flow matters more than iterations: limit work in progress, measure lead and cycle time, reduce the delay between "we decided to do this" and "the family is using it."
  • Be willing to stop. A project that will not produce its benefits should be terminated, and terminating it early is a success, not a failure. The PM raises this with the sponsor with evidence.

Value, sustainability, and the wider footprint

Sustainability now appears by name in PMI's July 2026 outline (Process Task 7 covers cost of quality and sustainability), and it is sound practice to weigh social and environmental impact as part of value, not as a separate virtue exercise. For our work that is concrete: choosing a higher-efficiency HVAC unit whose lifecycle energy savings exceed its first-cost premium; specifying low-VOC finishes in homes with asthmatic residents; diverting demolition debris from landfill; hiring local subcontractors so the program's spending stays in the community it serves. Each of these is a value decision with a measurable outcome, and each can be written into the benefits management plan and reported to funders who increasingly require it.

AI shows up here too. Predictive models can help identify which homes will benefit most from a limited pool of accessibility funding, but a model trained on historical service data will happily reproduce historical inequities. The project manager is accountable for the fairness and explainability of a recommendation that decides who gets served, and "the model said so" is not an answer you can give a board.

Common trap

A project is 80% complete, on budget, and on schedule, but new census and inspection data shows the target neighborhood has largely relocated and the intended benefits will not materialize. The trap answers are "continue, we are nearly done" and "cancel it immediately." The correct move is to gather the evidence, quantify the revised benefits against remaining cost, and present the analysis to the sponsor and governance for a decision, including redirecting scope to a neighborhood where the benefit still exists. The PM surfaces the problem with data; the sponsor owns the go/no-go.

Practice Questions

1. A project is 70% spent and the sponsor argues it must continue because of the money already invested. This reasoning reflects:

  1. Sound financial stewardship
  2. The sunk cost fallacy
  3. Opportunity cost analysis
  4. Benefit-cost ratio thinking

2. Which document explains why a project is worth undertaking and is a key input to the project charter?

  1. The stakeholder register
  2. The benefits management plan
  3. The business case
  4. The project management plan

3. A minimum viable product is BEST described as:

  1. A product delivered under budget
  2. The first draft of a deliverable, released regardless of whether it is usable
  3. A prototype used to gather requirements
  4. The smallest genuinely usable version that delivers value and feedback

4. Two projects are proposed. Project A has an NPV of 180,000 dollars and Project B has an NPV of 240,000 dollars. Which should be selected and what is the opportunity cost?

  1. Project B; opportunity cost 180,000
  2. Project B; opportunity cost 60,000
  3. Project A; opportunity cost 60,000
  4. Project A; opportunity cost 240,000

5. Which selection measure ignores every cash flow that occurs after the investment has been recovered?

  1. Net present value
  2. Internal rate of return
  3. Payback period
  4. Benefit-cost ratio

6. A benefits management plan primarily addresses:

  1. What benefits are expected, when, how they are measured, and who owns them
  2. How risks will be identified and analyzed
  3. How the team will be acquired
  4. How deliverables will be produced, inspected, and handed over to the customer

7. A GCHS intake system backlog is being ordered for the next release. Which approach BEST reflects value-based prioritization rather than technical convenience?

  1. Build whichever items are easiest first, to show quick progress to stakeholders and the funder
  2. Let each department build its own module at the same time
  3. Build modules in the order they appear in the WBS
  4. Order the backlog by value using a technique such as WSJF, adjusted for dependencies and risk

8. GCHS compares two energy retrofit packages. Package A costs 40,000 dollars and produces an expected 52,000 dollars of benefit. Package B costs 60,000 dollars and produces an expected 84,000 dollars of benefit. Using benefit-cost ratio, which is the better value?

  1. Neither; BCR cannot compare projects of different cost
  2. Package B; its BCR (1.40) exceeds Package A's (1.30)
  3. Package A; its BCR (1.30) exceeds Package B's (1.40)
  4. Package A, because it costs less to implement

9. During a sprint review, stakeholders see a working demonstration instead of a written status report. This practice primarily supports:

  1. Formal schedule compliance reporting to the funder each month
  2. Keeping value visible throughout delivery
  3. Maintaining the risk register
  4. Procurement transparency requirements

10. A GCHS team uses kanban rather than fixed iterations because flow matters more than iteration boundaries for their work. Which measure is MOST directly relevant to that team?

  1. Cycle time
  2. Estimate accuracy
  3. Velocity
  4. Burn-down of remaining story points

11. GCHS is choosing an HVAC unit for a rehab; a higher-efficiency model costs more up front but saves substantially over its service life. Weighing this lifecycle tradeoff as part of the decision reflects:

  1. Sunk cost reasoning
  2. Considering social and environmental impact as part of value
  3. Gold plating, adding unrequested extras the homeowner did not ask for
  4. Scope creep

12. A predictive model recommends which homes should receive a limited pool of accessibility funding. A board member asks why certain households were excluded. What is the appropriate response?

  1. Refer the board member to the software vendor
  2. Decline to answer, citing a proprietary algorithm
  3. The project manager explains the recommendation and takes accountability for its fairness and explainability
  4. "The model made the recommendation"

13. Midway through execution, evidence shows a project's intended benefits can no longer be realized as scoped, though the work itself is progressing well. What should the project manager do?

  1. Quietly reduce quality to finish under the original budget
  2. Continue, since the work is already well underway
  3. Present the evidence to the sponsor and governance and recommend a decision, potentially redirecting scope
  4. Cancel the project immediately without informing the sponsor

14. How does a minimum business increment (MBI) differ from a minimum viable product (MVP)?

  1. An MBI applies only to physical products, and an MVP applies only to software
  2. An MBI is oriented toward validating assumptions, while an MVP is oriented toward realizing value
  3. They are synonyms used interchangeably in PMI material
  4. An MBI is the smallest release that delivers measurable business value, while an MVP is oriented toward learning and generating feedback

Glossary

Business case
The document that justifies a project: problem, options, recommendation, expected benefits, cost, and assumptions; a key input to the charter.
Benefits management plan
The companion document to the business case, defining what benefits are expected, when, how they are measured, and who owns them after closure.
Minimum viable product (MVP)
The smallest genuinely usable version of a product that delivers real value and generates trustworthy feedback.
Minimum business increment (MBI)
The smallest chunk of work that delivers measurable value to the organization once released.
Net present value (NPV)
The value of future cash flows discounted to today's dollars; higher is better, and a positive NPV means the project is worth doing.
Benefit-cost ratio (BCR)
Expected benefits divided by expected costs; a ratio greater than 1.0 is favorable.
Sunk cost
Money already spent and unrecoverable; it must be ignored in go/no-go decisions about remaining work.
Opportunity cost
The value of the option given up by choosing one project or alternative over another.

Progress

Previous: Day 10 Next: Day 12