PMP - Business Environment (8% of the exam) - Section 3.2

Evaluate and deliver project benefits and value, investigating that benefits are identified, agreeing on ownership of ongoing benefit realisation, and verifying measurement systems.

Investigate that project benefits are identified and that an owner is agreed for ongoing benefit realisation beyond the project's end. Verify that a measurement system is in place to track benefits, evaluate delivery options to demonstrate value, and appraise stakeholders of value gain progress so the project stays linked to the business case it was approved against.

Benefits realisationBusiness caseValue deliveryBenefits owner

Practice question for this objective

Free sampleBusiness Environmentmedium

A predictive infrastructure project was approved on a business case that promised a 20 percent reduction in call-centre handling time. Midway through delivery, a stakeholder asks the project manager to add a customer loyalty portal that is not in the business case but would be popular internally. How should the project manager BEST respond to protect the value the project was approved to deliver?

AAdd the loyalty portal because a popular feature will improve stakeholder satisfaction with the project overall.
BAssess the request against the business case and the benefits it commits to, then route it through integrated change control for a decision. Correct
CReject the request outright because it was not named in the original business case that the sponsor signed.
DEscalate the request to the steering committee immediately so senior leaders can settle it before the team wastes any effort.

Evaluate scope requests against the business case and process them through integrated change control to protect approved benefits. The business case is the reference point for whether new work advances the value the project was funded to deliver; measuring a change against it and applying integrated change control preserves benefit alignment rather than reacting to popularity or authority.

Why A is wrong: Adding scope purely because it is popular is gold-plating; it dilutes focus on the approved benefits and expands cost and risk without a business case, so it does not protect the value the project was funded for.

Why B is correct: The business case defines why the project exists and the value it must deliver; testing the request against it and using change control keeps delivery aligned to the approved benefits while giving the request a fair, governed evaluation.

Why C is wrong: A flat rejection skips analysis; the request might strengthen the business case or warrant a formal amendment, so refusing without evaluating it through change control is premature and closes off a possibly valuable option.

Why D is wrong: Escalating first offloads analysis the project manager should perform; the request should be assessed against the business case and passed through change control before consuming committee time, so immediate escalation is a premature handover.

See more PMP practice questions, answers explained.

Exam traps in Business Environment

Answers that look right on this material and are not. Each one is a distractor from a different question in the PMP bank for this domain.

Proceed with the two unmeasurable benefits as stated, since the business case was already approved and reopening it would delay planning.
Why it is wrong: An approved business case does not excuse benefits that cannot be tracked; carrying unmeasurable benefits forward guarantees that two of the three promised outcomes can never be demonstrated at realisation.
Record the productivity benefit as delivered at project closure, since the tool met every documented acceptance criterion.
Why it is wrong: Meeting acceptance criteria confirms the product works, but the benefit accrues in operational use over a year; declaring it delivered at closure confuses output with outcome and leaves realisation unmonitored.
Which option lets the team finish its current iteration fastest, so momentum on the schedule is preserved.
Why it is wrong: Short-term schedule momentum is one factor, but framing the decision on iteration speed alone ignores lifecycle cost and the value the business case seeks, so it is too narrow a basis for the choice.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.