The impact of inadequate customer collaboration on self-organizing Agile teams

ContextCustomer collaboration is a vital feature of Agile software development. ObjectiveThis article addresses the importance of adequate customer involvement on Agile projects, and the impact of different levels of customer involvement on real-life Agile projects. MethodWe conducted a Grounded Theory study involving 30 Agile practitioners from 16 software development organizations in New Zealand and India, over a period of 3 years. ResultsWe discovered that Lack of Customer Involvement was one of the biggest challenges faced by Agile teams. Customers were not as involved on these Agile projects as Agile methods demand. We describe the causes of inadequate customer collaboration, its adverse consequences on self-organizing Agile teams, and Agile Undercover - a set of strategies used by the teams to practice Agile despite insufficient or ineffective customer involvement. ConclusionCustomer involvement is important on Agile projects. Inadequate customer involvement causes adverse problems for Agile teams. The Agile Undercover strategies we've identified can assist Agile teams facing similar lack of customer involvement.

[1]  Judith A. Holton,et al.  Remodeling Grounded Theory , 2004 .

[2]  Barry W. Boehm,et al.  Rebalancing Your Organization's Agility and Discipline , 2003, XP/Agile Universe.

[3]  B. Glaser Basics of Grounded Theory Analysis: Emergence Vs. Forcing , 1992 .

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

[5]  James Noble,et al.  The XP Customer Team: A Grounded Theory , 2009, 2009 Agile Conference.

[6]  Steve R. Palmer,et al.  A Practical Guide to Feature-Driven Development , 2002 .

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

[8]  George Mangalaraj,et al.  Acceptance of software process innovations – the case of extreme programming , 2009, Eur. J. Inf. Syst..

[9]  Frank Maurer,et al.  A case study on the impact of scrum on overtime and customer satisfaction , 2005, Agile Development Conference (ADC'05).

[10]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

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

[12]  Jutta Eckstein,et al.  Xtreme programming and agile coaching , 2003, OOPSLA '03.

[13]  Sanjiv Augustine,et al.  Agile project management: steering from the edges , 2005, CACM.

[14]  Marcus Evans,et al.  Scaling Product Ownership , 2007, Agile 2007 (AGILE 2007).

[15]  Robert Biddle,et al.  The role of the customer in software development: the XP customer - fad or fashion? , 2004, OOPSLA '04.

[16]  George Allan,et al.  A critique of using grounded theory as a research method , 2003 .

[17]  Kieran Conboy,et al.  Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development , 2009, Inf. Syst. Res..

[18]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[19]  Frank Maurer,et al.  Knowledge Sharing in Agile Software Teams , 2004, Logic versus Approximation.

[20]  K. Parry Grounded theory and social process: A new direction for leadership research , 1998 .

[21]  Claes Wohlin,et al.  Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering , 2006 .

[22]  W. R. Howard Agile Project Management: Creating Innovative Products , 2010 .

[23]  Geir Kjetil Hanssen,et al.  Agile customer engagement: a longitudinal qualitative case study , 2006, ISESE '06.

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

[25]  Dewayne E. Perry,et al.  Customer relationships and Extreme Programming , 2005, ACM SIGSOFT Softw. Eng. Notes.

[26]  Robert C. Martin Agile Software Development, Principles, Patterns, and Practices , 2002 .

[27]  Lan Cao,et al.  A framework for adapting agile development methodologies , 2009, Eur. J. Inf. Syst..

[28]  Alistair Cockburn,et al.  People and Methodologies in Software Development , 2003 .

[29]  Bg Glaser,et al.  The grounded theory perspective Theoretical coding. , 2005 .

[30]  James Noble,et al.  Organizing self-organizing teams , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[31]  B. Glaser Theoretical Sensitivity: Advances in the Methodology of Grounded Theory , 1978 .

[32]  A. Cockburn,et al.  Agile Software Development: The People Factor , 2001, Computer.

[33]  Jeff Sutherland,et al.  The Scrum Guide , 2012 .

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

[35]  Ken Parry,et al.  Identifying paradox: A grounded theory of leadership in overcoming resistance to change , 2004 .

[36]  James Noble,et al.  XP Customer Practices: A Grounded Theory , 2009, 2009 Agile Conference.

[37]  Ken H. Judy,et al.  Great Scrums Need Great Product Owners: Unbounded Collaboration  and Collective Product Ownership , 2008, Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008).

[38]  Kent L. Beck,et al.  Agile management - an oxymoron?: who needs managers anyway? , 2003, OOPSLA '03.

[39]  A. Strauss,et al.  Basics of qualitative research: Grounded theory procedures and techniques. , 1993 .

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

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

[42]  Philippe Kruchten,et al.  A methodological leg to stand on: lessons learned using grounded theory to study software development , 2008, CASCON '08.

[43]  Rory V. O'Connor,et al.  Using grounded theory to understand software process improvement: A study of Irish software product companies , 2007, Inf. Softw. Technol..

[44]  Vinod Kumar,et al.  Identifying some important success factors in adopting agile software development practices , 2009, J. Syst. Softw..

[45]  S. Georgieva,et al.  Best Practices in Project Management Through a Grounded Theory Lens , 2008 .

[46]  James Noble,et al.  Agile Undercover: When Customers Don't Collaborate , 2010, XP.

[47]  Victor R. Basili,et al.  Iterative and incremental developments. a brief history , 2003, Computer.

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

[49]  Pekka Abrahamsson,et al.  A case study on the impact of customer communication on defects in agile software development , 2006, AGILE 2006 (AGILE'06).

[50]  James A. Highsmith,et al.  Adaptive Software Development: A Collaborative Approach to Managing Complex Systems , 1999 .