Value-Based Delivery, Status and Closure

PMP PMP · Process

By Abu Anns · Last updated 20 November 2026Exam version: July 2026 ECO (current since 9 July 2026)

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.

Advertisement

Exam traps to watch for

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?

Report an error

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?

Report an error

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?

Report an error

Q4.A project's funding is cut and the sponsor decides to cancel the project immediately. What should the project manager do?

Report an error

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?

Report an error

Q6.A startup wants to test whether customers want a new mobile app before investing in full development. What should the project manager recommend?

Report an error

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?

Report an error

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?

Report an error