Retrospectives and What They Can Tell Us
Retrospectives are one of the events in Scrum which give opportunities to a Scrum Team to inspect itself and create a plan for improvement. However, very often, this event tends to become boring and get away from the answers to three basic questions, What Went Good, What Went Bad and What To Improve. For that matter, at times team may not have food for thought and hence they disengage from these questions. So, what needs to be done or in fact, what can be done in such scenarios? Well, Retrospectives are all about figuring out what needs to be done. But, how do you know what to do, if you do not know what you did?. For starters, measuring a team’s progress on Sprint by Sprint basis might be a solution. Having such data might not solve many problems, but, it could certainly expose them. There are three basic metrics, which have been found to be beneficial for teams’ progress and also thought triggers in Retrospectives. As Mike Cohn once said, measure only what can be measured. Metrics can be misleading, hence it is up to us to measure what makes sense and use it to improve the team.
Outline/structure of the Session
- Introduction (5 min)
- Horror retrospectives (15 min)
- To measure or not to measure, that is the question (10 Min)
- The 3 musketeers of Retrospectives (10 min)
- Q&A and close out (5min)
- Learn to calibrate “The Boring Index” of Retrospectives.
- Learn about the “Facts” & “Myths” of Data Gathering for Retrospectives
- Walk-Away with three recommended metrics to facilitate goal oriented Retrospectives.
individual contributors, managers, Agile coaches, Scrum masters, POs