gds-correct-course

To manage significant sprint changes, you need a structured workflow that surfaces impact across epics, architecture, and documentation. This Skill coordinates analysis and handoffs to keep projects on track by generating a formal Sprint Change Proposal.

A Sprint Change Proposal is a formal document recording decisions and actions for significant sprint adjustments. You need one when triggering issues require cross-artifact impact analysis across epics, architecture, UX, and documentation to determine a viable path forward.

You assess sprint change impact by performing cross-artifact analysis that identifies affected epics, stories, architecture, and documents. This Skill guides the analysis to understand ripple effects and rationalize evidence-based options like direct adjustment, rollback, or MVP redefinition.

You coordinate stakeholder alignment by assigning clear roles, approvals, and next steps within a formal Sprint Change Proposal. This Skill ensures implementation handoffs are explicitly documented to maintain governance and alignment across teams.

Yes, the workflow supports evaluating rollback versus MVP redefinition by providing evidence-based options with pros and cons. It rationalizes decision-making to help you choose between direct adjustment, rollback, or MVP redefinition during a significant sprint change.

The best way to document implementation handoffs is to generate a formal Sprint Change Proposal that assigns specific roles, approvals, and next steps. This Skill outputs the structured document needed to ensure alignment and record decisions for significant sprint changes.