When a late-breaking requirement changes scope, what sequence best preserves trust and manages risk?

• A. Ignore the change and continue as planned.
• B. Assess impact, prepare a concise risk update, choose appropriate channel, explain options, maintain transparency, document decisions, and monitor.
• C. Rework everything immediately without communicating.
• D. Only inform the sponsor, not team.

Answer: (B)

When a late-breaking requirement changes scope, the key is to handle it with a structured, transparent process that balances risk with stakeholder trust. Start by assessing the impact to understand how the change affects schedule, budget, resources, and quality. This gives a factual basis for any decision and helps avoid surprises. Next, prepare a concise risk update that clearly outlines potential consequences and their likelihood so everyone sees the real magnitude of the change. Then choose the appropriate channel to communicate, ensuring the right people receive the right level of detail in the right format. After that, explain the options and trade-offs to stakeholders, so the team can decide together rather than be forced into a single path. Maintaining transparency throughout this dialogue builds trust and keeps alignment strong. Document the decisions and the rationale so there’s a traceable record for future reference and accountability. Finally, monitor the implemented change to catch new risks or unintended effects and adjust as needed.

Ignoring the change or reworking everything without communication undermines trust and increases risk, while informing only the sponsor leaves the team in the dark and creates misalignment. This sequence combines evaluation, open communication, and documentation to preserve trust while effectively managing risk.