Rewritten
Sprint Retrospective: Checkout Redesign
1. Quick Check-In
How's everyone feeling coming out of this sprint?
2. What Went Well
Celebrate shipping the checkout redesign on time.
3. What Was Challenging
Discuss the last-minute scope changes and the stress they caused.
4. Root Cause Discussion
Why did scope change late, and what could catch this earlier next time?
5. Action Items
Agree on 1-2 concrete changes to try in the next sprint.
About this tool
A retrospective only works if it has enough structure to get past surface-level "it went fine" comments and into what actually helped or hurt the team during a sprint or project. This tool builds a retro agenda tuned to that reflective format — what went well, what didn't, and what to change — using whatever context you provide about the sprint or project just completed. It's the most reflection-oriented agenda tool in this batch, distinct from the kickoff generator, which looks forward to a new project rather than back at a finished one.
Frequently asked questions
Does it follow a specific retro framework, like Start-Stop-Continue?+
It defaults to a went-well / didn't-go-well / action-items structure, but you can mention a specific framework like Start-Stop-Continue in your input and it will adapt.
Will it name specific people responsible for what went wrong?+
No, it keeps the tone focused on processes and outcomes rather than assigning individual blame, which tends to produce a more productive retro.
Can I use this for a project retro, not just a sprint?+
Yes, it works for any completed chunk of work, whether that's a two-week sprint, a full project, or a single product launch.