Start - Stop - Continue

An action-oriented format that pushes the team toward concrete decisions rather than abstract discussion. Participants name practices worth starting, those to stop because they get in the way, and the ones that already work and should continue. The result is a clear, immediately usable list of changes that supports a culture of continuous improvement.
Start

New practices worth trying in the next cycle

Roman

Roman

Start writing a one-line rollback plan on every deploy ticket
Maria

Maria

Start inviting support to sprint review
Kirill

Kirill

Start blocking two hours on Thursday for tech debt
Stop

Habits that get in the way and should end now

Anna

Anna

Stop pulling new tickets while three are in review
Daria

Daria

Stop booking meetings without an agenda in the invite
Roman

Roman

Stop merging on Friday afternoon
Continue

What already works and must survive the next change

Maria

Maria

Continue the Wednesday demo — people actually show up
Kirill

Kirill

Continue rotating the on-call handover doc
Anna

Anna

Continue pairing juniors with a reviewer for the first week

What is a Start Stop Continue Retrospective?

The Start Stop Continue retrospective is a framework for teams to reflect on their past performance and make improvements for the future. It covers three main focus areas:

  • Start
  • Stop
  • Continue

Start

This group contains items the team should be working on but aren’t just yet. “Start” is often home to new ideas that solve problems in different ways.

Stop

This group is all about those little annoyances and frustrations that team members face in their everyday jobs. If it’s a source of negativity in the team, it goes in this bucket.

Continue

This is where teams keep the stuff they’re most proud of. These items are things that are working well, producing results for the team, and so should be continued.

Benefits of using the Start Stop Continue Retrospective

  • Provides a democratic process for every team member to voice their opinions
  • Uncovers previously-unexplored ideas and insights
  • Improves team cohesion and productivity
  • Identifies potential flaws in the process
  • Maintains project momentum, even when things get tough

How to plan and run a Start Stop Continue retrospective meeting

  1. Schedule the meeting and create a board in QRetro with the Start Stop Continue template
  2. Brainstorm suggestions for each category
  3. Refine the list through voting and discussion
  4. Document the final decisions

Examples of the Start Stop Continue method

  • Start: Clean up the backlog, improve communication between team members
  • Stop: Adding too many stories to the sprint, beginning daily stand-ups late
  • Continue: Team-building and work outings, meeting shared goals

Get started with a free template

QRetro.com provides a free Start Stop Continue template that can be exported in various formats for future reference. Teams can improve their performance by trying out the Start Stop Continue framework.


Similar templates

Other formats teams pair with this one — open any of them as a board in one click.
4Ls Retrospective
A simple, popular method for Scrum Masters and their teams that captures both the positive and the negative sides of a sprint. Across four lenses — what people liked, what they learned, what they lacked and what they longed for — the team gathers honest feedback and turns it into ideas for improvement. The structure makes it easy for everyone to contribute, even in quieter teams.
Sailboat Retrospective
A metaphorical exercise that turns reflection into a picture of the team's journey. The wind represents what moves the team forward, the anchors what holds it back, the rocks the risks lurking ahead and the island the shared goal everyone is sailing toward. The visual framing makes it easier to talk openly about obstacles and align around where the team wants to go.
Mad Sad Glad
Mad, Sad, Glad helps a team explore how it felt about the past sprint before moving on to the next one. By naming what made people angry, what saddened them and what brought joy, the team surfaces emotional signals that plain metrics miss. Done well, it builds emotional awareness, strengthens team spirit and turns frustration into a constructive conversation.
Thumbs up, Thumbs down, new ideas and recognition
A light, balanced format that keeps the conversation moving between the good, the bad and the forward-looking. The team marks what deserves a thumbs up, what gets a thumbs down, the new ideas worth trying and the people worth recognizing. Adding recognition to the mix keeps the tone positive while still leaving room for honest criticism.
Lean Coffee
A meeting format that minimizes wasted time and boosts engagement by letting participants build the agenda themselves. Topics are proposed, voted on and discussed in order of priority, so the team spends time only on what truly matters to everyone in the room. First run in Seattle in 2009, Lean Coffee is easy to learn and adapts to almost any team conversation.
Original 4
The classic retrospective that laid the foundation for every method that followed. Built around four questions proposed by Norman Kerth in Project Retrospectives: A Handbook for Team Reviews, it asks what went well, what didn't, what the team learned and what still puzzles it. This timeless structure helps teams reflect honestly and keep striving for continuous improvement.
Try Template