insights you can use |
|
|
"Poor management can increase software costs more rapidly than any other factor." (Barry Boehm) Behind Closed Doors: Secrets of Great Management (Pragmatic Programmers) Archives May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 April 2006 March 2006 February 2006 January 2006 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 Contents (c) 2003-2006 Esther Derby I also publish a quarterly newsletter for people who manage in software organizations. If you'd like to receive the newsletter, drop me an email. It's on paper, so please include surface coordinates - name and full address.
Syndicate this site (XML)
Links |
Saturday, April 28, 2007
Two more ways to gather data in retrospectives
If you've been holding iteration retrospectives for a while, you know that timelines get old after a while. But when team skip the data part, each person works from his own data (which other people may not know) and his own interpretations (which other people may not share). That means that the team is less likely to come up with actions that have broad support. So here are two more fairly quick ways to gather data for an iteration retrospective. Diana describes FRIM, an activity that looks at the frequency and impact of events, impediments and boons that affected the team during the iteration. Use this as input into analysis and to decide on experiments and changes for the next iteration. Jean Tabaka used a sailing metaphor to gather data at the Retrospective Facilitators Gathering retrospective. She asked us to identify events, interactions, etc that put wind in our sails. Then she asked us when we were in the doldrums, becalmed or held back by tides and current. We put up the "wind in the sails" stuff behind the boat, filling the sail and the doldrums stuff in front of the boat. The metaphor helped keep us out of habitual thinking and automatic categorization. And it was kind of fun. Labels: Retrospectives | |