20 Retrospective Games and Ideas to Energise Your Team

Retrospective games are structured activities that turn a team’s lived experience of a sprint into honest reflection and concrete change. A good game gives people a clear frame — a metaphor, a set of prompts, a few columns — so the conversation goes somewhere instead of drifting. The right activity also does quiet work on psychological safety: when everyone writes at the same time and votes without their name attached, the loudest voice stops setting the agenda.

The 20 ideas below are grouped by purpose so you can pick one to match what your team needs this week. Where a format has a ready-made template, we have linked it — you can run any of these free in TeamRetro, with silent writing, anonymous voting and tracked actions built in. Throughout, “activities” and “exercises” mean the same thing as “games”: the label matters less than choosing a structure that fits.

What are retrospective games?

A retrospective game is simply a retrospective with a deliberate shape. Instead of asking “how did the sprint go?” and hoping for a reply, you give the team a frame — what should we start, stop and continue?, or what is pushing our boat forward and what is anchoring it? — that makes input easy to produce and easy to act on.

Reach for a game when a plain discussion would stall: after a hard sprint, when one or two people tend to dominate, or when the team has run the same format so many times it has gone stale. Keep it plain when the team is small, trusting and short on time — a five-minute Plus/Delta beats an elaborate metaphor nobody needs.

Quick and easy retrospective games

Low-prep formats for a short sprint or a 15-minute slot.

Plus/Delta — two columns: what went well (plus) and what you would change next time (delta). The fastest way to capture signal without ceremony. Run it with the Plus/Delta template.
Start, Stop, Continue — each person names one thing to start doing, one to stop, and one to keep. Action-oriented and ideal for steady teams. Use the Start, Stop, Continue template.
Rose, Bud, Thorn — a rose (a win), a bud (an emerging opportunity) and a thorn (a problem). A gentle, balanced check that surfaces both upside and risk. Try the Rose, Bud, Thorn template.
Plus, Minus, Interesting — sort observations into positives, negatives and the merely curious. The “interesting” column catches signals that are neither good nor bad yet. Run Plus, Minus, Interesting.

Classic agile retrospective formats

The evergreen named formats most agile teams reach for first.

Mad, Sad, Glad — capture what made the team angry, disappointed or pleased. It surfaces the emotional temperature after a tough sprint, which the action-only formats miss. Open the Mad, Sad, Glad template.
4Ls — Liked, Learned, Lacked, Longed For. A rounded review that pairs feelings with what the team learned and what was missing. Use the 4Ls template.
Starfish — five zones from “stop” through “less”, “keep”, “more” to “start”, so the team can dial activities up and down rather than only on or off. Run the Starfish template.
DAKI — Drop, Add, Keep, Improve. A crisp decision-led format that pushes the team to commit to changes, not just observe. Try the DAKI template.
KALM — Keep, Add, Less, More. A close cousin of Starfish that is quick to explain and easy to vote on. Use the KALM template.
Lean Coffee — build a quick agenda of topics the team votes on, then timebox a focused conversation through each in turn. We do not template Lean Coffee, so generate a custom board for it instead.

Fun and creative retrospective games

Metaphor-led formats that lift engagement without losing rigour.

Sailboat — draw a boat with wind (what propels you), an anchor (what holds you back), rocks (risks) and an island (the goal). The single picture makes a rich discussion accessible to everyone. Open the Sailboat template.
Speed Car — an engine pushing the team forward and a parachute dragging it back. A fast, visual cousin of the Sailboat for teams who want momentum framing. Generate a Speed Car board to run it.
Hot Air Balloon — hot air lifting the balloon, sandbags weighing it down, and storms on the horizon. A friendly metaphor for what raises and lowers the team’s altitude. Create a Hot Air Balloon board.
RPG retrospective — frame the sprint as a quest: who were the heroes, what were the monsters, what loot did you gather? Playful, and surprisingly good at naming hidden wins. Run the RPG retrospective template.

Online and remote retrospective games

Activities built for distributed teams — everyone contributes at once, on a shared board, and you can run all of them free online.

