For my sins I love Bon Jovi! Maybe not so much the recent stuff, but they have some real classics. I have seen them in concert many times and I have to admit they are a real crowd pleaser and play for about 3 hours.
Whilst thinking about my teams retrospective this week and the fact I like to inflict upon them my sad hobbies and obsessions, I decided to do one on Bon Jovi.
I am going to keep sharing these with you because I want people to experiment and try different ways of helping teams to continuously improve. They can also be fun if the sprint has been a hard slog.
Here are the headings that I used.
I rated moral as follows:
I did have the music playing to motivate, but we did have one anti Bon Jovi fan. I might do AC/DC next as that is his favourite band.
I gave the team extra kudos if they could get song titles in their thoughts and comments. Ultimately we ended up with a set of actions for us to take forward in the next sprint.
If one was not enough…
I did a second retro this week for a different team.
The team has recently merged together with another team and are still looking to refine their ways of working together, and so I wanted the retrospective to be based upon how they work as a system.
I used a Scrum Image and asked them to use sticky dots to put where they thought the problems lie. They got two green dots and a red dot with signified a major problem. Green dots are still issues in this example, just not as bad as red.
I then got them to give me the headlines of the problems they encountered. An example of this might be ‘User stories are not coming in regularly enough from the clients’.
I got the team to then break into three groups and we used A3 thinking to look at the problem and come up with potential counter measures. A3 thinking is great because it means we can post them on the team wall and then validate the learning's at the end of the next sprint. I also wanted to teach them a different technique and really get them thinking about the challenges we have have. Quite often the problem in front of us is a symptom of a deeper root cause. Techniques such as the 5 whys can help the team delve down.
All in all I had a great couple of retrospectives this week. I will need to keep an eye on the teams as sometimes actions do get overlooked, but a little poke every now and again ensures that they keep driving them forwards.
One of my ScrumMasters come across this great website on retrospectives. It is worth checking it out for new idea.
Keep improving people!!
Email Helen Meek
© Copyright 2017 RippleRock