Hi everyone,
I came across a study question while preparing for the PMP exam, and I’d like your input to clarify a doubt:
Scenario:A client requests a major scope change due to a change in the market environment, which will significantly add to the project cost. This change is approved through the change control process.
Question: What should the project manager do to put the project on track?A. Reevaluate the scope baseline and impact on the project objectives.B. Use the management reserve to account for the schedule uncertainty.C. Monitor risks to ensure the effectiveness of the risk management process.D. Reevaluate the cost management plan to address the impact of the change.
Provided solution: B. Use the management reserve. The rationale is that the market-driven change is an unforeseen, unknown-unknown event, and management reserves are intended to address such situations to keep the project on track.
My reasoning / doubt:
- The change has already been approved through change control, which means it is no longer “unforeseen” in the formal project plan.
- Per PMBOK, management reserves are for unknown-unknowns that have not yet been planned or approved, and the PM usually needs sponsor approval to use them.
- The textbook next step after an approved major scope change is typically to update the scope baseline and related plans (cost, schedule, quality) to reflect the change.
- Using the management reserve before updating the baselines or getting formal approval may not align with PMI best practices.
My question to the community:
- Is B truly correct from a PMBOK/PMP perspective, even though the scope change is already approved?
- Wouldn’t the PM need to update the scope baseline first and then, if needed, request management reserve usage?
- How do you reconcile the guidance that management reserves are for unknown-unknowns with an approved change request?
I’d really appreciate your insights — this seems like a subtle but important distinction that could affect how we answer PMP exam questions.
Thanks in advance!