Sounds crazy doesn't it? Afterall, the retrospective influences change which we all know is highly valuable. In an ideal world, a retrospective would include lots of great ideas for improvement that were actually actioned. Unfortunately, that doesn't always happen. Some teams get stuck and struggle to come up with new exciting improvement items. Other teams have great ideas but they never get around to actually implementing them. As a Scrum Master, you could continue to

This blog is NOT about distributed teams and running distributed retrospectives. This blog IS about collocated or kinda collocated teams and the benefits of holding an off-site retrospective. Before we get into it, it's important to note that some organizations frown on off-site retrospectives. Management can sometimes get nervous when they can't actually see the teams or have arms length access to them. While an off-site retrospective can turn into an afternoon of alco

Multi Team Retrospectives can be very different than individual team retrospectives. Simply put, encompassing more people introduces challenges. Various Agile methodologies that focus on scaling deem it necessary to conduct multi team retrospectives. For example, SAFe prescribes that an I&A (Inspect & Adapt) workshop is run at the end of every PI (Program Increment) which can work out to approximately every 3 months. It can be a daunting task to hear the voice of over 100

Let's face it. Retrospectives can quickly become monotonous. If you don't change it up, the value you get out of it will quickly diminish. The facilitator role is typically taken on by the ScrumMaster. But in some cases the Coach (if there is one) will get things started and then transition over to the ScrumMaster. The facilitator has a difficult task because they are trying to keep things fresh so they can maximize the benefit from a Retrospective. But if you're holding a