---
name: Retrospective
description: Learn from each cycle.
---
# Retrospective

A retro converts experience into improvement. Without it, the same mistakes recur indefinitely because nobody extracted the lesson.

## Format
- **What went well.** Name it; reinforce it.
- **What didn't.** Specific, not blameful. "Estimates were off by 2×" — not "the team is bad at estimating".
- **What to change.** One or two concrete actions for next cycle, with an owner. Not a wish list of twenty.

## Discipline
- **Blameless.** People hide problems in a blameful culture, and the problems recur hidden.
- **Action-oriented.** A retro whose actions don't get done breeds cynicism. Track them; close them next retro.
- **Small and frequent** beats large and rare. Monthly 30-min retros surface things while they're still fixable.