What is the Start Stop Continue Retrospective?
The Start Stop Continue retrospective is a straightforward yet powerful method for teams to reflect on their work practices and behaviors. This action-oriented format helps teams quickly identify specific changes they want to make and successful practices they want to maintain. Developed as a feedback tool in the 1970s, this retrospective format has become popular in agile environments due to its simplicity and effectiveness. Teams use three simple categories to organize their thoughts: activities to begin implementing (Start), practices to eliminate (Stop), and successful behaviors to maintain (Continue). The clear structure makes it easy for teams to generate specific, actionable feedback while maintaining a balanced view of both improvements and successes. This approach is particularly effective for teams who want to focus on concrete actions rather than abstract discussions.
Start Stop Continue Retrospective Format
Start
What should we start doing?
This column focuses on new ideas and improvements. Encourage participants to think about gaps in current processes, missed opportunities, and innovative solutions. Consider both small improvements and larger strategic changes.
Stop
What should we stop doing?
This column identifies practices that aren't adding value or are causing problems. Help the team be specific about behaviors to eliminate, and encourage constructive rather than personal criticism.
Continue
What should we continue doing?
This column celebrates successful practices and reinforces positive behaviors. Help the team identify what's working well and should be maintained, as these practices contribute to team success.
When to use this retrospective
- When you want to quickly identify specific actions for team improvement
- During periods of change to determine which practices to keep or modify
- With new teams who need a simple framework for giving feedback
- When the team needs to focus on concrete actions rather than abstract discussion
Suggested icebreaker questions
- What's one positive change you've noticed in our team over the last month?
- If you could instantly implement one improvement to our team's way of working, what would it be?
Ideas and tips for your retrospective meeting
- Start with the 'Continue' column to begin on a positive note and acknowledge what's working well
- Encourage specific, actionable items rather than vague statements
- Keep a balanced perspective by ensuring all three columns receive adequate attention
- Focus on behaviors and practices rather than individuals
- Limit the final number of action items to ensure they're achievable
- Schedule follow-up discussions to track progress on implemented changes
New to retrospectives? Read our guide on how to run a retrospective →
Related templates
A structured reflection using Liked, Learned, Lacked, and Longed for categories to analyze sprint performance
What? So What? Now What? Retrospective
A structured reflection framework for systematic problem analysis and action planning
Agile Retrospective
A structured way to reflect on the past sprint and identify improvements.
Start Stop Retrospective
Retrospective Idea - A focused retrospective for clear, actionable team improvements