The Start, Stop, Continue retrospective is the fastest way to turn a team's reflection into concrete change. Instead of an open-ended "how did it go?" it forces three clear lanes: what to begin, what to end, and what to protect. That structure is why it remains one of the most-used retro formats for agile teams, project squads, and leadership groups alike.
Reach for this start stop continue template at the end of a sprint, a project phase, or a month of work. It shines when a team is short on time but needs a meaningful review, or when newer teams want a retro format that is easy to understand on the first try.
The whole delivery team plus a neutral facilitator. Keep it to roughly four to ten people so everyone gets airtime. Managers can join, but they should listen more than they steer so the team speaks freely.
Open by restating the goal and the working agreements. Then move through the three lanes in order: Start, Stop, Continue. Give people quiet time to write before anyone speaks, so the loudest voice does not anchor the room. Cluster similar notes, read them out, and dot-vote to surface the two or three items that matter most. Finally, convert those into owned action items with due dates and close with a quick round of one-word reactions.
Ready to make your retros stick? Run it in OrgTP to capture actions, assign owners, and track them automatically into your next meeting.
60 minutes total · 6 sections
Continuous improvement is the cornerstone of agile teams, but traditional retrospectives can easily devolve into aimless venting sessions or repetitive discussions. To drive real, actionable change, teams need a simple, action-oriented framework. That is where the Start, Stop, Continue retrospective comes in.
By focusing strictly on concrete actions - what to start doing, what to stop doing, and what to keep doing - this framework cuts through the noise and leaves your team with a clear, realistic action plan for the upcoming cycle.
This comprehensive guide provides a battle-tested Start, Stop, Continue Template and a step-by-step guide to running a high-impact retrospective that actually drives team progress.
The Start, Stop, Continue retrospective is a team reflection exercise designed to evaluate recent performance and identify specific behavioral or operational changes.
Unlike other retrospective formats that focus heavily on feelings or abstract concepts, this framework is strictly action-oriented. It forces the team to categorize their feedback into three distinct, actionable buckets:
To keep your team energized and ensure you leave the meeting with concrete action items, we recommend a strict time-boxed 60-minute agenda:
| Time | Agenda Item | Objective |
|---|---|---|
| 00:00 - 00:05 | Set the Stage | Welcome the team, outline the focus of the retrospective (e.g., the last sprint or month), and establish a safe, collaborative environment. |
| 00:05 - 00:15 | Silent Brainstorming | Team members work individually to write down their feedback and place them into the Start, Stop, and Continue buckets. |
| 00:15 - 00:30 | Group & Discuss | Group similar ideas together, read them aloud, and discuss the feedback as a team to ensure mutual understanding. |
| 00:30 - 00:45 | Prioritize (Dot Voting) | Give team members 3-5 votes each to identify the most critical items in each bucket that require immediate action. |
| 00:45 - 00:55 | Create Action Items | Turn the top-voted items into concrete action items with a clear owner and a realistic deadline. |
| 00:55 - 01:00 | Wrap-Up & Close | Thank the team, confirm where the action items will be tracked, and officially close the meeting. |
To get the most out of your Start, Stop, Continue exercise, implement these three essential best practices:
A retrospective only works if team members feel safe sharing honest feedback. Remind the team of the Retrospective Prime Directive: Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
Teams are usually great at coming up with new things to "Start" doing, but they rarely discuss what they need to "Stop" doing. Overloading a team with new initiatives without removing old bottlenecks leads to burnout. Force the team to identify at least 2-3 operational habits they can realistically stop.
Do not try to solve every problem at once. A successful retrospective should result in no more than 3 to 5 high-priority action items for the next cycle. If you try to implement 15 changes at once, your team will lose focus and accomplish none of them.
This exercise is highly versatile and can be run at the end of every sprint (typically every 2 weeks), at the end of a major project milestone, or on a monthly basis to check in on team dynamics and operational health.
The retrospective is typically facilitated by the Scrum Master or Agile Project Manager. However, to keep things fresh and encourage shared ownership, you can rotate the facilitator role among different team members each cycle.
While Glad, Sad, Mad focuses heavily on the emotional state of the team during the last cycle, Start, Stop, Continue is strictly focused on operational actions and behavioral changes. Both are valuable, but Start, Stop, Continue is ideal when you need to drive immediate process improvements.
Every action item must have a single owner and a clear deadline. Review the status of the previous retrospective's action items during the "Set the Stage" phase of your next meeting to maintain accountability and show the team that their feedback drives real change.
Stop copying agendas into a doc every week. OrgTP runs your meetings live — scorecard, rocks, issues, and to-dos all in one place, with your AI agents in the room.