Perspectives on Productivity and Delays in Large-Scale Agile Projects

Many large and distributed companies run agile projects in development environments that are inconsistent with the original agile ideas. Problems that result from these inconsistencies can affect the productivity of development projects and the timeliness of releases. To be effective in such contexts, the agile ideas need to be adapted. We take an inductive approach for reaching this aim by basing the design of the development process on observations of how context, practices, challenges, and impacts interact. This paper reports the results of an interview study of five agile development projects in an environment that was unfavorable for agile principles. Grounded theory was used to identify the challenges of these projects and how these challenges affected productivity and delays according to the involved project roles. Productivity and delay-influencing factors were discovered that related to requirements creation and use, collaboration, knowledge management, and the application domain. The practitioners’ explanations about the factors’ impacts are, on one hand, a rich empirical source for avoiding and mitigating productivity and delay problems and, on the other hand, a good starting point for further research on flexible large-scale development.

[1]  RegnellBjörn,et al.  Requirements engineering challenges in market-driven software development - An interview study with practitioners , 2007 .

[2]  Lionel C. Briand,et al.  AINSI: an inductive method for software process improvement: concrete steps and guidelines , 1995 .

[3]  G. Lynn,et al.  Marketing and Discontinuous Innovation: The Probe and Learn Process , 1996 .

[4]  Tony Gorschek,et al.  A practitioner's guide to light weight software process assessment and improvement planning , 2008, J. Syst. Softw..

[5]  Rosanna Garcia,et al.  A critical look at technological innovation typology and innovativeness terminology: a literature review , 2002 .

[6]  Nazim H. Madhavji,et al.  The Impact of Tools on Software Productivity , 1996, IEEE Softw..

[7]  J. Herbsleb,et al.  Global software development , 2001 .

[8]  Fabio Q. B. da Silva,et al.  SCRUM and Productivity in Software Projects: A Systematic Literature Review , 2010, EASE.

[9]  Samuel Fricker,et al.  Release Planning with Feature Trees: Industrial Case , 2012, REFSQ.

[10]  Aldo Dagnino,et al.  Agile Software Development in Large Organizations , 2004, Computer.

[11]  Philippe Kruchten,et al.  Scaling down large projects to meet the agile “sweet spot” , 2003 .

[12]  Hakan Erdogmus,et al.  Scaling Agile Methods , 2003, IEEE Softw..

[13]  Claes Wohlin,et al.  Measuring the flow in lean software development , 2011, Softw. Pract. Exp..

[14]  Dean Leffingwell,et al.  Scaling Software Agility: Best Practices for Large Enterprises (The Agile Software Development Series) , 2007 .

[15]  Tsun Chow,et al.  A survey study of critical success factors in agile software projects , 2008, J. Syst. Softw..

[16]  Jeff Sutherland,et al.  Fully Distributed Scrum: Linear Scalability of Production between San Francisco and India , 2009, 2009 Agile Conference.

[17]  Barry W. Boehm,et al.  Management challenges to implementing agile processes in traditional development organizations , 2005, IEEE Software.

[18]  Oliver Günther,et al.  RFID and the Perception of Control: The Consumer's View , 2005, IEEE Engineering Management Review.

[19]  Björn Regnell,et al.  Requirements engineering challenges in market-driven software development - An interview study with practitioners , 2007, Inf. Softw. Technol..

[20]  Rachel Jane McCrindle,et al.  An investigation into the effects of code coupling on team dynamics and productivity , 2002, Proceedings 26th Annual International Computer Software and Applications.

[21]  Colin Robson,et al.  Real World Research: A Resource for Social Scientists and Practitioner-Researchers , 1993 .

[22]  Khaled El Emam,et al.  Elements of Software Process Assessment & Improvement , 1999 .

[23]  Peng Xu,et al.  Can distributed software development be agile? , 2006, CACM.

[24]  Philippe Kruchten,et al.  Agility in context , 2010, OOPSLA.

[25]  Jeff Sutherland,et al.  Distributed Scrum: Agile Project Management with Outsourced Development Teams , 2007, 2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07).

[26]  Mike Cohn,et al.  Introducing an Agile Process to an Organization , 2003, Computer.

[27]  George Mangalaraj,et al.  Challenges of migrating to agile methodologies , 2005, CACM.

[28]  Michiel van Genuchten,et al.  Why is Software Late? An Empirical Study of Reasons For Delay in Software Development , 1991, IEEE Trans. Software Eng..

[29]  N. Hoffart Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory , 2000 .

[30]  Gary D. Scudder,et al.  Improving Speed and Productivity of Software Development: A Global Survey of Software Developers , 1996, IEEE Trans. Software Eng..

[31]  Tony Gorschek,et al.  Handshaking with Implementation Proposals: Negotiating Requirements Understanding , 2010, IEEE Software.

[32]  CohnMike,et al.  Introducing an Agile Process to an Organization , 2003 .

[33]  Victor R. Basili,et al.  How reuse influences productivity in object-oriented systems , 1996, CACM.

[34]  D. Garvin Building a learning organization. , 1993, Harvard business review.