Value-Based Delivery, Status and Closure
PMP PMP · Process
Delivering value, not just deliverables
The final Process guide covers three tasks from the July 2026 ECO: help ensure value-based delivery, evaluate project status, and manage project closure. They are grouped together because they share a theme: a project is not judged by whether it produced its deliverables on time and on budget, but by whether it delivered value — and the project manager's job is to keep the project pointed at value from start to finish, to report honestly on where it stands, and to close it properly when the work is done.
Value-based delivery starts with a simple question that the project manager should ask continuously: is this work still the most valuable thing we could be doing? In predictive projects, value is defined up front in the business case and the scope, and the project manager protects it by controlling scope and delivering what was agreed. In agile projects, value is defined continuously: the product owner orders the backlog so the most valuable items are built first, the team delivers working increments frequently, and stakeholders give feedback that reshapes the priorities. In both cases, the exam rewards the project manager who focuses on outcomes (what the customer and the organization gain) rather than outputs (what the team produces). A question describing a team that has delivered every planned feature but whose customer is unhappy is testing exactly this: outputs without outcomes are not value.
Prioritization and the minimum viable product
Value-based delivery needs prioritization techniques, and the exam tests the most common ones. The MoSCoW method sorts requirements into Must have, Should have, Could have, and Won't have (this time). The Kano model sorts features by how they affect customer satisfaction: basic features (expected, and their absence causes dissatisfaction), performance features (more is better), and delighters (unexpected features that create satisfaction). The 100-point method (cumulative voting) gives stakeholders 100 points to distribute across features, forcing them to make trade-offs. Weighted shortest job first (WSJF) divides the cost of delay by the job size, prioritizing work that delivers the most value per unit of effort. The exam tests these mainly by scenario: a question asking how to prioritize a backlog when everything seems urgent is usually looking for MoSCoW or WSJF, and a question about a feature that delights customers is testing Kano.
Closely related is the minimum viable product (MVP): the smallest version of a product that delivers enough value to be released and to generate learning. The MVP is not a low-quality product; it is a focused one — it contains only what is needed to test the core idea with real users. The exam expects you to know that delivering an MVP early and learning from it is better than building the full product in secret and discovering at the end that nobody wants it. Incremental delivery (releasing in small, usable pieces) and iterative delivery (refining through repeated cycles) are the two patterns that make MVP thinking work in practice.
Evaluating project status honestly
Evaluating project status means comparing actual performance against the baselines and reporting the truth — including bad news — promptly and accurately. The tools are the ones covered in the cost and schedule guides: earned value analysis, variance analysis, trend analysis, and forecasting. The exam's emphasis is on honesty and action: a project manager who discovers a problem and reports it promptly with a proposed response is doing their job; a project manager who hides a problem in the hope that it will fix itself is failing at it. Several exam scenarios test this directly, and the correct answer is always some version of "report it now, with the facts and a plan."
Status evaluation also includes the project's health beyond the numbers: team morale, stakeholder confidence, risk exposure, and quality trends. A project that is on schedule and on budget but has a demoralized team and a dissatisfied customer is not healthy. The exam rewards the project manager who looks at the whole picture — the dashboard, the team, and the stakeholders — rather than the one who reports green status because the earned value figures happen to look good this week.
In agile projects, status is evaluated continuously through iteration reviews, daily standups, and information radiators (burndown charts, task boards, cumulative flow diagrams) that make progress visible to everyone. The exam expects you to know that agile status reporting is transparent and frequent by design — there is no monthly status report that hides problems for weeks, because the board on the wall shows them every day.
Managing project closure
Project closure is the formal end of the project, and the exam treats it as a real phase of work, not an afterthought. Closure includes: verifying that all deliverables have been completed and accepted, closing all contracts (procurement closure), releasing the team and other resources, completing the final report, archiving project documents and records, capturing and sharing lessons learned, and formally transferring the deliverables to the customer or to operations. The project manager also ensures that the project's knowledge is preserved — the lessons learned register, the final report, and the archived documents become organizational process assets for future projects.
Two closure scenarios appear on the exam regularly. The first is early termination: a project cancelled before completion (because the business case failed, the market changed, or the funding was cut). The correct response is to close the project properly anyway — document what was completed, preserve the work and the knowledge, release resources, and close contracts. Cancelling a project does not mean abandoning it; the closure work still matters. The second is the customer who will not accept the final deliverable. The correct response is to review the acceptance criteria with the customer, address any genuine gaps, and escalate through the proper process if the customer refuses acceptance without a valid reason — not to keep the project open indefinitely or to accept the refusal without challenge.
Closure also includes the administrative and human side: celebrating the team's contribution, conducting performance reviews, and helping team members transition to their next assignment. The exam's servant-leadership theme runs through closure too — a project manager who ends a project by thanking the team and recognizing their work is doing what PMI expects.
Benefits realization and the project after the project
A project's value is often realized after the project closes: a new system saves money over years, a new product generates revenue, a process change improves quality. The benefits management plan describes how those benefits will be measured and who is responsible for realizing them — usually the sponsor or the receiving organization, not the project manager. The exam expects you to know that the project manager's responsibility is to deliver the capability that enables the benefits, and to hand over clearly to whoever will realize them. A question asking who is responsible for benefits after closure is testing this handover: the sponsor owns the benefits, the project manager delivers the project that makes them possible.
Exam mindset for value, status, and closure
For these topics, the pattern is: value over output, honesty over comfort, and proper closure over abandonment. Prioritize the most valuable work first, deliver it in increments that generate feedback, report status truthfully and promptly, and close the project completely — including the lessons learned, the archived records, and the recognition the team deserves. A project that ends well leaves the organization stronger; a project that just stops leaves confusion behind.
Exam traps to watch for
- Confusing outputs with outcomes. Delivering every planned feature is not success if the customer gains no value from them.
- Hiding bad news about project status. The correct response to a problem is to report it promptly with facts and a proposed response.
- Skipping closure work when a project is cancelled early. Early termination still requires proper closure: documentation, knowledge preservation, contract closure, and resource release.
- Forgetting that the sponsor owns benefits realization after closure. The project manager delivers the capability; the sponsor owns the benefits.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A project team has delivered every feature in the scope statement on time and on budget, but the customer says the product does not solve their business problem. What is the MOST likely cause?
Explanation: Delivering every planned feature on time and on budget is delivering outputs. Value-based delivery requires validating outcomes — that the product actually solves the customer's problem — through ongoing engagement, feedback, and prioritization. If the team built exactly what was specified without checking that it still addressed the business need, the project can succeed on its own terms and fail on the customer's. Option B is wrong because the team delivered everything on time and on budget — effort was not the problem. Option A is wrong because the project finished on budget. Option C is possible but is not the most likely cause: the scenario gives no evidence of a change of mind, and blaming the customer avoids the real lesson about validating value.
Exam objective: PMP ECO Task: Help ensure value-based delivery (Process)
Q2.A product owner must prioritize a backlog of 20 features. Everything seems urgent, and stakeholders disagree about what matters most. Which technique would BEST force stakeholders to make explicit trade-offs?
Explanation: The 100-point method (cumulative voting) gives each stakeholder a fixed budget of 100 points to distribute across the features. Because the points are limited, stakeholders must make explicit trade-offs — putting more points on one feature means fewer for another — which surfaces real priorities in a way that asking 'is this important?' never does. Option A is wrong because the Kano model sorts features by how they affect satisfaction (basic, performance, delighter), which is useful analysis but does not force trade-offs between features. Option C is wrong because a Pareto chart ranks causes by frequency, which does not apply to prioritizing features. Option B is wrong because a fishbone diagram finds root causes of problems, not priorities.
Exam objective: PMP ECO Task: Help ensure value-based delivery (Process)
Q3.A project manager discovers that the project is three weeks behind schedule and $30,000 over budget. The next status meeting with the sponsor is in two weeks. What should the project manager do?
Explanation: The PMI reasoning chain is: report bad news promptly, honestly, and with a plan. The sponsor needs to know now — not in two weeks — because the variance may affect decisions the sponsor is making today, and because the proposed response may need the sponsor's approval or support. Option A is wrong because waiting two weeks withholds information the sponsor needs. Option D is wrong because quiet recovery attempts hide the problem and, if they fail, the sponsor learns about a worse situation even later. Option B is wrong because falsifying a status report is dishonest and a serious breach of professional conduct.
Exam objective: PMP ECO Task: Evaluate project status (Process)
Q4.A project's funding is cut and the sponsor decides to cancel the project immediately. What should the project manager do?
Explanation: Early termination still requires proper project closure. The project manager documents what was completed, preserves the work products and the knowledge gained (lessons learned), closes contracts and settles obligations, and releases resources formally. This protects the organization's investment in the work done so far and ensures the knowledge is available to future projects. Option A is wrong because abandoning the project without documentation wastes everything that was built and learned. Option B is wrong because the sponsor has cancelled the project — continuing to spend is unauthorized. Option C is wrong because asking people to work unpaid is unethical and unprofessional.
Exam objective: PMP ECO Task: Manage project closure (Process)
Q5.A customer refuses to accept the final deliverable, saying it does not meet their expectations. The project manager believes the deliverable meets all the agreed acceptance criteria. What should the project manager do FIRST?
Explanation: The PMI reasoning chain is: check the facts against the agreement before acting. The acceptance criteria are the objective standard — if the deliverable meets them, the customer's expectations may have drifted beyond what was agreed, and the discussion should be about the gap between expectations and the agreed criteria (and whether a change request is needed). If the deliverable does not meet them, the project manager must arrange corrections. Option C is wrong because escalation is premature — the project manager should first establish the facts. Option B is wrong because keeping a project open indefinitely is not a resolution. Option D is wrong because offering a discount to secure acceptance is a commercial negotiation that does not address whether the deliverable meets the criteria.
Exam objective: PMP ECO Task: Manage project closure (Process)
Q6.A startup wants to test whether customers want a new mobile app before investing in full development. What should the project manager recommend?
Explanation: A minimum viable product is the smallest version of a product that delivers enough value to be released and to generate learning from real users. It tests the core idea with minimum investment, and the feedback shapes what gets built next. Option B is wrong because building the full product before any customer feedback risks discovering at the end that nobody wants it — the most expensive possible way to learn. Option C is wrong because a signed requirements document is not the same as validated demand; customers often cannot say what they want until they see and use something. Option D is wrong because building several full versions multiplies the cost of the experiment instead of minimizing it.
Exam objective: PMP ECO Task: Help ensure value-based delivery (Process)
Q7.A project has delivered its final product, and the sponsor asks who is responsible for making sure the expected business benefits are actually realized over the next two years. What should the project manager say?
Explanation: Benefits realization is owned by the sponsor or the receiving organization, as described in the benefits management plan. The project manager's responsibility is to deliver the project outputs — the product, service, or capability — that make the benefits possible, and to hand over clearly to whoever will realize them. Option A is wrong because the project manager's role ends at closure; they cannot be responsible for business outcomes over the following two years. Option C is wrong because the team is released at closure. Option B is wrong because the benefits management plan explicitly assigns ownership of benefits realization — it does not leave them unowned.
Exam objective: PMP ECO Task: Manage project closure (Process)
Q8.An agile team's burndown chart shows the remaining work line consistently above the ideal line, and the gap is growing. What does this indicate?
Explanation: On a burndown chart, the line shows remaining work over time, and the ideal line shows where remaining work should be if the team is on track. A remaining-work line above the ideal line means more work remains than planned — the team is behind — and a growing gap means the team is falling further behind, not catching up. The project manager should investigate with the team: is the scope too large, are there impediments, were the estimates wrong? Option B is wrong because being above the ideal line on a burndown chart means behind, not ahead (on a burnup chart, above the line would be ahead — the charts are mirror images). Option D is wrong because increasing velocity would close the gap, not widen it. Option C is wrong because a sprint scope that is too small would show the team finishing early, not falling behind.
Exam objective: PMP ECO Task: Evaluate project status (Process)