PMP · Question #774
A project manager is managing an internal project that was poorly defined. Recently, the project manager received several change requests raised by the organization's upper management. What should…
The correct answer is D. Review the benefits of the proposed changes in relation to the business case. When faced with multiple change requests on a poorly defined project, the project manager's primary initial action should be to evaluate the proposed changes against the original business case and their potential benefits.
Question
Options
- AAssess the time overrun, and start implementation to avoid additional delays
- BMotivate the team to avoid the frustration of working on a prolonged project
- CRequest a provisional budget increase to avoid any budget overruns
- DReview the benefits of the proposed changes in relation to the business case
How the community answered
(26 responses)- A4% (1)
- B23% (6)
- C12% (3)
- D62% (16)
Why each option
When faced with multiple change requests on a poorly defined project, the project manager's primary initial action should be to evaluate the proposed changes against the original business case and their potential benefits.
Immediately assessing time overruns or beginning implementation without a thorough understanding of the change's value and impact is premature and risky, especially given the project's initial poor definition.
While team motivation is important, it is not the initial step when evaluating new change requests; the changes themselves must first be assessed for their validity and alignment with project goals.
Requesting a provisional budget increase is a reactive measure related to cost impact, which should only be considered after the benefits and feasibility of the change requests have been thoroughly evaluated against the business case.
The first step in evaluating change requests, especially on a poorly defined project, is to understand their strategic justification. Reviewing the benefits of proposed changes in relation to the business case ensures alignment with organizational objectives and helps prioritize changes that add true value before assessing time or cost impacts.
Concept tested: Change management and business case alignment
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
9D is the right call here. Coming from an environment where scope was always shifting on poorly defined initiatives, the first move is never to just start implementing changes, no matter how much pressure upper management applies. You need to tie those change requests back to the business case to see if they actually deliver value before touching the budget or the schedule. If the changes do not support the original business justification, you are just throwing good money after bad on a project that was already shaky.
Agreed on D, and I would add that documenting the impact analysis formally matters just as much as doing it, because when leadership comes back asking why the timeline moved, you need the paper trail showing which requested changes were rejected and why.
D. Saw this on my exam last month, business case wins every time.
D is right but watch your clock on these business case ones because they often disguise a second valid answer in the options and you can burn 90 seconds second guessing.
Confirmed D on exam last month. Since the project was poorly defined to begin with, the PM needs to validate that these upper-management changes actually support the business case before touching the change control process.
Agreed on D, and remember the blueprint frames this as performing integrated change control under Domain 4, meaning you also want that change request documented and routed through the CCB even if the business case validation kills it first.
Saw this on my exam, landed on D because proposed changes must tie back to the business case.
D is right but I would add that in practice the business case is what sells the change to the steering committee, so tying proposed solutions back to it is not just a formality, it is the whole reason the engagement exists.
D is a 10-second pick, flag anything else for later. Always tie changes back to the business case before doing anything else, but does anyone know if the exam expects a formal change request submission first when upper management is the source?