Updated (published )

The "Keep Stop Start" retrospective incl. direct access

The Keep Stop Start retrospective is a deliberately positively framed retrospective format for teams that want to quickly arrive at a concrete improvement.

Retrospective Keep Doing, Stop Doing, Start Doing – the three questions you should ask

Keep Stop Start retrospective board with three colored columns

The Keep Stop Start retrospective consists of three questions. The special advantage of this order: you begin with what is already working well, and end with new ideas for concrete actions.

  • Keep Doing: [Optional: Looking at the last sprint…] What should we keep doing?
  • Stop Doing: What should we stop doing?
  • Start Doing: What should we start doing?

You are welcome to give the team more context (e.g. by saying “looking back at the last sprint or the last few weeks”) when you ask these questions.

By the way, you can also open the Keep-Stop-Start retrospective directly with our Retro Tool Echometer and run it online with your team (no registration):

Keep stop start retro

Keep: What should we maintain?
Stop: What should we stop doing?
Start: What should we start doing?

Why the Keep Stop Start order is helpful

If you ask last what the team wants to start, you elegantly lead into the last phase of the retrospective the transition: to the potential actions.

By the way, here you can find 7 tips for great action items in retrospectives.

Are you looking for the general “Start Stop Continue” method with examples, a template, and a complete process? Then read our Start Stop Continue guide.

Example responses in a Keep-Stop-Start retrospective

The following responses are meant to inspire you. They are most valuable when you relate them to your specific collaboration, the last sprint, or the past few weeks.

Keep Stop Start Retro: Example responses in remote teams

Keep – What should we keep doing?

  • Keeping our daily check-ins short while openly addressing blockers.
  • Recording decisions and tasks directly in the shared board after the meeting.
  • Working on complex topics together via screen sharing instead of writing long messages.

Stop – What should we stop doing?

  • Starting meetings without an agenda or a clear desired outcome.
  • Contacting colleagues spontaneously outside their agreed working hours.
  • Making important agreements only in private chats.

Start – What should we start doing?

  • Using a dedicated channel and a consistent format for asynchronous updates.
  • Scheduling regular informal virtual meetings to strengthen personal exchange.
  • Sharing a brief written preparation before larger meetings.

Keep Stop Start Retro: Example responses in agile teams

Keep – What should we keep doing?

  • Preparing small, clearly scoped work packages together during refinement.
  • Validating new ideas early with users or stakeholders.
  • Openly showing in the Sprint Review what is not yet finished and why.

Stop – What should we stop doing?

  • Starting too many tasks at the same time.
  • Taking tickets into the sprint whose goal or acceptance criteria are unclear.
  • Postponing improvement measures from retrospectives.

Start – What should we start doing?

  • Consciously limiting our work in progress.
  • Defining a concrete action item with a responsible person for each retrospective.
  • Checking assumptions through small experiments before implementation.

Keep Stop Start Retro: Example responses in Scrum teams

Keep – What should we keep doing?

  • Sharpening the Sprint Goal together at the start and keeping it in mind throughout the sprint.
  • Focusing in the Daily Scrum on progress toward the Sprint Goal instead of purely status updates.
  • Refining Product Backlog items together in good time.

Stop – What should we stop doing?

  • Taking on new work during the sprint without discussing the impact on the Sprint Goal.
  • Using the Daily Scrum for detailed problem solving with the whole team.
  • Ending retrospectives with general intentions instead of concrete improvements.

Start – What should we start doing?

  • Following up on the most important improvement from the retrospective visibly in the next sprint.
  • Purposefully gathering feedback on open product decisions in the Sprint Review.
  • Regularly reviewing the Definition of Done and adjusting it together when new insights arise.

Conclusion - Retrospective Keep Doing, Stop Doing, Start Doing: Simple and extremely effective

The “Keep Stop Start” retrospective is one of the most common retrospective methods, which is very easy to understand and at the same time leads very effectively to improvement measures. This is precisely what makes it so popular across the board.

Nevertheless, I generally recommend surprising your team regularly with a different set of retrospective questions as well. We have a blog post with 32 kickass retrospective ideas for beginners and professionals. written - feel free to check it out!

Or take a direct look in our retro tool at which retro formats we offer here:

Blog category

More articles on "Agile Retrospective Ideas"

View all articles in this category
54 Retrospective Ideas, Templates & Formats for Agile Teams in 2026

54 Retrospective Ideas, Templates & Formats for Agile Teams in 2026

54 fun retrospective ideas, templates, and formats for agile teams: sprint retrospectives, remote team retros, project retrospectives, and classics.

