Welcome back to this series on how to run awesome, super effective agile scrum retrospective meetings! In this bunch of pages, I’ll show you how you the best way to get the most out of your retrospective meetings + give you some pro tips and hints along the way.
In the previous part (here) you learned what retrospectives are and when you should run them. You also learn how long you should keep them and also about a certain promise your boss must give you for these meetings to work…. check it out now if you haven’t already!
It may surprise you, but there is a method you can use, a “retrospective recipe”. Yes, that’s right, there is a proven way to run your meeting!
A method to the madness if you will.
You gather your team in the meeting room…
….. everyone’s sitting ’round the conference table.
You start by drawing some columns on the whiteboard ::: What was good? | What was bad? | What do we want more of?
Then you ask the group to fill in the blanks….
…..and after some asking (begging, pleading) on your part, you get a bunch of responses in return.
Problem is these responses tend to be superficial and barely scratch the surface of any actual issues. At a quick glance, they may pass for something constructive, but in reality…. I doubt it.
So instead of finding causes (and coming up with brilliant, awesome ideas), most retrospectives end up with these shallow, easy-to-fix, band-aid solutions.
And when the meeting is finally over, everyone leaves wondering what the heck it was all about.
This is what I think: People are not challenged enough! The retro has become yet another ceremony. Just another duty to perform. Good|Bad|More|Less. Blargh.
Follow the process. Perform the ceremony.
I may be exaggerating a bit, sorry about that. Maybe your retros aren’t like this? Maybe you are getting incredible results out of them? Maybe you’re one of the few that actually know how to make it work? If that’s the case: please stop reading right now and get back to it! 🙂
Otherwise — It’s time to shake things up a bit, time to try something new!
THE 5 STEP SCRUM RETROSPECTIVE RECIPE
Your retrospective meeting flows through five steps. The result from each step is used as input in the next. For now, think of these steps as your meeting agenda (you’ll learn more about effective agendas in a later part).
To recap: First set the stage, then gather data from the team’s work. Study that data and come up with improvements. Then pick some actions to work with and then finally, wrap up the meeting.
(Btw, I first heard about this meeting format from the book Agile Retrospectives: Making Good Teams Great (Derby/Larsen, 2006). I don’t know if that’s the true origin though, but the book it well worth a read.)
Tip: Download the cheat sheet It’s a nice summary with all major takeaways from this series. It works as a handy guide when you create and run your meetings.
Let’s dive into the first part of the meeting (“set the stage”) right away!
The first step of the retrospective recipe is called Set the Stage.
Your goal here is to create a safe and productive meeting and get the group to start talking. Another goal is to get them to agree to certain things.
Setting the stage. Make a good job here and the rest of the meeting just will just rock.
Setting the stage should be kept short: spend maybe five to ten minutes on this (I’m assuming a one-hour meeting here).
This part lays the ground for the rest of the meeting, so this is very important. Make sure you don’t skip anything in this step!
By the way, if you’re feeling confused right now about things like ground rules and agendas — don’t worry, we’ll cover everything about that stuff later. Your questions will be answered, so for now just tag along.
Anyway, that’s it for Set the Stage.
You may think that this is all pretty rigid. You’re probably right, but what I’m doing here is giving you a step by step guide. Once you have used this a few times, you should start experimenting. Besides, if you read the rest of this series, I’ll give you lots of examples of how you can tweak this and what activities you can use.
I'm a developer, running my consulting business while raising two daughters. The little one is 9 months and the big one four years. Yikes, time flies! Wish I had more time to spend with them.