Scrum Exposes Bad Processes and Obstacles
In our last post, we discussed the Agile Retrospective technique of Start, Stop, Continue or SSC. In this, post we discuss a technique first tried by Pete Deemer [CST, co-leader of Yahoo's implementation of Scrum].
Often, as the end of a sprint, the team comes back and says things like
- Its more stressful in Agile
- Things are worse than before
- Agile does not work
- We were better off before
If as a Process Coach or Scrum Master you hear something like this, you can try this in your retrospectives:
- Ask the team to collectively come up with a list of things they thing are better than before/ is working well and also what is not working well/ worse than before. So, you have two lists : Better and Worse.
- Now ask each member to mark each item on both the lists from three possible options : Caused by Scrum [C]/ Agile, Exposed/ Made Visible by Scrum or Agile [E], Does not relate to Scrum/ Agile [U].
- Compile the score and let there be pin drop silence in the retrospective.
- The team may find a lot of C’s on the “What’s Working Well or is Better than Before” side of the board, and a lot of E’s on the “What Could Work Better or What is Worse than Before ”; this is good news, even if the “What Could Work Better” list is a long one, because the first step to solving underlying issues is making them visible, and Scrum is a powerful catalyst for that.
- The team’s opinion and acceptance of Agile/ Scrum would have undergone a complete 180 degrees turn.
It is often useful to keep a snapshot of the whiteboard where these lists are maintained and keep revisiting them in each of the Retrospectives. This is especially useful for the teams which are transitioning to Scrum or Agile way of working.