It seems like the importance of having Retrospectives in Agile teams has been covered, and more and more teams understand the reasons behind it and believe in them. But the more Retrospectives you've completed, the more difficult it becomes to keep teams engaged.
For this reason I feel it is important to start discussing the importance of using various Retrospective techniques. If you are still not sure, why it's NOT ok to use the same technique every time, keep reading.
Recently we have started to collect ideas for Retrospectives and use different techniques to look at the previous sprints with our teams. It had a great positive impact on how teams look at Retrospectives in general. Of course, this exercise involves a lot of preparation work in advance, but results are worth it.
Here is why I think it is extremely important to spice up your Scrum Master "toolbox" with new Retrospective techniques:
Even if changing techniques is intimidating at first as you need to be more prepared for each meeting (and we all know that the time is of essence for us), try it once, and you'll get into it.
If you need help running a new Retrospective technique, check out my free guide to engaging Retrospectives that will give you great tips on how to run your first Retro or just a new technique you haven't tried before.
Professional Scrum Master II