PMP · Question #48
A project is in the execution phase. The client was actively involved in the early stages but has been less engaged lately. A number of changes to the requirements have recently been requested. What s
The correct answer is A. Discuss the changes with the client and jointly make the decision on how to proceed.. A disengaged client is requesting numerous requirement changes during the project's execution phase.
Question
A project is in the execution phase. The client was actively involved in the early stages but has been less engaged lately. A number of changes to the requirements have recently been requested. What should the project manager do next?
Options
- ADiscuss the changes with the client and jointly make the decision on how to proceed.
- BReject the changes and stay the original course as initially agreed with the client.
- CReview the risk register to see if mitigations have already been outlined for this scenario.
- DReview the changes and make the decision based on the project team's recommendations.
How the community answered
(31 responses)- A77% (24)
- B6% (2)
- C3% (1)
- D13% (4)
Why each option
A disengaged client is requesting numerous requirement changes during the project's execution phase.
Engaging the client in a direct discussion about the requested changes and making joint decisions is critical for maintaining client satisfaction and ensuring the project continues to align with their evolving needs. This collaborative approach adheres to proper change management procedures and helps re-engage a disengaged stakeholder.
Outright rejecting client-requested changes without discussion is likely to alienate the client and can lead to significant dissatisfaction, potentially jeopardizing the project's success and relationship.
While reviewing the risk register is part of change impact analysis, the immediate and most crucial step is to engage directly with the client regarding their requests, not solely focus on internal documentation.
Making decisions solely based on the project team's recommendations for requirement changes bypasses client authority and ownership, risking the delivery of a solution that does not meet the client's current expectations.
Concept tested: Stakeholder engagement and change management
Topics
Community Discussion
3A is the golden pick here, and my memory hook is CARE: Client Actively Re-engaged Early. The client drifted away and then flooded you with change requests, so the fix is to pull them back to the table and hash out the path forward together. B is too rigid, D hands the steering wheel to the team when the client owns those requirement decisions, and C is a rabbit hole that does not actually resolve the changes. Confirmed A on exam last week because anytime you see late changes plus a disengaged client, the answer is always to collaborate, not to go solo.
Leaned D first, but client disengagement means re-engage them: A.
Confirmed A on my exam. Client reengagement fixes the root cause, not just the changes.