Integrating agile software development and software process improvement: a longitudinal case study

Agile software development solutions are targeted at enhancing work at project level. Little is yet known about the relationship between agile projects and organizational capability improvement. The agile project teams are suggested to iteratively improve their behaviour in a validated manner. This paper addresses the high value of such validated software process improvement (SPI) knowledge emerging from project teams and its utilization at the organizational level SPI. In this paper it is suggested that the novel SPI methods of agile project teams also require alterations in the activities of the organizational level in order to enable the mutually benefiting coexistence of the two. Empirical results from a longitudinal case study over Jive software development projects are presented to illustrate the evolvement of organizational SPI mechanisms and to derive implications for integrating the agile software development and organizational SPI. This study reveals the high importance of close collaboration between the organizational and project levels throughout the projects and identifies several organizational activities needed in enhancing SPI within agile projects and in an organization.

[1]  Victor R. Basili,et al.  Software development: a paradigm for the future , 1989, [1989] Proceedings of the Thirteenth Annual International Computer Software & Applications Conference.

[2]  R Gourlay,et al.  Learning in action. , 1986, The Health service journal.

[3]  M. J. Earl,et al.  Knowledge as strategy: reflections on Skandia International and Shorko Films , 1994 .

[4]  J. Cunningham,et al.  Case study principles for different types of cases , 1997 .

[5]  Outi Salo.  Systematical Validation of Learning in Agile Software Development Environment , 2005, Wissensmanagement.

[6]  Torgeir Dingsøyr,et al.  Extending Agile Methods: Postmortem Reviews as Extended Feedback , 2002, LSO.

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

[8]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[9]  Alistair Cockburn,et al.  Crystal Clear: A Human-Powered Methodology for Small Teams , 2004 .

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

[11]  Pekka Abrahamsson,et al.  Self-Adaptability of Agile Software Processes: A Case Study on Post-iteration Workshops , 2004, XP.

[12]  Pekka Abrahamsson,et al.  Mobile-D: an agile approach for mobile application development , 2004, OOPSLA '04.

[13]  H. D. Rombach,et al.  The Goal Question Metric Approach , 1994 .

[14]  Outi Salo,et al.  Deploying Agile Practices in Organizations: A Case Study , 2005, EuroSPI.

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

[16]  Francis Y. Lau,et al.  Toward a framework for action research in information systems studies , 1999, Inf. Technol. People.

[17]  Outi Salo,et al.  Improving software process in agile software development projects: results from two XP case studies , 2004, Proceedings. 30th Euromicro Conference, 2004..

[18]  Alan Mumford,et al.  Learning in action , 1995 .

[19]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.

[20]  Pekka Abrahamsson,et al.  Empirical Evaluation of Agile Software Development: The Controlled Case Study Approach , 2004, PROFES.

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

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

[23]  J. Vandeville.  Organizational Learning Through the Collection of "Lessons Learned" , 2000, Informing Sci. Int. J. an Emerg. Transdiscipl..