Some Reasons Why Actual Cross-Fertilization in Cross-Functional Agile Teams Is Difficult

Background: Agile teams are supposed to be cross-functional in order to be complete (so they can work without external help). Cross-functionality is also supposed to produce cross-fertilization: Better ideas and solutions, problems prevented or detected earlier, etc. Question: What is motivating or demotivating team members to work in a cross-functional manner? Method: We conceptualize observations from five agile teams (work observations, interviews, group discussion) and from interviews with five agile consultants/ coaches by applying Grounded Theory Methodology. Results: The inclination to interact cross functionally is moderated by at least six factors such as perceived inefficiency, a sense of responsibility for one's own functional domain, or the difficulty to find a level of detail that is suitable for the collaboration. Conclusion: Cross-fertilization is harder to get than one might expect and teams need to develop good judgment to succeed at it.

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

[2]  A. Strauss,et al.  Grounded theory , 2017 .

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

[4]  H Gaze Balancing acts. , 1992, Nursing times.

[5]  S. Hart New Product Development , 1995 .

[6]  Avan R. Jassawalla,et al.  Building collaborative cross-functional new product teams , 1999 .

[7]  Jorge F. S. Gomes,et al.  Critical success factors for cross‐functional teamwork in new product development , 2000 .

[8]  E. McDonough Investigation of Factors Contributing to the Success of Cross-Functional Teams , 2000 .

[9]  Debra L. Shapiro,et al.  Maximizing cross-functional new product teams' innovativeness and constraint adherence: A conflict communications perspective. , 2001 .

[10]  Cynthia F. Kurtz,et al.  The new dynamics of strategy: sense-making in a complex and complicated world , 2003, IEEE Engineering Management Review.

[11]  Kent Beck,et al.  Extreme Programming Explained: Embrace Change (2nd Edition) , 2004 .

[12]  C. D. De Dreu,et al.  Work group diversity and group performance: an integrative model and research agenda. , 2004, The Journal of applied psychology.

[13]  Tore Dybå,et al.  Understanding Self-Organizing Teams in Agile Software Development , 2008, 19th Australian Conference on Software Engineering (aswec 2008).

[14]  Subin Im,et al.  Spurring Cross‐Functional Integration for Higher New Product Performance: A Group Effectiveness Perspective* , 2010 .

[15]  James Noble,et al.  Balancing acts: walking the Agile tightrope , 2010, CHASE '10.

[16]  Rashina Hoda,et al.  Self-Organizing Agile Teams: A Grounded Theory , 2011 .

[17]  M. G. Lauby,et al.  A balancing act , 2011, Nature Immunology.

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

[19]  Abdul Azim Abdul Ghani,et al.  How grounded can facilitate research studies in context of agile software development. , 2013 .

[20]  Omar Bahy Badreddin Thematic Review and Analysis of Grounded Theory Application in Software Engineering , 2013, Adv. Softw. Eng..

[21]  R. Stock,et al.  A Closer Look at Cross-functional R&D Cooperation for Innovativeness: Innovation-oriented Leadership and Human Resource Practices as Driving Forces , 2014 .

[22]  K. Charmaz,et al.  Constructing Grounded Theory , 2014 .

[23]  Floortje Blindenbach-Driessen,et al.  The (In)Effectiveness of Cross-Functional Innovation Teams: The Moderating Role of Organizational Context , 2015, IEEE Transactions on Engineering Management.

[24]  Paul Ralph,et al.  Grounded Theory in Software Engineering Research: A Critical Review and Guidelines , 2016, 2016 IEEE/ACM 38th International Conference on Software Engineering (ICSE).

[25]  John Grundy,et al.  Systematic literature reviews in agile software development: A tertiary study , 2017, Inf. Softw. Technol..

[26]  Andrew Begel,et al.  Cross-Disciplinary Perspectives on Collaborations with Software Engineers , 2017, 2017 IEEE/ACM 10th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE).