bmad-correct-course

Manage significant sprint changes by analyzing cross-artifact impacts on PRD, epics, architecture, and UX to produce a structured Sprint Change Proposal. This ensures safe handling of deviations through systematic context gathering and stakeholder alignment.

Assess downstream impacts of a sprint deviation by loading project artifacts to evaluate implications across requirements, architecture, UI/UX, testing, and deployment. This cross-artifact analysis identifies dependencies and informs the recommended path forward.

You need a formal Sprint Change Proposal when sprint deviations are significant enough to affect PRD, epics, architecture, or UX plans. It documents the trigger, defines scope, and secures explicit stakeholder approval before proceeding with the change.

Coordinate change management handoffs by generating a concrete proposal with a recommended path, dependencies, and handoff plan. This structured approach aligns stakeholders and documents transitions to minimize disruption to the current sprint.

Document stakeholder approval for sprint scope modifications by following a procedural workflow that loads project documents, assesses implications, proposes options, and secures explicit approval. The resulting Sprint Change Proposal serves as the formal record.

Informal sprint change management lacks systematic cross-artifact impact analysis and documented handoffs, risking misalignment across PRD, epics, architecture, and UX. Significant deviations require structured procedural handling to secure explicit stakeholder approval and maintain project integrity.