Accelerate Through Retrospectives

I had been sitting in a few team retrospectives and hearing the same old tired pattern of “what went well, what didn’t, what can we improve”. The teams were bored, i was bored, they were just doing mechanical scrum. Retrospectives are such a powerful tool to drive continuous improvement, but what i was seeing was a stagnation and the true value of this event was being lost.
End of the Sprint was coming up so as the enterprise agile coach, I thought I’d provide some of my favourite patterns and ended up providing my 20 scrum masters with a playbook  to accelerate and reinvigorate learning and improvement and provided  a years worth of retrospectives and ideas as well as links to where to find more.
I sent the presentation out and this was the email waiting for me from one of my remote teams…..

Morning Mia

I just wanted to give you feedback on how our retro went yesterday as I trialed some of the ideas in your Accelerate Through Retrospectives doc you sent out. I will admit I don’t normally get excited by this kind of stuff but after the retro yesterday I think I nearly skipped out of the room and thought wow – so changing the way we do things did make a big difference and think it will contribute to continual improvement. 

I selected the 3Ls, What went well/Should Change and the team building activity.The team was far more engaged this time and were talkative, laughing as normally all just sit around the table and say what went well/ not so well etc and just look at each other, this time there was interaction, laughter.  It was good to show that regardless of how long they have all been in the organisation everyone came up with one or two things they learned this sprint which was good.

All up was a good retro and the time went fast. So thank you for the ideas and I will try some of the others next retro



This is coaching gold so i was feeling pretty happy. I wondered if it was a one off, but to my surprise, a number of teams had picked up ideas from the presentation and implemented.

We  have a scrum master forum and each sprint teams are adding to the deck with their own patterns and variations. Its great to see them being excited about retros and really looking at ways to improve.
Here is the original slide deck, hope your teams find some inspiration as well. Would love to hear your patterns and if these helped you.

About the author

Related Posts:

What Knowledge and Experience do you need to be an Agile Coach?

To be effective, agile coaches require deep, applied expertise and experience across multiple organisations, multiple projects and industries. As the organsiation scales, the Agile Coaching Development Pathway shows the focus of the role as it scales to more responsibilities beyond being a coach of a single team and provides guidance on what knowledge and experience is required to be an Enterprise Coach.


Better together: Agile + Lean UX

How do you make Design Thinking, Lean UX, and Agile work together. Sprint 0? Design Sprints? Upfront design and planning tends to delay the delivery of value, so there must be a better way to use Scrum but also engage in discovery work at the same time without devolving into parallel design work. Integrating design, user research, and experimentation into Sprints is the key.


How do I run a Sprint Review?

The Sprint Review is one of five events in Scrum. It’s purpose is to inspect the Increment of work, get feedback, and then adapt the Product Backlog. And while many people refer to the Sprint Review as the “demo” or “showcase”, this is only one aspect of the Sprint Review.


How do I run a Daily Scrum?

Many people use the Daily Scrum to provide a status report to the Product Owner or Scrum Master, and even to stakeholders, but this event plays a more critical part in ensuring that the team continues to stay focussed on their goal and adapt their work so they improve their chance of achieving it.

search previous next tag category expand menu location phone mail time cart zoom edit close