In an Agile team, work is punctuated by different team meetings and rituals, in particular: the sprint planning, standup daily meetings, the sprint review, and the retrospective.
The main objective of an Agile retrospective is to identify potential improvements in the way the team works, based on the past weeks’ events. Thus, their success is essential for the well-being (and functioning) of the team in the long run. However, they require a great deal of preparation and some key success factors.
In this article, we will share the ideal structure for efficient sprint retrospectives and the outcomes you can get.
Table of content:
- Agile Retrospective: Definition
- Agile Retrospective: Format
- Agile Retrospective: Agenda
- Agile Retrospective: Outcomes
Agile Retrospective: Definition of a Successful Retrospective
According to the official definition from the Scrum Guide: “The Agile retrospective is the opportunity for an Agile team to examine itself and define a plan for improvement to be enacted during the next Sprint.” It gathers all the active team members, including the Scrum master and product owner. And if necessary, people who contributed to the current sprint from other departments.
Ideally, the Agile retrospective takes place at the end of the sprint, right or soon after the sprint review (and before the next sprint planning). Indeed, you don’t want to wait too long and risk your team members to forget about what happens during the sprint that could be improved.
An Agile retrospective is considering “successful” if team members are confident that their functioning as a team will meliorate for the next sprint and the trend shows a continuous improvement over time.
Agile Retrospective: the Ideal Format
Retrospectives usually last for ½ hour to 1 hour. It should always include these three axes:
- Celebrate successes: a new client, a feature release, a past action identified during the last retrospective that led to the expected results, …
- Discuss the issues and irritants – from the smallest (the coffee is bad) to the biggest (we need new fundings) – and take time to analyze them
- Identify the actions to solve these issues and irritants
There are countless formats of retrospectives, such as:
- Three Words: everybody sums up the last iteration in 3 words
- Remember the Future: Imagine the next iteration is perfect. What is it like? What did you do?
- #tweetmysprint: Ask participants to write 3 or more tweets on sticky notes about the iteration they’ve just completed.
and none that you should adopt for good if you want your team to keep feeling excited about their retrospectives. If you want to find inspiration in order to vary your retrospective format, you can pick ideas from Retromat unreservedly.
A creative format is not enough. If you want your Agile retrospective to be successful, be careful to these warnings:
- Amplify the good! Retrospectives do not only take place to improve the way the team works but also to celebrate successes.
- Avoid jumping too quickly to a solution. Instead, take the time to reflect on the raised issue and analyze it collectively.
- Make sure everyone can speak their mind.
- End each retrospective by asking for feedback on the retro itself: no process is perfect.
- Cover the whole period, not only the last few days.
Using a tool like TeamMood to measure your team members’ mood and feelings over the Sprint can provide you with great insights for your Agile retrospective.
Start measuring the health of your team now!
Agile Retrospective: Agenda
An Agile retrospective usually follows these 5 steps (the timing should be adapted to the length of the retro):
1. Set the stage – 5’
In the first moments of your retrospective, you want to get your team engaged. Start by taking a moment to thank your team members for their work and for investing their valued time in this continuous improvement process. You can also ask each attendee to explain briefly what they are expecting from the session.
💡Tip: You can use a timer to give everyone equal time to have their say.
2. Gather data – 10’
After setting the stage, you can start to paint a picture of the current sprint, good and bad, based on the retrospective format you picked. You can collect data on action items and results, decisions made during the sprint, milestones achieved, processes, new tools and technologies implemented… For each of these, ask your teammates what went well and not so well.
💡Tip: Physical supports such as whiteboards or paper boards and colorful sticky notes are very useful to get your team members engaged.
3. Brainstorm ideas – 5’
After having identified shortfalls, here comes the time to understand the why and link the cause to the effect. Understanding the reason behind problems will guide your team for smarter (and several) solutions. Also, make sure that your team has the right influence to address the problem. Some problems may just be too big to be solved at your scale.
💡Tip: To get to the root cause of one problem, you can use the “5-whys” method. It will help you come up with a range of viable solutions.
4. Pick a solution – 5’
Once you have a handful of viable solutions, narrow down to two or three ideas you can reasonably take into your next iteration. Here are three decision-making processes you can use:
- the simple vote: each participant chooses the idea he/she likes the most
- the dot vote: each participant adds a dot to their top three priorities among the ideas
- the multiple vote: each participant gets a certain number of points that they can put on a single solution or divide up among solutions
But you can use any other system that you like.
💡Tip: To find solutions that get real results, don’t forget to consider their potential outcomes.
5. Close – 5’
If you want your retrospective to be useful, you must end up the meeting with:
- a clear summary of the past sprint
- a concrete action plan, broken into small and easy-to-implement tasks, assigned to an owner and with a fixed due date
- a clear process for follow-up, feedback, and measuring results
- the date for the next retrospective
💡Tip: You can also ask for feedback on the retrospective itself, in order to keep improving it.
Agile Retrospective: Outcomes
In the long run, your retrospective will only be useful if the participants see a real improvement in their work environment, process, tools, … Your role as a Scrum Master or team leader is to make sure that the 2 or 3 (relevant) actions that are selected during the retrospective are effectively implemented by the next one. Thus, make sure to favor quality over quantity.
To make sure these actions are relevant and realist, you can turn them into SMART objectives:
- S for specific
- M for measurable
- A for achievable
- R for relevant
- T for time-bound
During the vote, you can also ask for volunteers to be responsible for an action. You’ll have a better chance to see them implemented than if you assign them yourself to your team members.
Finally, you should consider these actions as fully-fledged tasks. You can even add them to the backlog and prioritize them accordingly (in agreement with the Product Owner).
Retrospectives help identify the small “pebbles in the shoe” of your team that, if unaddressed, can become real frustrations and brakes to the overall productivity. They don’t have to shake everything up. Common actions such as reviewing the DoD (Definition of Done) or changing the time of the daily meeting can have a real positive impact in the long run!
Photo by Marc Bustier on Unsplash