Data Driven Retrospectives - Where people meet metrics!
This will fun filled simulation workshop is one I've run with many Agile user groups. It is so effective as its come from REAL retrospectives I've facilitated with REAL teams that have achieved REAL results.
The session will begin by setting the scene to give some context, giving the audience a brief background of what data driven retrospectives are and why do them.
Then we dive straight into the activities. The participants will be split into 3 teams. They will be given a scenario that they can all associate with from real life, a board workflow and some metrics captured.
What lies ahead will then be 3 action packed, time boxed rounds that encourage fun, energy and quick collaboration between teams. The teams will analyse their data, identify problems, suggest changes and convert them to REAL actionable tasks using their own board.
After each round, the team share the improvement changes they have made with the whole group, what it did for their results using their board as a reference and what they will consider next.
As the rounds continue the teams will visibly see the value on the mix of people, collaboration and data in their results and continuous improvement as a unit.
The session will end with a group reelection on the past 90 minutes which will empathise that this isn't a Kanban activity. It is an activity people and teams everywhere can benefit from. Scrum teams can do this, ScrumBan teams can do this, Waterfall teams using a Kanban board can do this.
The principles will be the same:
***** People + Collaboration + Real data = Continuous Improvement( Whatever your Flavour) ****
Oh I probably should. mention the small matter of HAPPY MOTIVATED PEOPLE too.
NOTE - It's currently 8.58pm on submission deadline day when I am submitting this (Sept 10) so vote for this submission because everyone loves Just in Time right :)
Outline/Structure of the Workshop
Introduction to Data Driven Retrospectives - 10 MINS (all) **Fun + Energy reminder **
Split into 3 teams and brief - 10 MINS (3 teams)
Round 1 - Team use data to analyse and problem solve - 10 MINS (all 3 teams)
Round 1 feedback - 10 MINS (2 mins per team plus contingency)
Round 2 - Introduce changes, analyse results and problem solve- 10 MINS (all 3 teams)
Round 2 feedback - 10 MINS (2 mins per team plus contingency)
Round 3 - Final changes, analyse results and problem solve - 10 MINS (all 3 teams)
Round 3 feedback - 10 MINS (2 mins per team plus contingency)
Learnings/Takeaways - group replay of learnings, final summary a) Any team can use this b) Understand important combo of people and data coming together 5 MINS
*** NOTE - Some contingency time is built in here, but this can be flexed to fill the slot if needed. Having done this numerous times, give and take 5 mins either side of the structure/times above are accurate. ***
What are Data Driven Retrospectives and why do them - The Audience/participants will get a little bit of theory but this is hands on and practical rather than a slide deck. So rather than listen to a lecture they will get a real life experience
How to run a Data Driven Retrospective - Audience will go away knowing how to apply something that will work in their own teams. Again benefitting from doing rather than listening to make the idea stick so they feel confident to go away and try it.
Knowledge that I will share from my first hand experience about how this has worked with real teams! . This will be a linked theme throughout; during the introduction, throughout every round and in the takeaways at the end so it cements the idea in their head that this is from the real world, giving them the confidence to go and try it in their real world
A 'How to' Simple step by step handout of how to run this activity with their own teams - this will help consolidate/refresh the audience/participants on what they have learnt once they've had a night's sleep :)
Whilst David Anderson eluded to this sort of activity in the blue 'Kanban' book, the audience/participants will see how I've took the ball and ran with it here. Defining an easy yet solid structure of how to run this activity to make sure the people element is just as focused as the data/metrics part of it because data is great but we need people to collaborate to look at the data to push the boundaries and figure out how these problems they identify can be solved.
Anyone working on an Agile team in any role - eg Developers, BAs, DevOps, Scrum Master, Product Owner, any other wonderful titles :)