A 5-why root cause analysis retrospective
The idea For quite a while I have been waiting for an opportunity to try a 5-why root cause analysis in a sprint retrospective. The 5-why analysis has its origins within Toyota and lean manufacturing...
View ArticleEven done is never done
A “done” definition in an Agile project is a statement that the team use to measure whether they’ve met all of the requirements for completing a userstory / feature (and in some cases completing an...
View ArticleChart your happiness
We all know or at least we should know that retrospectives are one of the Agile recipe’s 11 secret herbs and spices. It performs a valuable role in the improvement of the team and its practices, as...
View ArticleStand by your values!
I recently ran a “get to know your team” session to help a team with lots of new members to better understand each other’s history, motivations, likes and dislikes. We did a number of exercises...
View ArticleAre your votes going to waste?
It’s common among Agile teams to use some form of voting to make decisions, and that’s especially true for retrospectives where the team as a whole decides what to fix next. Over the years I have...
View ArticleDeep tissue massage retrospective
Even with high performing teams sometimes there are common themes coming up again and again in each retrospective. Much like a tight spot in a muscle that keeps lingering around (until we get a good...
View ArticleFinding it hard to visualise improvement ideas?… Try idea balloons!
Are you tired of capturing ideas and experiments that come out of your retrospectives only to forget about them after a couple of days? Do your improvement ideas get lost in waves of sticky-notes and...
View ArticleHow to Avoid Waste – a Lean Retrospective
In Implementing Lean Software Development: From Concept to Cash Mary and Tom Poppendieck categorised waste encountered in software development into: Partially Done Work Is work going from beginning to...
View Article