PMP · Question #1057
During the execution phase of a project, one of the customer's stakeholders keeps requesting changes to the scope every week. Which three actions should the project manager take to resolve this…
The correct answer is A. Update the relevant project documents with this obstacle. B. Highlight the impacts of the changes during the next project meeting. E. Schedule a meeting with the customer to align the approach.1. To address frequent scope change requests, the project manager should document the impacts, highlight them to stakeholders, and align the approach with the customer.
Question
During the execution phase of a project, one of the customer's stakeholders keeps requesting changes to the scope every week. Which three actions should the project manager take to resolve this issue? (Choose three.)
Options
- AUpdate the relevant project documents with this obstacle.
- BHighlight the impacts of the changes during the next project meeting.
- CAdjust the project management plan to include the changes in scope.
- DContinue the execution as planned and defer the changes to a future phase.
- ESchedule a meeting with the customer to align the approach.1
How the community answered
(40 responses)- A73% (29)
- C20% (8)
- D8% (3)
Why each option
To address frequent scope change requests, the project manager should document the impacts, highlight them to stakeholders, and align the approach with the customer.
Documenting the constant scope change requests as an obstacle is crucial for formal tracking and ensures that the issue is recognized and can be communicated to stakeholders and addressed.
Highlighting the impacts (e.g., on schedule, cost, quality) of continuous changes during project meetings makes stakeholders aware of the consequences, which is essential for managing expectations and gaining their support for stability.
Adjusting the project management plan to include every change without formal change control or stakeholder alignment would lead to scope creep and loss of control over the project baseline.
Continuing execution as planned and deferring changes ignores the customer's immediate needs and may lead to dissatisfaction or a solution that no longer meets evolving requirements, which is unsustainable with frequent requests.
Scheduling a meeting with the customer is vital to directly address the frequent change requests, understand their underlying needs, and collaboratively align on a structured approach to manage scope changes going forward.
Concept tested: Managing scope changes and stakeholder engagement
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/project-scope-management/control-scope
Topics
Community Discussion
5
Bao N.Jul 5, 2026A, B, E confirmed. The combo here is about transparency and communication: you document the obstacle (A), show the impact of the constant changes (B), and sit down with the customer to get aligned on how to handle scope going forward (E). C and D are traps because you never just absorb scope changes or ignore them without going through the change control process.
Dervla O.Jul 5, 2026Second read of the stem matters here because if you miss that the customer is driving these changes, E becomes less obvious and people grab C thinking flexibility is the same as approval.
Dervla O.Jul 5, 2026A, B, and E is the trio here because you are dealing with a process breakdown, not a single approved change request. Updating project documents (A) captures the obstacle formally, highlighting impacts (B) makes the cost of this behavior visible to stakeholders, and scheduling the alignment meeting (E) tackles the root cause with the customer. C is a trap because you never silently fold scope changes into the plan without going through the change control process, and D is just avoidance that will blow up later. One thing that trips people up: does anyone know if the exam expects you to invoke the formal
Samuel O.Jul 3, 2026I first leaned toward C because in my old consulting gigs we would just absorb the changes and keep moving. But two decades of getting burned taught me that without documenting the obstacle, showing the impact, and getting the customer aligned, you end up eating the cost and schedule overrun yourself. A, B, and E is the right call.
Bao N.Jul 4, 2026A, B, and E is the right call but I would add that getting the change request signed before any further work happens is what actually protects you, because alignment without a paper trail still leaves you holding the bag.