As time goes by, one key observation from team retrospectives is – the core issues do not seem to surface during retrospectives. Most of the issues are superficial or “it was all the the other teams fault”.
Two key reasons for this lack of insight seems to be …
* Lack of data or not using the data from the just concluded iteration/sprint
* Do not remember important events from the just concluded iteration/sprint
So it’s important for the facilitator to guide the team to get to these insights. Here are some techniques to try…
* Create a time line on the board for the just concluded iteration/sprint
* Ask the team to remember events that happened from the beginning of iteration/sprint and post them on the time line.
* Bring up the burndown chart for the recently concluded iteration/sprint
* Ask the team on reflect on the ups and downs of the graph
This should help the team to reflect more deeply on what truly occurred during the iteration/sprint. Once the team has those insights and have voted on key items (if there are too many), try root cause analysis. This almost always help identifying dealing with the real problem rather than a symptom(s) of a problem.