AGILE IN ACTION

Saturday, 15 December 2007

Looping the loop

Posted by Simon Baker

All teams have blips. I sensed growing frustration in the team over the last few iterations - sniping, bickering, moaning, negative comments. Morale was starting to be affected. When the team norms were breaking down and a lack of respect started to emerge I decided to intervene and focus the next retrospective on getting to the root of the problem.

General frustrations were around learning a new technology (Grails), people perceiving others to be uncommitted, people cutting corners and not being held accountable, ambiguous information sharing and story myopia leading to a lack of teamwork. Chatting about it all reminded people of their responsibilities to the team and helped people generate some great yet simple ideas for making things better and getting the team back of track.

Connected learning from retrospectives

The retrospective cleared the air and we’ve made some small changes that have completely transformed the team. The small changes so far include:

  • A more conscious effort to vertically slice stories to create opportunities for collaboration with (and obtain feedback) from testers, the graphics designer and the product owner. The rule of thumb is at least one slice a day. People are taking a little time now to think how they will build the story out using slices before jumping in.

  • In the daily standup when story owners talk about their card, they now mention their pairing partner and speak only in terms of the acceptance tests.

  • Again, in the daily stand-up story owners request any specific expertise they might require during the day and when they think they will need it. At the end of the stand-up when we form pairs, the team organizes itself so that the right skills can get to the coalface on each card.

  • Pairing is more promiscuous. The Grails expertise and CSS expertise are now being transferred more effectively spreading the knowledge and building skills redundancy into the team.

These are simple changes we’ve made many times before with other teams. Sometimes blips happen because we take our eye off the team. With respect and trust restored, the team norms have returned. There’s a stronger sense of team. Everyone is asking for help and offering help. Collaboration has gone through the roof. The net results - the team is happy, healthy and hustling.