Question walkthrough 02
PMP question walkthrough: A mandatory change arrives mid-iteration
A requirement can be mandatory without making every implementation decision automatic. The challenge is finding the first move that creates a responsible plan.
Mandatory does not mean unexamined
When a compliance need appears late, the pressure to act can make analysis look like delay. But the team still needs to understand what must change, what it will affect, and who has authority over the resulting tradeoff.
Choose what the project manager should do first. Then open the walkthrough and compare the sequence behind each response.
Change control and delivery
A hybrid project is midway through a two-week iteration when the customer identifies a regulatory disclosure that must appear in the upcoming release. The product owner agrees it is mandatory. The team says adding it now requires removing another committed item, while the sponsor says to keep every commitment and include the disclosure. What should the project manager do first?
Choose a response to continue.
The strongest response is B
Clarify and assess a mandatory change before choosing how to absorb it. Develop feasible options with the people closest to the work, then use the agreed governance path for any tradeoff beyond their authority.
A. Decisive, but it assumes the solution
The requirement is important, but importance does not prove that overtime is feasible, safe, or authorized. This commits the team before the impact and options are understood.
B. Strongest response
This treats the disclosure as mandatory while still producing the information needed for a sound decision. The product owner and team can clarify the work, evaluate what must move, and identify whether a higher-level change decision is actually required.
C. The governance step comes too early
A formal decision may be necessary, but approvers need a defined change, impact, and set of options. Submitting first turns the process into a request without enough evidence.
D. It ignores the stated constraint
The customer has identified the disclosure as required for the upcoming release. Deferring it without analysis or authorization does not address the compliance need.
A mandatory requirement can tempt you to skip directly to overtime, escalation, or deferral. Those are decisions, not substitutes for understanding the change.
Impact analysis is part of acting quickly
The disclosure is mandatory, so ignoring it is not a viable option. That does not tell the team how to absorb the work or which commitment should move.
The project manager first helps the product owner and team turn the new requirement into clear work, assess the effect on the iteration and release, and identify feasible options. Any decision that exceeds their authority can then move through the agreed change path with useful evidence instead of a vague demand to do everything.
A decision pattern you can reuse
When a new requirement sounds nonnegotiable, separate four questions:
- What outcome is mandatory, and what details still need clarification?
- What is the impact on current work, schedule, cost, risk, and quality?
- Which options can the team and product owner resolve within their authority?
- Which remaining tradeoff requires formal approval or escalation?
See which traps repeat in your answers
One question can teach a decision pattern. Thirty answers can begin to show which patterns repeatedly pull you away from the strongest response.