Start/Stop/Continue, Mad/Sad/Glad, 4Ls, Sailboat, Five Whys, or Lean Coffee? Answer 6 questions about your last sprint and team state — get a recommendation with run-of-meeting steps and watchouts.
Question 1 of 6
The default. Three columns, low cognitive load. Best for first-time retros, large teams, or when nothing specific went wrong.
Surfaces morale before facts. Best after a rough sprint or when restarting retro practice with low team energy.
More structured than Start/Stop/Continue. Forces reflection on growth, not just behaviour.
Forward-looking. Best at end of release cycle or before a new initiative — vision, drag, risks, goal.
Root-cause for one specific failure. Best when action items keep recurring or after an incident.
Open agenda, dot-voted, time-boxed. Best for small teams who self-organise well.
Full cluster: retro formats, action tracker, why retros die, sprint review without theatre.
Open the toolkitMarkdown template that survives across sprints. Owners, due dates, status — and a kill-list for items that keep slipping.
Open templateThe format is rarely the problem. Read this if your action items never land.
ReadSprintFlint records action items as tickets, tracks them across sprints, and surfaces the ones that keep slipping. The retro becomes a system, not a meeting.
SprintFlint surfaces velocity, capacity, burndown, and cycle time automatically — no calculator, no spreadsheet, no plugin maze. Free for the first 300 tickets. No credit card.