AI_SCRUM/process/05_sprint_retrospective.md

Process: Sprint Retrospective

Primary agent: .claude/agents/scrum-master.md

When to run

At the end of every sprint, after the Sprint Review.

Steps

1. Gather objective signals (velocity, burndown, defects, cycle time) and subjective signals (team input) from the sprint.
2. Surface patterns/insights together as a team, using templates/retrospective_template.md.
3. Prioritize a small number of insights (e.g., quick voting) rather than trying to address everything.
4. Commit to concrete, actionable items for the next sprint.
5. Add the agreed actions directly into the next sprint's plan/backlog — not a separate document.
6. Keep a running list of lower-priority improvement ideas for later.
7. Check whether prior retro actions were actually followed through; call it out if not.
8. Run process/07_process_improvement.md as a final pass: separate any insight about the Scrum kit itself (the process/templates/agents in this repo) from insights about how this team works, and log the former to logs/process_improvement_log.md instead of the sprint plan.

Exit criteria

• A short, prioritized list of concrete actions exists and is scheduled into the next sprint.
• Kit-level insights (if any) are logged in logs/process_improvement_log.md, not silently dropped or mixed into the team's own action items.

On completion: update state.md — phase → 1 (Backlog refinement) for the next sprint cycle, leading agent → product-owner, next action → fold retro actions into backlog refinement/next sprint planning. This is a natural pause point; confirm with the user before starting the next sprint.