Sprint Retrospectives Made Simple
Originally published in GoRetro
Originally published in GoRetro
It's Monday, the last day of the Sprint. After receiving critical feedback from the client, Björn took the time between the Sprint Review and Sprint Retrospective to address some issues. He is uneasy because the client complained about features he worked on. The time seems insufficient, and he starts wondering: "Damn it! I have no time to work. Now, we will have this stupid Sprint Retrospective."
Björn sees no value in the Sprint Retrospective; he wants to skip it and keep working on something else. Without hesitation, he calls Floki the Scrum Master.
Björn: "Hey, Floki. May I skip the retro today? I've got a lot on my plate, and I really don't want to be in a room for 2 hours bullshitting around."
Floki: "Bullshitting around? What's that?"
Björn: "Come on! Let's be honest with ourselves. We stay in this room for 2 hours, complain, curse a bit, and give flowers to each other. Then, two weeks later, the same happens. What's the point?"
Floki: "Björn, you know we are very picky about Scrum, and the Sprint Retrospective is a mandatory event. I am sorry, but you cannot skip it. Please, share your frustration with the team during the event."
Björn: "I'm tired of this. Meetings, meetings, and more meetings. I've got work to do, and I see no value in gazillions of meetings."
Now, let me ask you a simple question. What's the point of doing a Sprint Retrospective? Take your time before you answer it. During this article, I want to share what is not a Sprint Retrospective and how you can benefit from great ones.
What's Not a Sprint Retrospective?
Although many Retrospectives become a blame game and nothing happens, that's a massive anti-pattern. This event isn't the moment to complain and become powerless.
A bad Sprint Retrospective will end up with the following:
Talk, talk, talk: the team exchanges about everything, but they don't come to a point or cannot agree upon anything.
Powerless: if the world outside were sunnier, we would be happier. When the attitude is about complaining about external factors, the team becomes powerless.
No clear actions: even after a long talk, the team doesn't commit to any action for the next Sprint. Team members leave the retro with empty hands and a bitter taste in their mouths; they may wonder, "have we just wasted two hours of our lives?"
Without clear actions, Sprint Retrospectives are a waste of time.
What's a Sprint Retrospective?
What is the purpose of a Sprint Retrospective? Let's have a quick look at the Scrum Guide, 2020.
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
It sounds straightforward, right? As a team, we want to be proud of what we create and be more effective in working together. That's why the Sprint Retrospective exists; we give time to ourselves to evaluate how we function as a team and how we can become a bit better.
A common mistake of a retrospective is trying to solve everything at once, which will only overwhelm the team. Like product development, we should have a vision and then, step by step, get closer. A great Sprint Retrospective results in small steps that help the team function a little better.
Successful Sprint Retrospectives in 5 Steps
I've been working with Scrum for around a decade. It means I've been to incredible and horrible Sprint Retrospectives. Some of them I facilitated, and some I acted as a participant. I am not a Scrum Master or an Agile Coach, but I love helping teams become better. That's why I am super enthusiastic about retrospectives; I perceive them as an excellent opportunity to improve as a team.
Let me share my recipe for successful Sprint Retrospectives. It works well for the people who work with me and me, and maybe it helps you as well.
1. Set the Stage
A vital part of any meeting is to ensure participants are mentally present. In other words, their attention goes entirely to the meeting. Therefore, helping people arrive at the meeting is crucial. I like doing the following steps:
Prime directive and goal: make it a safe environment. It may become repetitive, but I experienced more openness once I stated how the event works; here is an example: "Goal: We agree on actions to improve as a team. Prime Directive: Regardless of what we discover today, we understand and truly believe that everyone did the best job they could."
Make it funny: help the team distract and be relaxed. You can make a 3 minutes game or something funny. For example, ask everyone to make the emoji face you present. It makes a massive difference in the room.
Tune in: let everyone connect to the event. You can use several ways for that; for example, describe the last Sprint with an image or three words. Give the team 2 minutes to prepare and 10 minutes to tune in.
2. Evaluate the Last Actions
As I mentioned before, great retrospectives result in clear actions. However, defining the actions isn't enough; you have to evaluate whether they were done or not.
After the tune-in, it's time to look at the previously agreed actions and navigate the results. What did the team do about them? I like keeping it simple; a Kanban Board is enough, open, keep, done, drop. The point is to evaluate whether it was beneficial for the team or not.
Warning: if the team constantly skips actions, you need to review its reason.
3. Generate Insights
Everyone sees the world from different perspectives. The retrospective is the moment to share how each member sees the last Sprint. This part is potentially the longest one of the events. There are several ways of generating insights. The most important is to ensure everyone has the chance to share what happened during the Sprint from their perspective openly.
Here are some dynamics I like using:
Sprint Timeline: draw a matrix where X represents the time and Y the mood. Invite each team member to draw their Sprint timeline and share the highlights and lowlights. This technique is helpful and open.
The sailing boat: draw a boat, wind, anchor, sharks, and an island. Give the team members 5 minutes to collect ideas and 20 minutes to share. The anchor represents what slowed down, while the wind means what speeded up. The shark relates to the potential risks for the next Sprint, and the Island places the opportunities. This technique is also practical and often quite revealing.
Keep, Drop, Improve, Start: looking at the team's collaboration, what should they continue the way they are, stop at all, make it a little better, or start doing? Give each member 5 minutes to prepare and 20 minutes to share. This method is straightforward and valuable.
There are tons of dynamics you can use. Each situation is different; you should evaluate what makes sense for you and pick the most suitable option.
4. Define Actions
Talking about the last Sprint isn't enough for a successful retrospective. After you generate insights, it's time to define the actions you want to carry over the next Sprint. Be sure the agreed action is achievable during your next cycle.
Agreeing upon actions can be tricky. Before trying to commit to anything, I'd suggest doing the following:
Cluster: the team may share common points; try clustering them to facilitate the discussion.
Prioritize: As you have clustered, you need to choose where to put your attention. You don't need to talk about all identified items but choose what to explore deeper. You can either decide spontaneously or do a dot voting, for example. It depends on how your team functions and its size.
Discuss: Once you know where to put your energy, it's time to discuss with your team and identify the bottlenecks. Gaining clarity is the goal of this part.
Agree on actions: What next step can you take to improve? Set a measure for that. Ensure your definition is actionable and it has an owner.
A common mistake is defining too many actions or, even worse, putting dependencies outside the teams' influence. Generally, two or three actions per Sprint are more than enough.
5. Close the Sprint Retrospective
After you agree upon actions, you need to close the session. I like closing in a positive mood to ensure the next Sprint starts well, but you can explore different closing styles.
I call the closing part a tune-out. Let me share some approaches you could use:
Kudos: invite team members to give kudos to each other. Positive feedback boosts the mood.
Take away: ask everyone to answer these questions: What will I do differently? What will we do differently as a team? This format is more on a commitment level.
Confidence: You can evaluate how the team feels for the next Sprint. You can ask them how confident they are for the next interaction on a scale from 1 (not confident at all) to 5 (totally confident). Encourage them to say why; this will help you define how to act during the Sprint.
Feedback: If you want to understand how the team perceived the retrospective, ask them that. For example, how satisfied are you with the value of this session on a scale from 1 (totally unsatisfied) to 5 (totally satisfied)? Invite them to share the reason behind it; this will help you design better retrospectives next time.
Final Thoughts
Retrospectives shouldn't be boring, tiring, or annoying. The great ones are engaging, motivating, and encouraging.
High-performing teams don't shy away from conflicts. On the contrary, they embrace conflicts to figure out how to work better together.
Use retrospectives to ensure everyone knows how everyone sees the world. Identify conflicts, and address them. The more you do that, the stronger the team gets.
Did you like this post? What about becoming a Medium member to benefit from unlimited reading? By doing that, you also support writers like me and thousands of others 😊