PMP · Question #1051
A project scope was developed with numerous assumptions. During the execution phase, the assumptions changed, which has jeopardized the planned business value of the project. What should the project…
The correct answer is B. Update the assumptions log and change log, and implement the change control process. When project assumptions change and jeopardize planned business value, the project manager must formally document these changes and initiate the change control process.
Question
Options
- ADeliver what was planned in the project management document according to the specifications
- BUpdate the assumptions log and change log, and implement the change control process
- CInform the client that the project cannot meet the project timeline and additional costs will be
- DReport on the changed assumptions to the project sponsor and seek support to prioritize the
How the community answered
(21 responses)- A5% (1)
- B71% (15)
- C10% (2)
- D14% (3)
Why each option
When project assumptions change and jeopardize planned business value, the project manager must formally document these changes and initiate the change control process.
Delivering what was planned despite changed assumptions is irresponsible and risks project failure and loss of business value, as the original plan is no longer valid.
Changes to assumptions are critical and must be formally managed. Updating the assumptions log and change log ensures proper documentation, and initiating the change control process allows for formal review, approval, and management of the impact on scope, schedule, cost, and business value.
Informing the client of timeline and cost issues without first initiating formal change control is premature and does not address the underlying issue of changed assumptions systematically.
Reporting to the sponsor is a part of communication but does not constitute the formal process required to address the changed assumptions and their impact on the project.
Concept tested: Managing project assumptions and change control
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/process-groups/monitoring-controlling-process-group
Topics
Community Discussion
8
Anjali D.May 9, 2026Our group landed on B. When assumptions change and business value is at risk, you need to document those changes in the assumptions log and change log, then run them through the change control process. A is wrong because blindly following the original plan when the underlying assumptions have shifted defeats the purpose of monitoring and controlling. C and D both jump to escalating before you have gone through the proper process of evaluating the impact and submitting a change request. Anyone else get tripped up by D, since it sounds reasonable to involve the sponsor?
Yuki V.May 11, 2026Agree on B, and D is a classic trap because involving the sponsor feels like the responsible move, but the change control process has to come first so the sponsor actually has something concrete to evaluate.
Samuel O.May 14, 2026B is correct. Does anyone know if changed assumptions always trigger formal change control or just logging?
Lena V.Apr 17, 2026Leaned toward D but assumptions changed means update logs and run change control.
Grace U.Apr 27, 2026Going with C here. If assumptions shifted enough to threaten business value, the client needs to know about timeline and cost impact right away. You cannot just quietly update logs or keep delivering to a plan that no longer makes sense. The business value is at risk, so transparency with the client comes first before anything else.
Anjali D.Apr 28, 2026It is actually B, because when assumptions change enough to affect business value, you update the assumption log first to create the traceable record, then use that documented change to drive the conversation with the client about timeline and cost impacts. Grace is right that the client needs to know, but C skips the logging step that keeps the process auditable before escalating.
Yuki V.May 22, 2026Going with D here. When assumptions shift enough to threaten business value, that is a sponsor-level conversation, not a change control form. You need leadership to re-prioritize before you go updating logs or pushing forward with a plan that no longer delivers what mattered.
Anjali D.May 22, 2026Actually the answer is B, because once assumptions change and threaten value, the first step is updating the assumption log to capture the new information and then bringing it to the sponsor for a decision, not skipping the documentation. D sounds reasonable but it jumps straight to escalation without recording the change first, which is what the question is really testing.