Evidence-Based Timelines for Agile Project Retrospectives - A Method Proposal

Retrospective analysis of agile projects can support identification of issues through team reflection and may enable learning and process improvements. Basing retrospectives primarily on experiences poses a risk of memory bias as people may remember events differently, which can lead to incorrect conclusions. This bias is enhanced in project retrospectives which cover a longer period compared to iteration retrospectives. To support teams in recalling accurate and joint views of projects, we propose using an evidence-based timeline with historical data as input to project retrospectives. The proposed method was developed together with a large software development company in the telecommunications domain. This paper outlines a method for visualizing an evidence-based project timeline by illustrating aspects such as business priority, iterations and test activities. Our method complements an experience-based approach by providing objective data as a starting point for reflection and aims to support objective analysis of issues and root causes.

[1]  G. Shaw.  The Importance of NOT Learning from Experience , 2000 .

[2]  Per Runeson,et al.  Combining agile methods with stage-gate project management , 2005, IEEE Software.

[3]  Robert L. Glass.  Predicting future maintenance cost, and how we're doing it wrong , 2002, IEEE Software.

[4]  L. Baird,et al.  Learning from action: Imbedding more learning into the performance fast enough to make a difference , 1999 .

[5]  Robert L. Glass,et al.  Project retrospectives, and why they never happen , 2002, IEEE Software.

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

[7]  André van der Hoek,et al.  A Visualization for Software Project Awareness and Evolution , 2007, 2007 4th IEEE International Workshop on Visualizing Software for Understanding and Analysis.

[8]  Kevin C. Desouza,et al.  Experiences with conducting project postmortems: reports versus stories , 2005, Softw. Process. Improv. Pract..

[9]  Michael Maham.  Planning and Facilitating Release Retrospectives , 2008, Agile 2008 Conference.

[10]  Wayne Turner.  Engineering: Education and Training , 2011 .

[11]  Tom DeMarco,et al.  A defined process for project post mortem review , 1996, IEEE Software.

[12]  Andy J. Nolan,et al.  Learning from Success , 1999, IEEE Softw..

[13]  Christoph Treude,et al.  ConcernLines: A timeline view of co-occurring concerns , 2009, 2009 IEEE 31st International Conference on Software Engineering.

[14]  M. Zedtwitz.  Organizational Learning through Post-project Reviews in R&D , 2002 .

[15]  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.

[16]  Gerhard Schewe.  Integrating Innovation and Technology Management , 1991 .

[17]  H. Sertic,et al.  A Project Retrospectives Method in Telecom Software Development , 2007, 2007 9th International Conference on Telecommunications.

[18]  Martin Boldt,et al.  Computer forensic timeline visualization tool , 2009 .

[19]  Kieran Conboy,et al.  Decision Making in Agile Development: A Focus Group Study of Decisions and Obstacles , 2011, 2011 AGILE Conference.

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

[21]  DeMarcoTom,et al.  A Defined Process For Project Postmortem Review , 1996 .

[22]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[23]  Claes Wohlin,et al.  A Framework for Technology Introduction in Software Organizations 1 , 1996 .

[24]  Pekka Abrahamsson,et al.  The impact of agile practices on communication in software development , 2008, Empirical Software Engineering.