The good, the bad, and the ugly
I seem to have been running a lot of retrospectives lately. And yes, I just used an Oxford comma. Get over it.
In case you don’t know what that means, a retrospective (or a ‘retro’ for short) is a meeting-come-workshop where you look back on work you’ve done, as a team, and try to identify ways you could be better in future.
In agile methodologies, you can hold retros pretty regularly. With Scrum, you’d hold one at the end of every sprint – typically every 2 weeks – so you can get feedback quickly and adjust course immediately.
Think guiding a canoe through rapids; if you can’t change course quickly, you are going to hit a rock (a fairly common metaphor for retros uses a sailboat, as above) pretty soon, and pretty fatally.
Continue reading “Running an asynchronous retrospective”