First retrospective: How to get started easily as a team

First retrospective: How to get started easily as a team

Your first retrospective, explained simply: goals, process, typical mistakes, and why the Keep-Stop-Start retro is the best entry point for new teams.

9 effective team exercises for agile retrospectives

9 effective team exercises for agile retrospectives

9 team exercises that prepare your team for agile retrospectives and ensure that retros become more open and effective.

26 Fun & Fresh Agile Retrospective Templates in 2026

26 Fun & Fresh Agile Retrospective Templates in 2026

Discover 26 fun & fresh Agile Retrospective templates for 2026. Find the best method for your team and make your retrospectives successful.

Spotify Health Check Retrospective: Moderation & Tips

Spotify Health Check Retrospective: Moderation & Tips

Use the Spotify Health Check in retrospectives for team development. This guide offers moderation questions and templates for Team, Tech & Co.

Sprint Refinement vs Sprint Retrospective: Explained Simply

Sprint Refinement vs Sprint Retrospective: Explained Simply

Sprint Refinement vs Sprint Retrospective explained simply: clear differences, practical examples, decision support, 2 retro ideas and FAQ.

4-Quadrant Retrospective: Examples & Implementation Tips

4-Quadrant Retrospective: Examples & Implementation Tips

What is a 4-quadrant retrospective? Learn about the structure, quick facts, origin, comparison, and concrete implementation for effective sprint retros.

42 Fun & Creative Retrospective Icebreakers breaking any Ice

42 Fun & Creative Retrospective Icebreakers breaking any Ice

Discover 42 creative retrospective check-ins and icebreakers for agile teams. Find the best questions and methods to make every retro interactive.

When should a sprint retrospective happen?

When should a sprint retrospective happen?

When is the best time to hold a sprint retrospective? Find out when in the sprint cycle and on which day the retrospective is most effective.

Echometer Newsletter

Don't miss updates on Echometer & get inspiration for agile working

FAQs about Retrospective Tool

Top answers for anyone exploring our Retrospective Tool.

Do I have to register to test the Retro Tool?

No, you do not need to log in to Echometer or register to test the Retro Board and Retro Tool in Echometer.

You can try out Echometer’s Retro Board via the following link without logging in: Try a Practice Round

Where can I try retrospective software for free?

You can test retrospective software directly in Echometer for free. You do not need to log in or register: the retro board and templates can be tried out immediately in the browser.

You can easily try out Echometer’s retro board without logging in using the following link: Start trial run

You can find more ways to try it out for free on the Page for the retro board without login and registration.

How can I buy Echometer's retro tool?

First, simply register for free in Echometer. Then navigate to the workspace for which you would like to purchase the retro tool. If you haven’t already done so, you can do so here: Create account in Echometer 1:1 tool

You can then manage your subscription (for both the retro tool and the 1:1 software) within the workspace settings.

You can choose from various payment methods when upgrading.

If you do not have access to your company’s credit card yourself, you can simply add a buyer as a workspace admin in your Echometer workspace so that this admin can carry out the upgrade for you.

What is the difference between the Retrospective tool and the 1:1 software?

In Echometer there are two separate software solutions that are available within each workspace in Echometer:

  • 1:1 tool: Software for planning and conducting 1:1 meetings and tracking employee development
  • Retrospective tool: Software for planning and moderating retrospectives and tracking team development through team health checks

Both are independent software solutions, so they can be used separately from each other.

However, they work according to the same principles and aim to achieve the same added value: The continuous improvement of agile teams. In this respect, the simultaneous use of both software solutions is recommended.

Can I appoint several admins in Echometer?

Yes, you can assign administration rights to any number of users at both team level and workspace level. Please note the following:

  • Only workspace admins can take out and manage a Echometer subscription for a Echometer workspace.
  • Only workspace admins can create additional teams and name or remove additional workspace admins.
  • Team admins can appoint and remove additional team admins and team members for their team
What is the structure of retrospectives in Echometer?

The Echometer Retrospective software is designed to guide teams through the retrospective process with maximum ease and effectiveness, following best practices.

The steps and their sequence can be customized using the navigation within the retro. By default, a retrospective in Echometer is structured in this way:

  • Icebreaker
  • Review of open measures from past retros
  • Collect feedback (first Health Checks, then open questions)
  • Prioritization of feedback
  • Deriving action items
  • Concluding the retrospective with the “ROTI score” (Return on Time Invested)

Additional whiteboards (e.g. for workshops, for analyzing problems or for brainstorming measures) can also be added spontaneously at any point using the Retrospective navigation.