Image by cindy47452 via Flickr
During our November meeting of the Ottawa Scrum Users Group, I talked a bit about how retrospectives should be used to do more than just discover things that aren’t working well and ways to improve them. Often a team can identify problems but do not have the ability to make the changes to correct the problem for various organizational reasons.
The alternate approach is to instead concentrate on the bright spots. These are the things that are working well and overcoming challenges. If you can replicate the conditions and settings that produce these successes, then you may not need to address the things that are getting in your way.
- Quick introduction to describe the retrospective
- Thank you notes between team members to get everyone engaged
- Brainstorming on all the things we have done well in the recent past
- Envisioning exercise to imagine the places we want to get to and how we will get there
- Grouping of these ideas into common themes
- Selection of top 2 things to concentrate on as we finished the release
Initially, there were a lot of looks of disbelief and a few chuckles as the retrospective was introduced. After all, it is a little unusual (but not wrong!) for an engineering team to focus positive emotions outwardly. But it really didn’t take long for people to throw themselves into it. A lot of the thank you notes focused on effort people put into the iteration. My favourite when something like this:
Thanks for always being there to review my code even when you were very busy.
Your pal, _______
From that point on, the team went from positive to positive. A great dynamic was built as one person’s ideas quickly built upon others. By the time we started the grouping exercise, even the quietest person was taking a leading role and stepping up for their turn with the stickies on the wall.
In addition to the renewed energy levels, our outcomes from the retrospective were well-focused and easily implementable by the team:
- continue to pair up / triple up on stories to decrease the time to complete features and to reduce work in progress
- continue to communicate often and closely between everyone with a stake in the story
All-in-all, it was a very successful experiment and a retrospective format that we will often repeat. If your retrospectives are becoming stale or not providing your team with what they need, consider running one based on appreciative inquiry. It is a lot easier than you may thing.