Our blog articles are translated to English by machine and may not always be accurate - sorry for that.

If you understand German, we recommend to switch to the German version.

sprint - tips for a quick retro

Short retrospective - better quick than not at all

Share on linkedin
Share on twitter
Share on facebook
Share on email

Retrospectives are one of the most important meetings for agile teams to reflect on and further develop their collaboration. The frequency usually varies between weekly and monthly, and there is a fixed block in the team's calendar to ensure that this meeting will take place.

It can happen from time to time that the planned time window is not available due to external factors, such as ad-hoc appointments or deadlines. In these cases, we advocate doing a short retrospective rather than simply skipping it.

The Scrum Guide on the duration of a retrospective

The Scrum Guide suggests that you should free up 3 hours for a retrospective - when you have a one-month sprint rhythm. In practice, this time window is usually not feasible. In our experience, most teams block between 60 and 120 minutes for their retrospectives.

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 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/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 from 0 for bad to 10 for super - how are you feeling right now?

Otherwise, there are various check-in generators that you can use. The few minutes spent on a check-in are worth it, I promise.

Tip 2 for your short retrospective: collect feedback in advance

The data gathering phase of a retrospective is often the part that takes up the most time - whether you are just using sticky notes or 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.

Would you like to try a new format in your next retro, which can quickly lead to positive results? Then our tool Echometer could be something for you. You can find more information here:

Tip 3 for your short retrospective: Discussing measures in breakout sessions

Another part of the retrospective is the discussion about deriving measures. While the prioritization of the topics should definitely be done together during the retrospective, the discussions on the definition of these measures can be clarified in small groups outside of the retrospective - for example in 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 is worth or necessary to pursue Solution Z, and share their conclusion with the team latest tonight.

With these tips, it should be possible to conduct a valuable (short) retrospective in less than 60 minutes. Perhaps now the only question you have left is:

How short can you make a retrospective?

Using the aforementioned tips, a retrospective can be completed (in some individual cases) in about 30 minutes. Of course, this also depends on the choice of method. There are many retrospective methods that are not feasible in such a short time.

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.

At Echometer, we provide a kit that enables you to create varied retrospectives within a structured process. The process can, of course, be adjusted flexibly if that's what you want - and also backs your retrospective with psychological knowledge! Feel free to ask us for 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

 

Moving can also be an alternative.

If it is already clear in advance that even the minimum time of 60 minutes recommended is not going to be possible: think about whether a postponement of the retrospective might be the better solution. At the very least: postponed does not mean canceled 😉

On a similar note

Articles you may also be interested in

Want to get started?

Test team retros with Echometer for free & drive agile work in your organization.

I recently got an ebook too "12 retrospective methods from psychology" written - interested?

Christian Heidemeyer, Psychologist & Scrum Master