Correct Course - Sprint Change Management Instructions

The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml

Confirm change trigger and gather user description of the issue Ask: “What specific issue or change has been identified that requires navigation?” Verify access to required project documents: - PRD (Product Requirements Document) - Current Epics and Stories - Architecture documentation - UI/UX specifications Ask user for mode preference: - Incremental (recommended): Refine each edit collaboratively - Batch: Present all changes at once for review Store mode selection for use throughout workflow

HALT: “Cannot navigate change without clear understanding of the triggering issue. Please provide specific details about what needs to change and why.”

HALT: “Need access to project documents (PRD, Epics, Architecture, UI/UX) to assess change impact. Please ensure these documents are accessible.”

Load and execute the systematic analysis from: {project-root}/bmad/bmm/workflows/4-implementation/correct-course/checklist.md Work through each checklist section interactively with the user Record status for each checklist item: - [x] Done - Item completed successfully - [N/A] Skip - Item not applicable to this change - [!] Action-needed - Item requires attention or follow-up Maintain running notes of findings and impacts discovered Present checklist progress after each major section

Identify blocking issues and work with user to resolve before continuing

Based on checklist findings, create explicit edit proposals for each identified artifact

For Story changes:

• Show old → new text format
• Include story ID and section being modified
• Provide rationale for each change

• Example format:

  Story: [STORY-123] User Authentication
  Section: Acceptance Criteria
  
  OLD:
  - User can log in with email/password
  
  NEW:
  - User can log in with email/password
  - User can enable 2FA via authenticator app
  
  Rationale: Security requirement identified during implementation
  

For PRD modifications:

• Specify exact sections to update
• Show current content and proposed changes
• Explain impact on MVP scope and requirements

For Architecture changes:

• Identify affected components, patterns, or technology choices
• Describe diagram updates needed
• Note any ripple effects on other components

For UI/UX specification updates:

• Reference specific screens or components
• Show wireframe or flow changes needed
• Connect changes to user experience impact

Present each edit proposal individually Review and refine this change? Options: Approve [a], Edit [e], Skip [s] Iterate on each proposal based on user feedback

Collect all edit proposals and present together at end of step

Compile comprehensive Sprint Change Proposal document with following sections:

Section 1: Issue Summary

• Clear problem statement describing what triggered the change
• Context about when/how the issue was discovered
• Evidence or examples demonstrating the issue

Section 2: Impact Analysis

• Epic Impact: Which epics are affected and how
• Story Impact: Current and future stories requiring changes
• Artifact Conflicts: PRD, Architecture, UI/UX documents needing updates
• Technical Impact: Code, infrastructure, or deployment implications

Section 3: Recommended Approach

• Present chosen path forward from checklist evaluation:
  • Direct Adjustment: Modify/add stories within existing plan
  • Potential Rollback: Revert completed work to simplify resolution
  • MVP Review: Reduce scope or modify goals
• Provide clear rationale for recommendation
• Include effort estimate, risk assessment, and timeline impact

Section 4: Detailed Change Proposals

• Include all refined edit proposals from Step 3
• Group by artifact type (Stories, PRD, Architecture, UI/UX)
• Ensure each change includes before/after and justification

Section 5: Implementation Handoff

• Categorize change scope:
  • Minor: Direct implementation by dev team
  • Moderate: Backlog reorganization needed (PO/SM)
  • Major: Fundamental replan required (PM/Architect)
• Specify handoff recipients and their responsibilities
• Define success criteria for implementation

Present complete Sprint Change Proposal to user Review complete proposal. Continue [c] or Edit [e]?

Get explicit user approval for complete proposal Do you approve this Sprint Change Proposal for implementation? (yes/no/revise)

Gather specific feedback on what needs adjustment Return to appropriate step to address concerns If changes needed to edit proposals If changes needed to overall proposal structure

Finalize Sprint Change Proposal document Determine change scope classification:

• Minor: Can be implemented directly by development team
• Moderate: Requires backlog reorganization and PO/SM coordination
• Major: Needs fundamental replan with PM/Architect involvement

Provide appropriate handoff based on scope:

Route to: Development team for direct implementation Deliverables: Finalized edit proposals and implementation tasks

Route to: Product Owner / Scrum Master agents Deliverables: Sprint Change Proposal + backlog reorganization plan

Route to: Product Manager / Solution Architect Deliverables: Complete Sprint Change Proposal + escalation notice

Confirm handoff completion and next steps with user Document handoff in workflow execution log

Summarize workflow execution: - Issue addressed: {{change_trigger}} - Change scope: {{scope_classification}} - Artifacts modified: {{list_of_artifacts}} - Routed to: {{handoff_recipients}}

Confirm all deliverables produced:

• Sprint Change Proposal document
• Specific edit proposals with before/after
• Implementation handoff plan

Report workflow completion to user Remind user of success criteria and next steps for implementation team