A sprint retrospective template generator is a free tool that creates a structured agenda for your team's end-of-sprint reflection meeting. It produces timeboxed sections, format-specific prompts, and an action item tracker you can export as markdown.
1. Set the stage
5 min2. Icebreaker
5 min3. Gather data: Start
11 min4. Gather data: Stop
11 min5. Gather data: Continue
11 min6. Group, theme, and vote
8 min7. Action items
7 min8. Close
2 min| Owner | Action | Due | Status |
|---|---|---|---|
| Name | What will be done | YYYY-MM-DD | Open |
| Name | What will be done | YYYY-MM-DD | Open |
| Name | What will be done | YYYY-MM-DD | Open |
Start/Stop/Continue is best for teams that want clear, action-oriented outcomes. Push for specific, observable behaviors in each bucket rather than vague goals.
Paste this directly into Notion, Confluence, GitHub, or any markdown-aware tool.
# Sprint Retrospective Retrospective **Format:** Start / Stop / Continue **Sprint length:** 2 weeks **Total time:** 60 minutes **Team size:** 6 **Mode:** Remote **Date:** _YYYY-MM-DD_ **Facilitator:** _Name_ **Attendees:** _List names here_ > Classic action-oriented retro. Three buckets that lead naturally to commitments. ## Agenda | # | Section | Time | | - | ------- | ---- | | 1 | Set the stage | 5 min | | 2 | Icebreaker | 5 min | | 3 | Gather data: Start | 11 min | | 4 | Gather data: Stop | 11 min | | 5 | Gather data: Continue | 11 min | | 6 | Group, theme, and vote | 8 min | | 7 | Action items | 7 min | | 8 | Close | 2 min | ### 1. Set the stage (5 min) - Welcome the team and remind everyone of the prime directive: assume good intent. - Restate the sprint goal and what was actually delivered. - Confirm the format and timebox so people know what to expect. ### 2. Icebreaker (5 min) - One word to describe how this sprint felt - go around the room. - Optional: share a small win, personal or professional, from the past two weeks. ### 3. Gather data: Start (11 min) - What new practices, tools, or habits should we start doing? - What did we wish we had been doing this sprint that we weren't? - What experiments would help us move faster or with higher quality? ### 4. Gather data: Stop (11 min) - What did we do this sprint that wasn't valuable or actively hurt us? - What ceremonies, processes, or meetings are draining time without payoff? - What habits or shortcuts are creating future pain? ### 5. Gather data: Continue (11 min) - What worked well this sprint that we should keep doing? - Which practices made us more effective as a team? - What deserves explicit recognition so we don't lose it? ### 6. Group, theme, and vote (8 min) - Cluster similar items together as a group. - Each person gets 3 dot votes to spend on the items they most want to act on. - Discuss the top 2-3 voted clusters in detail. ### 7. Action items (7 min) - Convert the top discussion items into specific, owned actions. - Each action needs a single accountable owner and a due date - usually within the next sprint. - Capture the actions in the table below so they're not lost. ### 8. Close (2 min) - Quick return-of-energy round: one word on how the retro felt. - Confirm where action items live and who owns the follow-up. - Thank the team and end on time. ## Action item tracker | Owner | Action | Due date | Status | | ----- | ------ | -------- | ------ | | _Name_ | _What will be done_ | _YYYY-MM-DD_ | Open | | _Name_ | _What will be done_ | _YYYY-MM-DD_ | Open | | _Name_ | _What will be done_ | _YYYY-MM-DD_ | Open | ## Tips for this format Start/Stop/Continue is best for teams that want clear, action-oriented outcomes. Push for specific, observable behaviors in each bucket rather than vague goals. ## Tips for a remote retro - Use a shared digital board (Miro, FigJam, Mural) so everyone can add notes simultaneously. - Cameras on by default - body language is most of the signal in a remote room. - Silent writing first, then discussion. It prevents anchoring on whoever speaks first. - Timebox aggressively - remote retros drift more easily than in-person ones. - Capture action items in the same shared doc every sprint so they don't get lost. --- _Generated with the free [Sprint Retrospective Template Generator](https://www.elitecoders.ai/tools/sprint-retrospective-template-generator) by Elite Coders AI._
A sprint retrospective is the meeting an agile team holds at the end of every sprint to inspect how they worked together and decide what to change. The goal isn't to relitigate every story or celebrate the demo - it's to find one or two specific improvements the team will commit to for the next sprint.
A good retrospective follows a predictable arc: set the stage, gather data, generate insights, decide on actions, and close. The format you pick (Start/Stop/Continue, Mad/Sad/Glad, 4Ls, Sailboat, Plus/Delta, and so on) is just a frame for the "gather data" phase - they all work as long as the team commits to concrete, owned action items at the end.
Retrospectives are the single most important meeting in scrum. When teams stop running them - or run them on autopilot - they quietly stop improving. A 30-to-60 minute retro every sprint, with a fresh format every few months, is one of the highest-leverage habits an engineering team can build.
Choose Start/Stop/Continue or Plus/Delta when you want fast, action-oriented outcomes. Pick Mad/Sad/Glad when morale needs a check-in, or Sailboat when team alignment on the goal feels fuzzy.
Enter your team size, sprint length, total retro duration, sprint name, and whether the meeting is remote or in-person. The generator timeboxes each section automatically.
Add an icebreaker for new or quiet teams. Keep the action item tracker on so every retro produces written commitments with owners and due dates.
Copy the rendered template as Markdown or plain text, or download a .md file you can paste into Notion, Confluence, GitHub, or your meeting doc of choice.
Pair this retro template generator with other free tools for agile planning, codebase health, and delivery workflows.
Calculate your team's sprint velocity and predict future sprint capacity from past story point data.
Open toolEstimate the dollar cost of technical debt and get a prioritized remediation plan for your codebase.
Open toolExplore every free engineering tool we publish - calculators, generators, and reference cheat sheets.
Open toolCommon questions about choosing a format, running an effective retro, and turning conversations into committed actions.
There's no single best format - the right one depends on what your team needs right now. Start/Stop/Continue and Plus/Delta are great for action-oriented teams that want clear next steps. Mad/Sad/Glad surfaces morale and team health when something feels off. The Sailboat helps with goal alignment at the start of a quarter, and 4Ls produces richer reflection at the end of a project. Rotate formats every few sprints to avoid retro fatigue.
A common rule is 45 minutes per week of sprint length, capped at 90 minutes. So a 2-week sprint typically gets a 60 to 90 minute retrospective. Shorter retros (30 to 45 minutes) work for 1-week sprints or experienced teams with light agendas. Longer retros (90+ minutes) are appropriate for end-of-project reviews or when significant issues need to be worked through.
Start/Stop/Continue is action-oriented: each bucket points directly to a behavior change. It's tactical and works well when the team wants concrete next steps. Mad/Sad/Glad is emotion-oriented: it gives space to surface feelings, frustrations, and morale signals before jumping to fixes. Use Mad/Sad/Glad when the team feels off, then follow it with explicit action items so feelings translate into change.
Yes. Skipping retrospectives is one of the most common ways agile teams stop improving. Even a 30-minute Plus/Delta retro is better than nothing. The cost of a short, regular retro is low; the cost of accumulating unaddressed problems compounds quickly. If retros feel stale, change the format rather than canceling them.
For remote retros, use a shared digital board (Miro, FigJam, Mural, or even a shared doc), have everyone add notes silently for the first few minutes before discussion, and use camera-on by default to read body language. Timebox aggressively, designate a facilitator to call on people who haven't spoken, and capture action items in writing in the same place every sprint so they don't get lost between meetings.
Beyond templates
Use the free retro generator to run better meetings, then hand the development work to a full-stack AI developer for $2,500/month.
Visit the Elite Coders AI homepage