Business
Sprint Retrospective Generator
A sprint retrospective generator gives you ready-made prompts for running a focused, engaging retro in one of five proven formats. Pick the format — Start/Stop/Continue, Glad/Sad/Mad, 4Ls, Sailboat, or What-went-well — and it returns the questions to guide the discussion, ending with a prompt to commit to action items. Scrum masters, team leads, and agile teams use retros to inspect how the last sprint went, surface what is helping and hindering, and agree concrete improvements for the next one. Varying the format keeps retros fresh so the team engages instead of going through the motions — each lens surfaces different insights, whether focused on emotions, learnings, risks, or behaviours. Always close by committing to one or two owned, time-boxed actions rather than a long wish list.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick a retrospective format.
- Click Generate to see the prompts.
- Work through each prompt as a team.
- Commit to one or two owned, time-boxed actions.
Use Cases
- •Running a sprint retrospective with a clear structure
- •Varying the retro format to keep the team engaged
- •Surfacing what helped and hindered the sprint
- •Guiding a team toward concrete action items
- •Giving a new scrum master ready-made prompts
Tips
- →Rotate formats so retros stay fresh.
- →Make it safe to speak honestly.
- →Focus on the process, not blaming people.
- →End with a couple of owned, dated action items.
FAQ
Why vary the retrospective format?
Running the same retro every sprint makes the team disengage and answer on autopilot. Different formats — emotional, learning-focused, risk-focused — surface different insights and keep the session fresh, honest, and genuinely useful.
What is the Sailboat format?
A visual retro where wind represents what pushed the team forward, anchors what held it back, rocks are risks ahead, and the island is the goal. The metaphor makes it easy and slightly fun to discuss progress and obstacles, which often loosens up a quieter team.
How do we make retrospectives actually improve things?
End every retro by committing to one or two specific actions, each with an owner and a deadline. A long list of vague ideas changes nothing; a couple of owned, time-boxed improvements reviewed at the next retro is what drives real, sustained progress.
What is the difference between 4Ls and Start/Stop/Continue?
4Ls (Liked, Learned, Lacked, Longed for) is learning-focused and draws out what the team took away from the sprint. Start/Stop/Continue is behaviour-focused and drives direct changes to team practices. Use 4Ls after a sprint with new challenges, and Start/Stop/Continue when you want crisp, actionable behaviour change.
How long should a sprint retrospective take?
Scrum recommends a maximum of three hours for a one-month sprint, proportionally shorter for shorter sprints — roughly 45 minutes to 1.5 hours for two-week sprints. Keeping it time-boxed forces the team to prioritise what really matters rather than airing every grievance.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.