rcode-correct-course

To document mid-sprint scope changes without losing accountability, analyze the trigger and cross-artifact impact, then generate a Sprint Change Proposal with explicit tradeoffs and approval requirements.

Impact analysis for a sprint change reviews ripple effects across PRD, epics, architecture, and UX artifacts, identifying what must be removed, deferred, or adjusted before implementation proceeds.

The best way to handle epic reordering during an active sprint is to capture the trigger, document cross-artifact impacts, compare adjustment and rollback options, and draft a structured proposal for stakeholder approval.

You need a sprint change proposal for technical blockers when a planned feature cannot be completed as designed, requiring documentation of what changed, what must be deferred, and who must approve the revised plan.

Yes, you can use this course correction process for stakeholder-driven requirement shifts by capturing the context, comparing MVP-scope and adjustment options, and producing a proposal with explicit tradeoffs and handoff details.