Retrospective: looking back on or dealing with past events or situations. An essential practice to make the future better.
It’s a pretty tired discussion in my house: Multi-threading, multi-tasking, the cost of context switching, etc. Especially with a teenager at the dinner table… So I found a nifty exercise to drive the point home. Supplies Needed: One volunteer who considers themselves an expert context-switcher / multi-threader Three decks of …
…What could possibly go wrong? Here’s an idea: conduct a “pre-mortem” to prepare. The gist of the activity is to consider all that could possibly “go wrong.” Then the conversation switches to a mitigation and action plan. (Maybe the team even does a pre-mortem activity at Lift-Off or at Sprint 0?)
Opportunities for failure lurk everywhere. In projects, in code roll-outs, in team member interactions. We’re going to try a lot of new things. Some will work. Some won’t. We don’t set out to fail, but when we do, how will we handle it?
Overview The goal of the retro is to empower teams (groups of people focused on a common goal) to control their own destiny. In retrospectives teams look for primarily for improvement actions that they can do themselves. If they want to try a different way of working, it’s up to them …
