Supporting Reflection in Software Development with Everyday Working Tools

Through their day-to-day usage collaboration tools collect data on the work process. These data can be used to aid participants’ retrospective reflection on the process. The paper shows how this can be done in software development project work. Through a case study we demonstrate how retrospective reflection was conducted by use of an industry approach to project retrospectives combined with the examination of historical data in Trac, an issue tracker. The data helped the team reconstruct the project trajectory by aiding the recall of significant events, leading to a shift in the team’s perspective on the project. The success of the tool-aided retrospective reflection is attributed to its organization as well as the type of historical data examined through the tool and the tool features for navigating the data. These insights can be used to help project teams determine the potential of their tools to aid retrospective reflection.

[1]  Christian R. Prause,et al.  Managing the Iterative Requirements Process in a Multi-national Project Using an Issue Tracker , 2008, 2008 IEEE International Conference on Global Software Engineering.

[2]  Mark Keil,et al.  Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models , 2000, MIS Q..

[3]  Paul F. Dubois,et al.  Issue tracking , 2003, Comput. Sci. Eng..

[4]  D. Schoen.  The Reflective Practitioner , 1983 .

[5]  Lars Mathiassen,et al.  The post mortem paradox: a Delphi study of IT specialist perceptions , 2008, Eur. J. Inf. Syst..

[6]  Martin J. Eppler,et al.  Harvesting project knowledge: a review of project learning methods and success factors , 2003 .

[7]  Birgit R. Krogstie,et al.  Using Project Wiki History to Reflect on the Project Process , 2009, 2009 42nd Hawaii International Conference on System Sciences.

[8]  Steve Whittaker,et al.  The character, functions, and styles of instant messaging in the workplace , 2002, CSCW '02.

[9]  Rebecca E. Grinter.  Doing Software Development: Occasions for Automation and Formalisation , 1997, ECSCW.

[10]  Birgit R. Krogstie,et al.  A Model of Retrospective Reflection in Project Based Learning Utilizing Historical Data in Collaborative Tools , 2009, EC-TEL.

[11]  Kjeld Schmidt,et al.  Computer Supported Cooperative Work: New challenges to systems design , 1999 .

[12]  Kalle Lyytinen,et al.  Learning failure in information systems development , 1999, Inf. Syst. J..

[13]  SharpHelen,et al.  Collaboration and co-ordination in mature eXtreme programming teams , 2008 .

[14]  Birgit Rognebakke Krogstie.  The wiki as an integrative tool in project work , 2008, COOP.

[15]  Paul Dourish,et al.  Awareness and coordination in shared workspaces , 1992, CSCW '92.

[16]  Li-Te Cheng,et al.  Shared waypoints and social tagging to support collaboration in software development , 2006, CSCW '06.

[17]  David C. Brown,et al.  SEURAT: integrated rationale management , 2008, ICSE '08.

[18]  E. Hutchins.  Cognition in the wild , 1995 .

[19]  Monica Divitini,et al.  Shared Timeline and Individual Experience: Supporting Retrospective Reflection in Student Software Engineering Teams , 2009, 2009 22nd Conference on Software Engineering Education and Training.

[20]  Carl Gutwin,et al.  A Descriptive Framework of Workspace Awareness for Real-Time Groupware , 2002, Computer Supported Cooperative Work (CSCW).

[21]  James R. Rhyne,et al.  Communication and information retrieval with a pen-based meeting support tool , 1992, CSCW '92.

[22]  James D. Herbsleb,et al.  Pushing relevant artifact annotations in collaborative software development , 2008, CSCW.

[23]  Owen Daly-Jones,et al.  Informal workplace communication: what is it like and how might we support it? , 1994, CHI '94.

[24]  Michael D. Myers,et al.  A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems , 1999, MIS Q..

[25]  Helen Sharp,et al.  Collaboration and co-ordination in mature eXtreme programming teams , 2008, Int. J. Hum. Comput. Stud..

[26]  Robert E. Kraut,et al.  Coordination in software development , 1995, CACM.

[27]  Esther Derby,et al.  Agile Retrospectives: Making Good Teams Great , 2006 .

[28]  Birgit R. Krogstie.  Using Project Wiki History to Reflect on the Project Process , 2009 .

[29]  James D. Kiper,et al.  Capturing Decisions and Rationale from Collaborative Design , 2008 .

[30]  Gina Venolia,et al.  The secret life of bugs: Going past the errors and omissions in software repositories , 2009, 2009 IEEE 31st International Conference on Software Engineering.

[31]  Joan Manuel Marquès,et al.  Distributed Cognition in the Context of Virtual Collaborative Learning , 2002 .

[32]  Susan Leigh Star,et al.  The Structure of Ill-Structured Solutions: Boundary Objects and Heterogeneous Distributed Problem Solving , 1989, Distributed Artificial Intelligence.

[33]  Victor R. Basili,et al.  Improve Software Quality by Reusing Knowledge and Experience , 1995 .

[34]  Christine Halverson,et al.  Organizational Memory as Objects, Processes, and Trajectories: An Examination of Organizational Memory in Use , 2004, Computer Supported Cooperative Work (CSCW).

[35]  Geraldine Fitzpatrick,et al.  CVS integration with notification and chat: lightweight software team collaboration , 2006, CSCW '06.

[36]  Sara A. Bly,et al.  It's all in the words: supporting work activites with lightweight tools , 1999, GROUP '99.

[37]  Carl Gutwin,et al.  Group awareness in distributed software development , 2004, CSCW.

[38]  Carla Simone,et al.  Coordination mechanisms: Towards a conceptual foundation of CSCW systems design , 1996, Computer Supported Cooperative Work (CSCW).

[39]  William G. Poole.  The softer side of custom software development: working with the other players , 2003, Proceedings 16th Conference on Software Engineering Education and Training, 2003. (CSEE&T 2003)..

[40]  Alf Inge Wang,et al.  Improving the effectiveness of root cause analysis in post mortem analysis: A controlled experiment , 2009, Inf. Softw. Technol..

[41]  Audris Mockus,et al.  Distance, dependencies, and delay in a global collaboration , 2000, CSCW '00.

[42]  Jonathan Grudin,et al.  Messaging And Formality: Will IM Follow in the Footsteps of Email? , 2003, INTERACT.

[43]  James D. Herbsleb,et al.  What is chat doing in the workplace? , 2002, CSCW '02.

[44]  Susanne Bødker,et al.  Computer Support for Social Awareness in Flexible Work , 2006, Computer Supported Cooperative Work (CSCW).

[45]  Tore Dybå,et al.  Empirical studies of agile software development: A systematic review , 2008, Inf. Softw. Technol..

[46]  Norman L. Kerth,et al.  Project Retrospectives: A Handbook for Team Reviews , 2001 .

[47]  Janice Singer,et al.  Learning from project history: a case study for software development , 2004, CSCW.

[48]  Yvonne Rogers,et al.  Distributed cognition: an alternative framework for analysing and explaining collaborative working , 1994, J. Inf. Technol..