Retrospective Experience — Halloween Special
Running a Halloween Themed Retrospective! The fun way of working, right?
As you know, Sprint retrospective is one of the most important events for the Scrum Team. I am sure you don’t skip it. Because I have a great idea for you to try for the retro :)
The end of the sprint was approaching, and I was researching which technique to try next when I saw this blog. I felt I had to try.
Thankfully the team is used to the 5 stages technique, so after queuing up a few spooky songs, and introducing the theme, give it a go!
Now, this kind of retrospective may seem a little abstract or off the wall, and believe me, I have had many a strange look by teams experiencing my themed retrospectives for the first time. But do not worry! I promise you that running an innovative retrospective like this will generate great, innovative ideas and improve the bond within your team.
Stage 1 — Setting the Stage — Halloween Treats
Each team member should think of a Halloween treat to describe how the last sprint went by adding their avatar/stamp on the ghost that best describes how they are feeling today.
I like to start retrospectives in a fun way to get the team warmed up and relaxed. I do this by using an ice-breaker or a Sprint Metaphor.
Stage 2 — Gathering Data — What’s sweet last sprint? and Ghost Stories
Halloween and no candies? Impossible! Drop some kudos in the candy jar to let them know how much their contributions mean to you. Next, make notes on what went well in the past sprint.
Ghost Stories, Okay, this is scary, but it has to be done :)
Each team member had to come up with a scary story (which could have a happy ending) describing a key event in the last sprint. This can have a happy or a scary (sad) ending but should cover the events during the sprint.
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)
Stage 4 — Decide what to do- What’s cooking for the next Sprint?
Improvement actions for the next Sprint that you chose as a team.
Now that the team has come up with an abundance of ideas try to group the ones that are the same (or very similar).
The team will now have some options to choose to improve. For a team of 8 people, there could be up to 16 ideas.
If you have grouped your items and want to do dot voting, you can pick the top 3, and there you have your 3improvements to take forward into the next sprint, as decided by the team.
Stage 5 — Closing the Retrospective — Feedback
Asking for feedback is important to improve as a team. As a Scrum Master you may want to improve the flow, process, and facilitating skills. You can gain insight from your team.
Other Ideas
Play Music — Rather than the team sitting in silence while thinking, give them a length or one, two, or three songs. As it’s a Halloween theme, think Thriller (the shorter radio version!).
Halloween Treats — Stick some sweets in the middle of the table, it’s the end of the sprint, and your team deserves it! (If you are facilitating the retro in person)
Don’t forget to take a team photo at the end:) and paste it into the team board.
Dress Up — Why not go full Halloween on this? (Maybe not)
Again, this kind of retrospective may seem a little abstract or off the wall, and believe me, you will have a great experience.
Resource:
Inspired by the miroverse template: A Halloween Retro by Clyde D’Souza
Inspired by the Figma community template.
Please share your feedback and other techniques you used in the comments.
Thanks for reading!