Kudo Cards — each person writes a short, specific thank-you to a teammate. A warm, low-effort way to close a remote session on a high note. Generate a Kudo Cards board to run it.
Letter to your future self — everyone writes a note to the team they will be next sprint: what to remember, what to watch for. Revisit it at the next retro. Create a board for it.
Emoji or energy-levels check-in — open by asking each person for one emoji, or a number from one to five, to describe their week. A 60-second read of the room before the work begins. Build a check-in board.
Online Lean Coffee — Lean Coffee works well remotely: collect topics on a shared board, dot-vote, then timebox each. Generate a Lean Coffee board.

Problem-solving and deep-dive retrospectives

Analytical formats for when the team needs to get to a root cause, not just vent.

SWOT analysis — map Strengths, Weaknesses, Opportunities and Threats. Useful at a milestone or quarter boundary when the team is reflecting on more than one sprint. Run the SWOT analysis template.
Fishbone (Ishikawa) — work backwards from a problem to its contributing causes, grouped into categories, until the real driver is visible. Use the Fishbone template.
Five Whys — take one recurring problem and ask “why” repeatedly until you reach a cause the team can actually change. A surface symptom such as flaky CI usually hides a deeper, fixable one. Generate a Five Whys board.
Sprint retrospective — the general-purpose agile review at the end of an iteration. When you want a balanced, repeatable format rather than a themed game, start from the agile retrospective template.

Team-bonding and icebreaker games

Short openers that build trust before the reflection begins.

Fun fact / Two truths and a lie — each person shares a few facts about themselves, one of which is false, and the team guesses. A light way to start that works just as well remotely.
Snapshot — everyone shares one photo or one word that sums up their sprint, then says a sentence about it. Quick, personal, and easy on a video call.
A pet for our team — the team invents a mascot animal for the sprint and explains why. A creative warm-up that doubles as a read on morale.

These openers need no template — run them as a quick round before any of the formats above, or generate a custom check-in board to capture the answers.

How to run a retrospective game

The format matters less than the facilitation around it. A simple arc works for almost any game on this page:

Set the stage. Open with a short check-in and a reminder that everyone did their best with what they knew. Keep it under five minutes.
Gather data. Give the team quiet time to add their own notes before anyone speaks.
Generate insights. Group related notes, dot-vote on what matters most, then dig into the top items together.
Decide actions. Turn insight into one or two specific changes, each with a single named owner and a date.
Close. End on kudos, and review last retro’s actions at the start of the next one — follow-through is what teaches a team that retros are worth the time.

For remote teams, lean on anonymous voting and silent writing even harder: they level the playing field when you cannot read the room as easily.

Run any of these free in TeamRetro

Every format above runs free in TeamRetro, with silent brainstorming, anonymous voting and tracked actions out of the box. Browse all retrospective templates to find a ready-made board, or, for a game we do not template, generate a custom retrospective in seconds and run it with your team today.

Frequently asked questions

What are good retrospective games?

Good retrospective games are structured activities that help a team reflect on how they worked and decide what to change. Reliable starting points include Start, Stop, Continue; Mad, Sad, Glad; the Sailboat; the 4Ls; and the Starfish — each gives people a clear frame for honest feedback rather than an open-ended discussion.

What are some online retrospective games?

Most retrospective games work online when you run them on a shared board with silent writing and dot-voting. Kudo Cards, an emoji or energy-levels check-in, a Letter to Your Future Self, and online Lean Coffee all suit distributed teams. In TeamRetro everyone adds notes at the same time and votes anonymously, so a remote session feels the same as an in-person one.

How do you make a retrospective fun?

Use a metaphor-led format such as the Sailboat, Speed Car or Hot Air Balloon, open with a short check-in question, timebox each step, and close on kudos. Fun comes from a safe, well-paced session where people are genuinely heard — not from gimmicks bolted onto a status meeting.

What is a good retrospective game for remote teams?

The Sailboat and Start, Stop, Continue both translate well to remote teams because they give a clear shared picture and short, votable input. Pair either with an emoji check-in to read the room, and run it on a tool where everyone writes at once and votes anonymously so the loudest voice does not anchor the discussion.

How long should a retrospective game take?

A focused retrospective game runs in 30 to 60 minutes for most teams. Quick formats such as Plus/Delta fit a 15-minute slot after a short sprint; deeper problem-solving sessions like a Fishbone or root-cause analysis can take an hour. Timebox each phase so you always reach agreed actions before you close.