3 tips to run a better Scrum Retrospective

Need a prescription to gain 20/20 hindsight in your Scrum Retrospective?

If you’ve been involved with multiple scrum teams, especially those that have been running for some time, there’s a good chance you’ve had one of ‘those’ retrospectives. The same feedback keeps getting raised, stifled conversations causing tensions to run high and psychological safety to plummet.

Maybe even worse, your team has just given up and refuses to participate, claiming the ceremony adds no value.

I’ve certainly found myself in this situation a few times, and although it should’ve been caught earlier it can serve as a timely reminder to go back to the roots of what a retrospective is meant to be in the first place; a safe, engaging space to focus on continuous improvement.

With that in mind, here are a few practical tips and tricks I’ve employed in my teams to get people back to the table and ensure the right conversations are being held.

Every Scrum Master’s worst nightmare; a disengaged team

Tip 1 – Give participants different ways to express themselves

One of the most common symptoms of a stale retrospective, in my view, is when the facilitator runs the ceremony in the same way, the same format, the same template, the same dollar-store snake lollies in the bowl at the centre of the table, you name it. If you keep asking the same questions, you’re inevitably going to receive the same answers and feedback. This locks you into a cultural pattern that can become difficult to correct.

There are literally hundreds of ways you can setup a retrospective, with each format focusing on a particular analogy or set of questions.

You can also switch up the way you facilitate the session itself. Maybe you can alternate between voting for the top 3 most important topics, and going wide by reading every piece of feedback individually to give participants equal share of voice. This level of nuance can become incredibly powerful if you have some dominant characters in the room that tend to speak before others.

Tip 2 – Don’t be afraid to focus on burning topics in a Scrum Retrospective

Sometimes flexibility in your facilitation methods can be a double-edged sword, however, and by going too open-ended with your feedback you can wind up overwhelming your participants with choices. Especially if there are some elephants in the room, it can be beneficial to focus on those topics and ensure everyone has their say.

As is the case with all the advice here, however, there is definitely a balance you must strike to ensure your participants still have a chance to express themselves with their own topics. You aren’t all-seeing and all-knowing, so try to guide and constantly validate the assumptions in the room.

Tip 3 – Split your feedback between localised and systemic

In a perfect world, we could solve all of the team’s problems during a retrospective. However, we know this isn’t always the case as the solutions to some problems may be more complex than we had hoped, or the right people simply aren’t present at the time.

As a facilitator, the Scrum Master can face this challenge head-on by accepting this scenario and guide it by actively categorising feedback that can and can not be addressed in that forum. In a pinch, this can help the team focus on the things that they can control, but equally as important is that you as a Scrum Master take the more systemic issues away as action items to ensure we aren’t always solving our problems locally.

In closing

One of the core concepts of agile is continuous improvement, which therefore makes it vital for any Scrum Master (or Retrospective facilitator) to ensure that flow of feedback is maintained. Next time you find your team to have low energy, or if the same old conversations keep coming up, mix it up!

Brad Quirk

Brad Quirk is a data-driven Agile Coach with a proven track record of executing large-scale organizational change across various industries, helming some of Australia's largest transformation programs. Brad has also developed several Atlassian Jira apps, including the Dependency Mapper, which is among the Top 20% of apps installed on the Atlassian Marketplace and has also been featured on Atlassian's 'Staff Picked' list of shortlisted apps. Brad has a heavy focus on early agile adoption, creating workplace cultures that embrace change, and highlighting improvement opportunities through engaging and interactive data visualizations. He promotes the best use of various methodologies across all levels of management, including Scrum, SAFe, and Kanban. In his spare time, he enjoys working out, watching pro wrestling, and managing the collective chaos with his wife, daughter, two cats, two dogs, and three horses.


Get a Free $2000 Discovery Call to Accelerate Your Success