Guide
What is an agile retrospective?
An agile retrospective is a recurring team meeting — usually at the end of a sprint or iteration — where the team reflects on how it worked, decides what to change, and commits to specific improvements. It's the mechanism agile teams use to inspect and adapt their own process, not just their product.
Why retrospectives matter
The retrospective is the only ceremony whose entire job is making the team itself better. Done well, it converts frustration into experiments: unclear ownership becomes a working agreement, a recurring blocker becomes an action item with a name on it. Done poorly, it becomes a venting session whose sticky notes never survive the meeting — the most common reason teams quietly stop holding them.
Common formats
Start / Stop / Continue
The workhorse. What should we start doing, stop doing, keep doing? Fast to run, easy to turn into actions.
Glad / Sad / Mad
Emotion-first framing that surfaces how the sprint actually felt — useful when morale is the signal.
Starfish
Five zones — keep, more of, less of, start, stop — when plain start/stop flattens too much nuance.
Sailboat
Wind, anchors, rocks, and the island: a metaphor for momentum, drag, risks, and the goal.
The format matters less than what survives the meeting. Any of these works if actions leave with owners. Full prompts and facilitation notes live in the retrospective templates library; running on a sprint cadence? See the sprint retrospective guide .
The ordinary failure modes
-
Opinion theater. The loudest memory wins because nobody has evidence. The sprint's actual friction — visible in Slack threads and tracker churn — never makes it to the board.
-
Action items that expire. Improvements get agreed, nobody owns them, and by the next retro no one remembers they existed.
-
Groundhog-day retros. The same theme surfaces sprint after sprint, but without cross-cycle memory nobody can prove it's the third time — so it never escalates.
Fixing the failure modes is the whole product
SmartRetro is a retrospective tool built around exactly these three failures: it gathers evidence between retros so discussion starts from signal, keeps action items owned and visible until they move, and remembers what came up before. The AI side of the tool detects, surfaces, and recommends — your team decides and acts.