Leadership & Delivery
Project Scope Changes: How to Give a Sponsor a Real Choice
Present a project scope change with credible alternatives, delivery impact, and a clear sponsor decision.
Accumentum® ·
Present the sponsor with a baseline, a scope exchange, and a timing option. Explain the benefit, dependency, acceptance criteria, and decision deadline for each viable choice.
A sponsor asks for live chat six weeks before a customer portal launches. The team is at capacity, a critical integration is still being tested, and the feature is described as "small." The project manager's responsibility is not to say yes or no instantly. It is to translate the request into an impact-based decision that the sponsor can approve with eyes open.
Clarify the business outcome the sponsor wants rather than treating a proposed feature as the only solution. Estimate scope, dependencies, testing, support, security, cost, and delivery risk. Compare alternatives including deferral, a restricted pilot, or a scope trade. Apply the project's agreed change process and identify who holds authority over budget, scope, and timeline.
How to practice
- Clarify value: Ask which customer need, commitment, or outcome the new request serves.
- Size the change: Obtain delivery, security, operations, and acceptance estimates from responsible owners.
- Offer alternatives: Compare the current baseline, a tradeoff, phased delivery, and a formal schedule change.
- Record authority: Document the recommendation, sponsor decision, updated baseline, and acceptance criteria.
The workplace scenario
Instead of saying "we can add chat," show three options. Option A preserves launch scope and schedules chat for a later release. Option B exchanges a lower-value feature for a bounded chat pilot with acceptance tests. Option C adds capacity and moves the release if justified. The sponsor chooses against explicit impacts, and the team receives a documented commitment rather than a hallway promise.
Price the change in the constraint the sponsor owns
A sponsor wants a new approval screen in a release with ten working days left. The team estimates four days of development and two days of testing. Six days of effort does not necessarily mean a six-day delay. Ask whether the people are available, whether testing can overlap other work, and whether the change requires another approval. A specialist who is available only on the last two days can determine the release date even when total team capacity looks adequate.
Present three credible choices for the fictional case. Keep the baseline and deliver the screen later. Exchange an existing feature of comparable effort after checking dependency and benefit impacts. Or move the release and preserve both features. For each option, identify who receives the benefit, what acceptance evidence changes, and which estimate remains uncertain. If the sponsor’s request addresses a mandatory requirement, establish that fact with its owner before treating deferral as viable.
Record the decision in a sentence
“By Thursday the sponsor will choose whether to move the release or exchange the export feature for the approval screen, after the test lead confirms the regression window.” This makes the deadline meaningful. After approval, update the baseline, acceptance criteria, and affected owners. A positive conversation with the sponsor is only the start of implementing the decision.
A common mistake
Do not label an unapproved change green simply because individual teams have started the work. Likewise, avoid hiding contingency or treating overtime as a substitute for capacity planning. The choice must show effects on user acceptance, dependencies, and risk.
Try it yourself
Draft a one-page change brief: requested outcome, baseline, three options, impact estimates, decision owner, deadline, and acceptance test. Deliver a ninety-second recommendation without assigning blame for the request.
Should every small change go through formal approval?
Use the project's change thresholds and governance model. The discipline is to keep authority, impact, and baselines explicit, not to create bureaucracy for its own sake.
Put it into practice
PathHire's Project Manager pathway includes late-scope-change scenarios. Accumentum PMP and CAPM preparation can reinforce current project management practices.