Start, Stop, Continue Retrospective

A simple retrospective format that helps teams choose new practices, remove unhelpful habits, and protect the approaches that already work.

What Is Start, Stop, Continue?

Start, Stop, Continue is a structured Sprint Retrospective technique. Team members suggest practices to begin, habits or constraints to remove, and successful behaviors to preserve. The three prompts create a balanced view of the sprint instead of focusing only on problems.

Teams use the format because it is easy to explain, flexible enough for many situations, and naturally leads toward decisions. It works especially well for teams that want a familiar structure, have a mix of positive and challenging feedback, or need to reset working agreements after a period of change.

Start, Stop, Continue Examples

Start

Begin practices that could make future sprints more effective.

Start writing clearer acceptance criteria before sprint planning.
Start involving QA while stories are being refined.
Start documenting important architectural decisions.
Start pairing on complex or unfamiliar stories.
Start reviewing progress toward the sprint goal mid-sprint.

Stop

Remove behaviors that repeatedly create delay, risk, or unnecessary work.

Stop routinely carrying unfinished work between sprints.
Stop accepting stories with unclear requirements.
Stop postponing every technical debt discussion.
Stop holding meetings that have no decision or useful outcome.
Stop merging code without an appropriate review.

Continue

Protect practices that are already helping the team succeed.

Continue using focused Daily Scrums to surface blockers.
Continue collaborative and timely code reviews.
Continue expanding valuable automated test coverage.
Continue gathering stakeholder feedback early.
Continue celebrating sprint successes and team contributions.

For more ways to make observations concrete, explore these Sprint Retrospective examples, What Went Well examples, and constructive What Didn't Go Well examples.

How to Facilitate the Session

Prepare the session. Define the sprint or period being reviewed, create three clearly labeled areas, and review previous action items.
Invite individual reflection. Give everyone quiet time to add specific responses before discussion begins.
Encourage participation. Use a round-robin or anonymous input when needed so quieter team members have equal space.
Group similar responses. Combine duplicate ideas and clarify what each group means without losing important differences.
Prioritize improvements. Vote or discuss which ideas would have the greatest positive impact.
Create action items. Choose a small number of changes, name an owner, and define how the team will know whether each change helped.

The practices in BugNBrag's Sprint Retrospective best practices can help facilitators maintain psychological safety and follow through after the meeting.

Discussion Tips

Focus on improving systems and processes rather than assigning blame.
Ask for specific observations instead of broad labels such as “communication.”
Encourage participation from the entire team before prioritizing ideas.
Select only one or two improvements the team can realistically test next sprint.
Review previous action items before creating new commitments.
Treat “Stop” as an invitation to remove friction, not a list of personal criticism.

A thoughtful retrospective icebreaker question can make it easier to begin. For distributed teams, plan silent writing and discussion using the guidance for remote Sprint Retrospectives.

When to Choose Another Format

Start, Stop, Continue is less useful when the team needs to explore one complex incident in depth, repair a serious conflict, or examine the emotional impact of a difficult sprint. A root-cause exercise, a timeline, or a Mad, Sad, Glad retrospective may create more insight in those situations. Rotating formats can also help when the three prompts have become routine and responses are losing specificity.

Whichever format you choose, continuous improvement matters more than filling every column. A successful retrospective ends with shared understanding and a manageable experiment the team can revisit.

Run a focused Start, Stop, Continue retrospective

Free. No account. No setup. Just a clear path from feedback to action.

Create Free Session