I often tell Agile coaches to start with a health check on the teams they are about to coach.
People think this a health check is a great idea and they often research complex algorithms and assessment tools.
But that is really hard work for you and the team. So at our coaching clinic we tried a lazier alternative – I put these conversation starter kits up on the wall.
Continue reading “Quick and easy health checks for Agile teams”
A retrospective is a meeting where the team stop working and take a step back to review how well they are working and what they can do to improve.
It is generally done every sprint (or every two weeks if there is no sprinting going on).
The theory is easy – the team share their views on what went well in the last fortnight, what did not go well and what they should keep doing or change as a result.
In practice though, it often turns into a therapy session where people share opinions about the way the world is really bad (or even how the team is awesome) and then they wander off without taking on any action items.
So when your team have lost their mojo and the retros are getting stale maybe it is time to do a retro on the retro. Similarly, when you first start out as a team, it is often good to define what you might want to get from your retro.
Continue reading “Do you get value from your retrospective?”
One of the most powerful components of agile approaches is the retrospective. I often think that even if a team does not know what “agile” is, if that team pauses on a regular basis and reflects on how to get better at what they do, then they would invent most of the other agile practices for themselves.
But stopping on a regular basis can get stale after a while, so I thought I would sharer some slightly different sets of questions that you can use to keep things fresh.
