bmad-gds-correct-course

To analyze sprint changes across cross-functional teams, you need a structured workflow that assesses impacts on timelines, capacity, and deliverables while generating risk registers and stakeholder communications to minimize miscommunication.

The best way to plan for mid-sprint scope changes is to generate a corrective-course plan that maps tasks, owners, and deadlines, ensuring cross-team alignment through structured impact analysis and concise change plans.

Yes, you can automate stakeholder communication by running a workflow that analyzes sprint modifications and produces aligned planning artifacts, including risk registers and concise change updates for all affected parties.

To assess risks of modifying sprint deliverables, execute a corrective-course workflow that evaluates cascading changes across product, design, and engineering teams, outputting a detailed risk register and impact analysis.

No, this sprint planning workflow does not require external dependencies, as it independently loads and executes its designated production configuration to generate change plans and impact analyses without additional components.

You need a corrective-course plan for project management when a sprint change requires cross-team coordination, causing potential cascading impacts across timelines and capacity that demand structured alignment and risk documentation.