It’s one of the most common complaints I hear from development teams: “Urgh! We have far too many meetings.” It’s not often true but that is their perception because the meetings felt boring and wasteful.
Meetings don’t have to be like that. I’ve just started reading a book called Meeting Design: For Managers, Makers and Everyone by Kevin M Hoffman (Two Waves Books, 2018) which I’m hoping will help me plan more productive, more meaningful gatherings in the future.
In this post, I offer a few simple rules to help meeting feel more manageable.
The sailboat retrospective is a model that I especially like to use at the end of significant chunks of work, like a release or the end of an epic or the end of a project. But it could be used at any time, especially if there is a need to better understand project objectives, risks, hindrances and helpers.
I like to use this model for post release retrospectives because it helps the team to focus on lessons learned around unexpected risks, the things that slowed the team down and celebrate the things had really helped us.