Short retrospective: Better a quick retro than no retro at all
Retrospectives are one of the most important meetings for agile teams to reflect on and further develop their collaboration. But what if things are stressful and time is short, or meetings come up and the slot in the calendar for the retro has to be shortened? Then don’t just let the retro fall through; use a quick retrospective instead.
A short retrospective, often also called a quick retrospective, requires clearly moderated steps with a timebox, a few clear questions, and at least one verifiable action.
Three recommended formats for a short retrospective
For short retros, you don’t need a generic standard program, but rather a format that fits your occasion. These three formats work especially well because they quickly get the conversation going while still leaving room for a concrete next step.
| Format | Especially suitable when … | Recommendation for a short retro |
|---|---|---|
| Lean Coffee | there are already topics in the room or the team should decide for itself what it talks about | Good for 15 to 30 minutes: collect topics, prioritize together, and discuss only the most important ones. |
| Keep–Stop–Start | you want to derive concrete improvements quickly from the last sprint | Our first choice for a short, action-oriented retro: The three questions lead directly to what you want to keep, stop, or start. |
| Health-Check Retro | you need a quick overview of mood and collaboration | Ideal if you want little silence while collecting input: rate statements, discuss only notable results, and open up further topics at the end. |
A short retro is suitable after a small milestone, when recurring topics come up, or as a weekly check-in. It is not suitable for conflicts, major changes, or many open issues. Then more time is the better choice.
The Scrum Guide on the duration of a retrospective
The Scrum Guide suggests that you should take 3 hours for a retrospective - with a one-month sprint rhythm. In practice, this time slot is usually not available. In our experience, most teams block out between 60 and 120 minutes for their retrospectives.
💡 New analysis of 30,000 retrospectives
Short retrospectives with a duration between 30-45 minutes are even the ones with the best rating (8.5/10) by participants!
view study
tips for short retrospectives
What can you do when things have to be fast? Here are our tips for a quick retrospective that will help you move forward.
Tip 1 for your short retrospective: Do NOT skip the check-in
A common mistake is to simply skip the check-in as a first step and get straight to the point - after all, the productive part of the retrospective only comes after the check-in as a warm-up, right?
That’s a misconception. The check-in and “setting the stage” is an essential component of the retro, and is far too important to the process, that you should even think about skipping.
Those who do not check-in will have a hard time actively engaging the team during the process of the retrospective, as it is a prerequisite for productive discussions.
For example, the check-in can simply be a basic open question, that each team member answers after each other in 2 to 3 sentences. For example:
- What is your high- or lowlight from last week?
- On a scale of 0 for bad to 10 for great - how are you feeling right now?
Otherwise, there are of course various check-in generatorsthat you can use. The few minutes spent on a check-in are worth it, I promise.
Tip 2 for your short retrospective: Keep–Stop–Start retro
If you want to get directly to concrete improvements in a short time, the Keep–Stop–Start retro is our first recommendation. The three clear questions are quickly understood, give everyone a clear writing prompt, and naturally lead from what is working well to the next steps.
Keep Stop Start Retro: How the retro works
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
- Keep: What should we keep?
- Stop: What should we stop doing?
- Start: What should we start doing?
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
Keep Stop Start Retro
Tip 3 for your short retrospective: Collect feedback in advance
The data gathering phase of a retrospective is often the part that takes the most time - whether by sticking notes or with the support of online tools.
Here, teams who have collected feedback and topic suggestions beforehand are at a great advantage. This way, you can have all data ready for the retrospective and go straight to the topic discussion without needing to make time for individual brainstorming. For example, you could send out a survey before the retro, create a page in Jira where topics are collected, or simply ask for feedback via e-mail for the short retrospective.
As a tool for retros, on Echometer you can, for example, ask for retro feedback on both psychological behavior anchors and open questions (“Keep, Stop, Start” & Co.). The answers received are automatically compiled for the upcoming retrospective and ready for presentation in an interactive team development workshop.
Tip 4 for your short retrospective: Put discussions on measures into breakout sessions
Another part of the retrospective is the discussion to derive actions. While prioritizing the topics should definitely be done together in the retrospective, the discussions about the definition of the actions can also be clarified in small groups outside the retrospective - for example, in so-called breakout sessions.
If your team agrees on what the most important problems are at the moment, you can form a “task force” consisting of 2 or more people, who will then discuss the topics among themselves, then share the results with the rest of the team.
Measures like this can then be recorded in the retrospective as follows:
- Topic X: Klaus and Greta work out a concept for a solution and share it with the team before next Tuesday
- Topic Y: Gundula and Kevin discuss whether it might be worth pursuing solution Z and share their result with the team by tonight
Tip 5 for your short retrospective: Health Check retros
If a quick mood and collaboration check helps you, a short Health Check is a good fit. Instead of spending a long time searching for topics, each person rates a few concrete statements on a scale. This is quick, makes differences in perception visible, and often already provides enough material for a short retro.
That means the process for the quick Health Check retro is as follows:
- Specific statements are presented (see below for examples).
- Each team member briefly and concisely evaluates the statements anonymously on a survey scale - how much do you agree from 1 to 7?
- Optional: The results are discussed. Positive and negative examples are collected that might explain the results. This part potentially takes a long time.
- Prioritization is now carried out, with each team member voting anonymously as to which of the statements require the greatest need for action.
- An action item is only put down for the statement that has the most votes - not the “second most voted” one - to save time.
The advantage of this method is that a lot can happen with just a few clicks. Only go into discussion for each statement if someone has thoughts about the answers; otherwise, move straight on to the next one. This avoids awkward silence, and the retro can still deliver valuable insights in 15 to 30 minutes.
Secondly, you can use our Retrospective Tool Echometer to conduct various health check retro formats conduct. For a short retro, we recommend this compact selection from the Spotify Health Check. After the four statements, there is an open Lean Coffee question so that topics also have room if they do not appear in any rating:
Spotify Health Check: Team: How the retro works
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
Health Check
All team members can answer the health checks anonymously on a scale. Then go through the results of the health checks together and record any additional comments if necessary. If you use the same health checks in several retrospectives, you can also track trends over time in Echometer.
- We enjoy coming to work and have a lot of fun collaborating.
- We always receive great support and help when we ask for it!
- We are a great team that works wonderfully together.
- We’re constantly learning many interesting things!
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
- Lean Coffee: What else would you like to talk about in our retro?
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
Spotify Health Check: Team
Health Check Questions (Scale)
Open questions
Note: This retrospective format asks for agreement with the given Health Check items on a scale.
Tip 6 for your short retrospective: Try Echometer
A good support to keep your retro short are good retro tools (see 7 best retro tools comparison). Retro tools can take a lot of work off your hands - including timeboxing or prioritizing feedback.
In particular, I want to mention the retrospective tool Echometer name, in whose development I was personally involved. It combines insights from psychology with Agile best practices to get the best out of Team Health Checks & retros for team development.
We give you concrete tips in the tool on how to derive good measures - and it can be used both online remotely and offline (more on this here: the Best Retrospective Meeting Tool).
You can use this button to quick open the ‘lean coffee’ retrospective and invite a team via a link (there are more than 30 other retrospectives ideas available):
When you get to the end of the retro, if you want to, you can create a free account to save your results.
If you would like to find out more beforehand or start a proper trial directly - right here or start for free.
The agenda: How short can a retrospective be?
For a truly short retro, we recommend at least 20 minutes. Anything shorter makes it difficult to fit in all the important steps and still arrive at a concrete action. These timeboxes are the shortest sensible time budget per step:
| Step | Minimum timebox | Goal |
|---|---|---|
| Check-in and set the frame | 2 min. | Everyone arrives and knows where the retro is headed. |
| Collect topics or answers | 3 min. | Each person quietly contributes their most important observations. |
| Cluster and prioritize | 5 min. | The team chooses the one topic with the greatest leverage. |
| Discuss and develop a solution | 5 min. | Clarify causes and possible next steps without getting sidetracked. |
| Define an action | 3 min. | Record a small, verifiable action with a responsible person. |
| Closing | 2 min. | Repeat the action and schedule the next check-in. |
That makes a 20-minute retro. If you want to discuss more than one topic, try out a new method, or reflect on a larger change, it’s better to plan 30 minutes or more.
If the team attaches great importance to making the retrospectives as effective as possible, it can make sense to agree on a structured model in the team, according to which the retros are designed.
With Echometer, we provide a modular system that enables you to design varied retrospectives within a structured process. The process can of course also be designed flexibly if required - and, by the way, it also complements your retrospective with psychological know-how! Feel free to ask a free demo account if that sounds like something for you.
Nevertheless, keep in mind that you should always block at least 60 minutes in the calendar for the team retrospective (depending on the team size, more if necessary), even if it can occasionally be faster.
Final note: shortening retrospectives properly
If it is clear in advance that not even the minimum recommended 60 minutes are possible: Think about whether postponing the retrospective might be the better solution. Because: postponed is not abandoned ;-)
If you are searching for fun retrospective ideas, check out our post on 54 Kickass Retrospective Ideas for Agile Teams (including the Mario Kart Retro & the Team Morale Health Check).
By the way, one of the best ways to sustainably develop team members’ agile mindset is to implement an Agile Health Check. Our free team health check kit can help you ask the right questions - just click through.
By the way, if you are still looking for a suitable retro board (with 60+ agile retrospective formats), this post can help you: Comparing the 6 best retrospective boards
FAQ on short retrospectives
What’s the difference between a short retro and a normal retrospective?
A normal retrospective examines several topics in more depth. A short retro focuses on three to five questions and one outcome. Both require a check-in, prioritization, and a clear next step.
Can a short retrospective take place remotely?
Yes. What matters is silent writing time, anonymous voting, and a visible result. An online board helps. But it does not replace good facilitation.
How often should a team do a short retrospective?
As a light check-in, it can work weekly. After each sprint, it remains useful if the team reviews the agreed actions at the next meeting.
How does a 15-minute retrospective work in practice?
A 15-minute retro is very ambitious: plan two to three minutes for the check-in, then collect topics or answers silently for three minutes and prioritize them. Discuss only the most important topic and, in the end, define a concrete action with a responsible person.
Tip for the 15-minute retro: Use a pre-survey to save time on individual brainstorming. Then, after the check-in, you can go straight to presenting and grouping the feedback.
Which retro method is suitable if the team has not prepared any topics?
A short health check is particularly well suited. Concrete statements give everyone an immediate prompt for evaluation; discuss only the results that someone wants to contribute to.
When is Lean Coffee better than Keep–Stop–Start?
Lean Coffee is a good fit when several topics are already on the table and the team should prioritize them itself. Keep–Stop–Start is better when you want to quickly derive concrete improvements from the last sprint with a clear structure.
How do I prevent a short retro from ending without a result?
Prioritize consistently after gathering and discuss only the most important topic. Define at least one small, verifiable action and assign a person to follow it up until the next retro.
How long should the check-in in a short retro take?
Two to three minutes are usually enough. Still, don’t skip the check-in: it helps the team arrive and engage in the shared reflection.
Can a short retro replace the normal sprint retrospective?
As an exception or a light weekly check-in, it may be sufficient. In the event of conflicts, major changes, or several open issues, you should take more time for a more detailed retrospective.
