Retrospective guide

The Start, Stop, Continue retrospective

One of the simplest and most effective retrospective formats for software teams. Here's what it is, how to run it, and examples you can steal.

Run a Start / Stop / Continue retro

What is Start, Stop, Continue?

Start, Stop, Continue is a retrospective format that organizes a team's feedback into three simple questions about the last sprint:

Start

What should we begin doing? New practices, tools, or habits the team thinks would help.

Stop

What should we quit doing? Things that waste time, cause friction, or aren't working.

Continue

What's working well that we should keep doing on purpose, so it doesn't quietly disappear?

Its strength is focus. Because every note has to be an action-oriented Start, Stop, or Continue, the conversation naturally moves toward change instead of drifting into general venting.

How to run one (in about 30 minutes)

  1. Collect (10 min). Everyone silently adds notes to the three columns. Anonymous input works well here — it surfaces honest feedback people might hold back in a group.
  2. Group (5 min). Cluster similar notes so themes stand out instead of a wall of near-duplicates.
  3. Vote (5 min). Give everyone a few votes to prioritize. The top items rise to the surface democratically.
  4. Discuss & act (10 min). Talk through the highest-voted items and turn them into action items with an owner. This is the step that makes the retro matter.

Start, Stop, Continue examples for software teams

Start

Stop

Continue

Facilitation tips

More retrospective formats

See all five templates with guidance on choosing between them: Sprint retrospective templates. Related formats: 4Ls, Mad, Sad, Glad, Sailboat, Rose, Bud, Thorn.

Run a Start / Stop / Continue retrospective now

It's a built-in template. Create a board, share the link — no account required.

Start the retro