The drive to inspect and adapt is one of the most important aspects of agile software development. A great way to bake this approach into your process is by having regular retrospective meetings that engage and challenge the team to solve their own problems and make things better. However, these meetings can be difficult to run well and drive improvement. In fact, many teams sleepwalk through sessions, treating them as a box-ticking exercise that signals the end of the iteration.
Maybe it’s time we tried a bit harder to make sprint retrospective meetings work?
In this workshop, Chris explained how to put together an awesome sprint retrospective. Attendees tried novel activities that can be used to gather information and challenge team members to consider problems from a new angle.