Agile Retrospective Ideas: 18 Formats for Scrum, Kanban, Scrumban & SAFe
Most "retro ideas" lists treat agile like it's one thing. It isn't. A scrum team wrapping a two-week sprint needs a different conversation than a kanban team that's been streaming work for six months, and both look nothing like a SAFe Inspect & Adapt workshop. This guide catalogues 18 retrospective formats grouped by agile flavor, with guidance on when each one actually helps.
Why the agile flavor matters
A retrospective's job is always the same: surface what's working, surface what's getting in the way, and leave with a few small commitments. What changes between agile flavors is the cadence, the unit of work, and the governance overhead around the team. Those three things should push you toward different formats.
- Scrum retros happen on a fixed sprint cadence. The unit of work is the sprint goal, and there's almost always a known facilitator (the scrum master). Activities can lean on the sprint as a shared frame.
- Kanban teams don't have sprints. The unit of work is the flow itself: lead time, WIP, blocked time. Retros are usually monthly or triggered by a service-delivery review, and activities should pull from the board data, not from "this sprint we…".
- Scrumban sits in the middle. There's a cadence (often two weeks) but no sprint commitment. Retros mix sprint-style reflection with flow-based metrics.
- SAFe retros happen at two levels: team-level (looks scrum-like) and Inspect & Adapt at the end of each Program Increment (8–12 weeks, multi-team, often 50+ people). Different formats are needed at each level.
With that frame in place, here's a working catalogue. Each format includes when to use it, how long to budget, and the variant you'd switch to for a brand-new team versus a team that's been together for a year.
Scrum retrospective ideas
1. Start / Stop / Continue
Scrum15–30 minAll agesThree columns. Cards go in based on what the team should start doing, stop doing, or continue. It's the smallest possible useful retro and a great default when sprints have been uneventful.
New team: facilitator collects cards silently to avoid groupthink, then reveals together.
Long-running team: compare against last sprint's "Continue" column. Anything that fell off?
2. Mad / Sad / Glad
Scrum30 minThree emotional columns. People drop cards into whichever bucket matches how the sprint felt. Good for teams where the sprint numbers looked fine but morale didn't.
Pitfall: can flatten into venting. Pair with a "what's one thing we'll change?" round at the end.
3. Sailboat (Wind / Anchors / Rocks / Island)
Scrum45–60 minA sailboat metaphor: Wind (what's pushing us forward), Anchors (what's holding us back), Rocks (risks ahead), Island (the goal). Works well when the team needs to reconnect long-term vision to short-term work.
When to skip: if the team is exhausted, the metaphor adds cognitive load. Use a simpler format.
4. 4Ls (Liked / Learned / Lacked / Longed For)
Scrum30–45 minA richer alternative to Start/Stop/Continue. "Learned" is the column most teams skip; force them not to. The "Longed For" column surfaces capability gaps (tooling, skills, access) that don't show up in sprint reviews.
5. The 5 Whys
Scrum45 minRoot causePick the most painful incident from the sprint. Ask "why?" five times in sequence. Designed for postmortems and missed-commitment retros. Overkill for routine ones.
Kanban retrospective ideas
Kanban retros need to talk about flow, not sprint outcomes. The board is your primary artifact. If you came up through scrum and feel adrift without a sprint goal, this is the most important adjustment to make.
6. Flow Retrospective (Cycle Time + Throughput)
Kanban45 minPull the last 30 days of cycle-time and throughput data before the meeting. Plot them. Discuss what changed and why. Items that took dramatically longer than peers are conversation seeds, not blame opportunities.
See our kanban retrospective template for a reusable board layout.
7. Bottleneck Hunt
Kanban30 minOne column on the board: "Where did work pile up this month?" Team members add columns or sub-states where they personally felt blocked. The cluster pattern usually points to a real systemic constraint (code review, QA handoff, design dependency).
8. WIP Limit Review
Kanban20–30 minA focused mini-retro: are the WIP limits still right? For each column, ask "did we hit the limit? did hitting it help or hurt?" Adjust on the spot. Excellent for newly-formed kanban teams in their first quarter.
9. Class-of-Service Audit
Kanban45 minMature teamsIf your team uses Expedite / Fixed-Date / Standard / Intangible classes of service, audit the last month: what got expedited, was it actually urgent, and what did it cost the standard queue? Excellent quarterly cadence.
Scrumban retrospective ideas
Scrumban teams should run retros that blend: half about the cadence/people, half about the flow.
10. The Two-Pane Retro
Scrumban45–60 minSplit the board into two halves: People & Process (sprint-flavor questions) and Flow & Board (kanban-flavor metrics). Time-box each half equally. Forces the team not to drift entirely into one mode.
11. Cadence Calibration
Scrumban30 minScrumban teams often inherit two-week cadences from a previous scrum era and never question whether they still fit. Once a quarter, dedicate a retro to "is our cadence still the right one?" Meeting load, planning accuracy, demo-ability.
SAFe retrospective ideas
12. Iteration Retrospective (Team Level)
SAFe30–60 minAt the team level, SAFe iteration retros look almost identical to scrum retros. Any of formats #1–#5 work. The only addition: also reflect on commitments made to other teams in the ART (Agile Release Train).
13. Inspect & Adapt: Problem-Solving Workshop
SAFe3–4 hoursWhole ARTThe signature SAFe retrospective. Multi-team, end-of-PI. Use a structured root-cause analysis (fishbone, 5-whys, or Pareto) on the top systemic issue from the PI demo and metrics review.
A facilitated online board with named columns per team is invaluable here. Co-located rooms with sticky notes don't scale past about 30 people.
14. Quantitative Measurement Review
SAFe60 minWalk through PI predictability, business value achieved per team, and DORA metrics if you have them. Pair this before the qualitative retros so the conversation is anchored in data, not opinion.
Universal formats that work across flavors
15. The Plus / Delta
All15 minTwo columns. What worked (+). What we'd change next time (Δ). The fastest useful retro format on the planet, perfect for the last 15 minutes of an iteration ceremony when you forgot to schedule one.
16. Lean Coffee Retrospective
All45 minTeam writes topics on cards, dot-votes the top 3–5, and discusses each one in time-boxed rounds (8 minutes each, "thumbs up to continue, thumbs down to move on"). Excellent for teams where the same loud voices dominate traditional retros.
17. Appreciation Retrospective
All20 minEveryone names something each teammate did that they appreciated. Schedule once a quarter, never more than that. Powerful for teams that have been through a tough delivery period.
18. Async / Written Retrospective
All2–3 days asynchronousRemote teamsOpen a retrospective board on Monday, close it Wednesday, then run a 30-minute synchronous discussion on the top items. Doubles useful input from teams with quieter members or across time zones. See retrospective ideas for remote teams for more remote-specific patterns.
Format chooser (which one, when)
| If your team is… | Try this format |
|---|---|
| Brand new (sprint 1–4) | Start / Stop / Continue (#1) |
| Tired and quiet | Mad / Sad / Glad (#2) |
| Drifting from product strategy | Sailboat (#3) |
| Stuck repeating the same issues | 5 Whys (#5) |
| Kanban with no sprint frame | Flow Retrospective (#6) or Bottleneck Hunt (#7) |
| Adjusting kanban for the first time | WIP Limit Review (#8) |
| Scrumban (half-flavor) | Two-Pane (#10) |
| End of a SAFe PI | Inspect & Adapt (#13) |
| Out of time | Plus / Delta (#15) |
| Dominated by a few loud voices | Lean Coffee (#16) |
| Distributed across time zones | Async retrospective (#18) |
New teams vs. long-running teams
The same format hits differently depending on team age. A few principles:
For new teams (first 3 months)
- Bias toward structure. Start / Stop / Continue and 4Ls give psychological safety because everyone knows what's expected.
- Anonymize early on. Use a tool where cards are masked from teammates until reveal. People will write things they'd never say.
- Time-box action items aggressively. Pick one. Just one. Make sure it's done by next retro before you generate more.
For long-running teams (12+ months)
- Rotate formats. Doing the same retro for a year is how teams stop attending mentally. Pick a 4-week rotation across format families.
- Compare to history. "We said this 3 months ago. Did it stick?" is the highest-leverage question a long-running team can ask itself.
- Schedule appreciation retros. Long-running teams accumulate quiet resentments. Format #17 once a quarter discharges them.
Facilitation tips that travel across formats
- Silent writing first. Always 5 minutes of silent card writing before any discussion. The loudest voice should not seed the conversation.
- Reveal once, not card-by-card. When you reveal cards, reveal them all at once. The pattern in the cluster is more informative than any single card.
- Dot-vote before discussing. Three dots per person, vote on what to discuss. You will never get through every card; pick the ones the team cares about.
- One action item per session. Five action items means zero next retro. Pick one, name an owner, set a date.
- Close with a temperature check. 1–5 on "how do you feel leaving this retro?". Watch the trend over time, not the absolute number.
Where to go next
If you're looking for a starting point on a specific flavor, jump straight to:
- Sprint retrospective ideas: the scrum-specific version of this catalogue.
- Team retrospective ideas: focused on people and team health over methodology.
- Kanban retrospective template: a ready-to-use board layout for kanban teams.
- Retrospective ideas for remote teams: async- and timezone-aware formats.