Role clarity deficiencies can wreck agile teams

Background. One of the twelve agile principles is to build projects around motivated individuals and trust them to get the job done. Such agile teams must self-organize, but this involves conflict, making self-organization difficult. One area of difficulty is agreeing on everybody’s role. Background. What dynamics arise in a self-organizing team from the negotiation of everybody’s role? Method. We conceptualize observations from five agile teams (work observations, interviews) by Charmazian Grounded Theory Methodology. Results. We define role as something transient and implicit, not fixed and named. The roles are characterized by the responsibilities and expectations of each team member. Every team member must understand and accept their own roles (Local role clarity) and everbody else’s roles (Team-wide role clarity). Role clarity allows a team to work smoothly and effectively and to develop its members’ skills fast. Lack of role clarity creates friction that not only hampers the day-to-day work, but also appears to lead to high employee turnover. Agile coaches are critical to create and maintain role clarity. Conclusions. Agile teams should pay close attention to the levels of Local role clarity of each member and Team-wide role clarity overall, because role clarity deficits are highly detrimental. Subjects Social Computing, Software Engineering

[1]  J. Barker Tightening the Iron Cage: Concertive Control in Self-Managing Teams , 1993 .

[2]  James Noble,et al.  Developing a grounded theory to explain the practices of self-organizing Agile teams , 2012, Empirical Software Engineering.

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

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

[5]  Robert Biddle,et al.  The Social Nature of Agile Teams , 2007, Agile 2007 (AGILE 2007).

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

[7]  Richard Torkar,et al.  Group development and group maturity when building agile teams: A qualitative and quantitative investigation at eight large companies , 2017, J. Syst. Softw..

[8]  Norsaremah Salleh,et al.  An empirical study of the effects of personality in pair programming using the five-factor model , 2009, ESEM 2009.

[9]  Robert Feldt,et al.  Psychological Safety and Norm Clarity in Software Engineering Teams , 2018, 2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE).

[10]  Robert Feldt,et al.  Behavioral software engineering: A definition and systematic literature review , 2015, J. Syst. Softw..

[11]  James Noble,et al.  Self-Organizing Roles on Agile Software Development Teams , 2013, IEEE Transactions on Software Engineering.

[12]  Helena Barke,et al.  Some Reasons Why Actual Cross-Fertilization in Cross-Functional Agile Teams Is Difficult , 2018, 2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE).

[13]  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).

[14]  Robert Amor,et al.  Reflection in Agile Retrospectives , 2017, XP.

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

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

[17]  Rashina Hoda,et al.  Embedding Reflection and Learning into Agile Software Development , 2014, IEEE Software.

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

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

[20]  Claus W. Langfred The paradox of self‐management: individual and group autonomy in work groups , 2000 .

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

[22]  J. Hackman,et al.  The psychology of self-management in organizations , 1986 .

[23]  Pilar Pazos,et al.  Self-Managing Team Performance: A Systematic Review of Multilevel Input Factors , 2018 .

[24]  Pekka Abrahamsson,et al.  Building blocks for self-organizing software development teams a framework model and empirical pilot study , 2010, 2010 2nd International Conference on Software Technology and Engineering.

[25]  Jennifer A. Chatman,et al.  “WHAT’S THE NORM HERE?” SOCIAL CATEGORIZATION AS A BASIS FOR GROUP NORM DEVELOPMENT , 2003 .

[26]  D. C. Feldman,et al.  The Development and Enforcement of Group Norms , 1984 .

[27]  Fabio Q. B. da Silva,et al.  Personality in software engineering: Preliminary findings from a systematic literature review , 2011, EASE.

[28]  Fadi P. Deek,et al.  Exploring the underlying aspects of pair programming: The impact of personality , 2008, Inf. Softw. Technol..

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

[30]  Jeff Sutherland,et al.  Manifesto for Agile Software Development , 2013 .

[31]  Alexander Newman,et al.  Psychological safety: A systematic review of the literature , 2017 .