Common retrospective actions

Retrospectives are an opportunity to reflect and learn together as a team, with the view to improving the way we work.

This is great for the early days of agile adoption as there is a crap load to do, and most of it is obvious or comes from some preexisting playbook.

What happens later though as your team hits a stable and performing cadence of delivery? How do you lever yourself up even further? What do you do when you hit the limits of your authority and influence? How do multiple teams coordinate their improvement efforts without resorting to top down command and control patters?

Tonight we are going to do an activity where we share lessons across multiple teams and tips on how to improve beyond where we are today.

Homework

Collect the last few months of your team's retrospectives and bring them along. We'll compare notes and help each other.

Agenda:

• Intro: Host to set the scene

• Activity: Create a card wall, sort things into groups

• Discussions: People cluster around their preferred topics and discuss.

• Close: So what does it all add up to? What lessons can you take back to work?