The end of the sprint was approaching and I was researching which technique to try next, when I saw this tweet from @aaronjmckenna which I had to try:
— Aaron McKenna (@aaronjmckenna) October 31, 2014
Thankfully the team are used to the 5 stages technique so after getting some speakers from IT, queuing up a few spooky songs and introducing the theme, we plowed head first into it.
Stage 1 – Setting the Scene – Halloween Treats
Each team member should think of a Halloween treat to describe how the last sprint went
As with all first stage techniques, this was great at getting every single member of the team to talk at least once and generally wake people up. We had some nice friendly banter at weird definitions of treats, so the team were set for the next stages.
Stage 2 – Gathering Data – Ghost Stories
Each member of the team had to come up with a scary story (which could have a happy ending) describing a key event in the last sprint
This was probably the least successful part of the retrospective as only a small number of team made an actual story. That’s a problem with either my explanation or the team, not the technique, and we still ended up with a decent set of views.
Stage 3 – Generate Insights – Trick or Treat
Each member of the team had to come up with 1 treat (something that will help improve the team) and 1 trick (something that is or could hold us back)
This worked really well as it limited everyone to just one idea. As you can see below, I also decorated the board:
Stage 4 – Decide what to do – Pick a Door
The team had to decide which doors to visit to talk about, aka dot voting
Stage 5 – Closing the Retrospective – Spook of the Sprint
Each member of the team had to thank one other member for something they did in the last sprint.
I must admit, we don’t normally do much for this part of the retrospective and we certainly don’t do anything as gushy as thanking each other, so I was a little skeptical!
I could tell by the audible groans from the team that they thought the same thing when I introduced the idea, but I’m pleased to say it was quite a positive thing. What’s more, we now have a wonderful mascot for the next sprint.
All in all, this was one of our better sprint retrospectives and I really like using a theme. Aaron’s idea of timing each thinking section with a song worked fantastically, so I’ll be looking to do that again.
I’ll also definitely be keeping an eye on his blog for any future themes to try.
What went well?
- The limit of 1 good thing and 1 bad thing helped focus the team. I’m not sure I would use this for every retrospective as it’s nice to let the team vent, but it’s a good way of getting to the most important matters.
What could I have done better?
- Given more time (and courage) it would have been nice to decorate the room a bit more;
- I’m not convinced I summarized the stories from the second stage clearly on the board, or even guided the team to use these as a basis for the next step. I think I’ll try and get the team to come up with a summary statement next time, rather than something only I understand.
What should I not do again
- Talk about writing a blog post over a week before having the time to do it!