Purpose
The method helps clarify backlog, sprint work, and team flow concretely. It helps sort work by value, risk, and deliverability. The result is captured as a Start Stop Continue Board and Improvement Actions.
Agile
Start Stop Continue
Turns backlog, sprint work, and team flow into a tangible result by setting context and timeframe, collecting start ideas, and prioritizing actions.
What should the team start, stop and deliberately continue to work noticeably better?
LowWorkshop30-60 min
How it works
The team follows the steps: clarify context and timeframe, collect start ideas, collect stop topics, collect continue strengths, and prioritize actions. Each step is captured visibly. In the end, a Start Stop Continue Board and Improvement Actions are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Clarify context and timeframe
- 2Collect start ideas
- 3Collect stop topics
- 4Collect continue strengths
- 5Prioritize actions
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Team Retrospectives
- Project Reviews
- Continuous Improvement
Not good for
- Deep root-cause analysis
- Conflicts without moderation
Deep dive
In detail
Start Stop Continue follows a clear working logic: clarify context and timeframe, collect start ideas, collect stop topics, collect continue strengths, and prioritize actions. This turns the method into a visible thinking process instead of only a conversation. The participants move step by step from raw material, observations, or options to a shared structure. As a result, a Start Stop Continue Board and Improvement Actions become actionable for decisions, learning, or further planning.
Facilitation
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 30 to 60 minutes with 3 to 12 people and run it in a facilitated workshop. Keep facilitation lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions are helpful.
Output artifacts
Start Stop Continue BoardImprovement Actions
Artifact templates
Start Stop Continue Working TemplateCompact working template for Start Stop Continue with context, input, output artifacts, and next step.canvas
Start Stop Continue Working TemplateCompact working template for Start Stop Continue with context, input, output artifacts, and next step.
canvasstart-stop-continue-working-template.md
Compact working template for Start Stop Continue with context, input, output artifacts, and next step.
Start Stop Continue Canvas
Context
What is this method used for?
Core question
Which question should be answered at the end?
Input
Which data, observations, or materials are available?
Working area
- Area 1:
- Area 2:
- Area 3:
- Relationships / patterns:
Output artifacts
- Start Stop Continue Board:
- Improvement Actions:
Open questions
- ...
Next step
Owner, date, success signal.
When to choose differently
Short decision aid for existing alternatives.
4Ls Retrospective
Statt Start Stop Continue, wenn ihr Retrospektiven mit Erinnern, Lernen und Verbessern eng zusammenhalten wollt.
Similar methods
All methodsAgile
Starfish Retrospective
Turns backlog, sprint work, and team flow into a tangible result by explaining five categories, collecting inputs, and formulating experiments.
Agile
4Ls Retrospective
Turns backlog, sprint work, and team flow into a tangible result by setting the timeframe, collecting liked and learned items, and selecting actions.
Statt Start Stop Continue, wenn ihr Retrospektiven mit Erinnern, Lernen und Verbessern eng zusammenhalten wollt.
Agile
Sailboat Retrospective
Turns backlog, sprint work, and team flow into a tangible result by defining the destination island, collecting drivers and anchors, and agreeing on actions.
Agile
Mad Sad Glad
Turns backlog, sprint work, and team flow into a tangible result by defining the timeframe, collecting signals of mad, sad, and glad, and deriving patterns and actions.
Agile
Working Agreements
Turns team flow, expectations, and delivery rhythm into a tangible result by clarifying work context, collecting expectations, and setting a review cadence.
Agile
Sprint Retrospective
Turns sprint backlog, sprint execution, and team flow into a tangible result through reflecting on the sprint, collecting positives and challenges, and carrying actions into the next sprint.