Self-Organizing Roles on Agile Software Development Teams

Self-organizing teams have been recognized and studied in various forms-as autonomous groups in socio-technical systems, enablers of organizational theories, agents of knowledge management, and as examples of complex-adaptive systems. Over the last decade, self-organizing teams have taken center stage in software engineering when they were incorporated as a hallmark of Agile methods. Despite the long and rich history of self-organizing teams and their recent popularity with Agile methods, there has been little research on the topic within software wngineering. Particularly, there is a dearth of research on how Agile teams organize themselves in practice. Through a Grounded Theory research involving 58 Agile practitioners from 23 software organizations in New Zealand and India over a period of four years, we identified informal, implicit, transient, and spontaneous roles that make Agile teams self-organizing. These roles-Mentor, Coordinator, Translator, Champion, Promoter, and Terminator-are focused toward providing initial guidance and encouraging continued adherence to Agile methods, effectively managing customer expectations and coordinating customer collaboration, securing and sustaining senior management support, and identifying and removing team members threatening the self-organizing ability of the team. Understanding these roles will help software development teams and their managers better comprehend and execute their roles and responsibilities as a self-organizing team.

[1]  Pekka Abrahamsson,et al.  New directions on agile methods: a comparative analysis , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[2]  James Noble,et al.  The impact of inadequate customer collaboration on self-organizing Agile teams , 2011, Inf. Softw. Technol..

[3]  E. Molleman,et al.  Empowerment and team development , 1998 .

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

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

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

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

[8]  D. Perry,et al.  Customer Relationships and Extreme Programming , 2005 .

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

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

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

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

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

[14]  Alvita K. Nathaniel,et al.  A grounded theory of moral reckoning in nursing , 2004 .

[15]  J. Benoliel Grounded Theory and Nursing Knowledge , 1996 .

[16]  Linda Rising,et al.  The Scrum Software Development Process for Small Teams , 2000, IEEE Softw..

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

[18]  R. Mcintyre,et al.  A Conceptual Framework for Teamwork Measurement , 1997 .

[19]  John W. Creswell,et al.  Research Design: Qualitative, Quantitative, and Mixed Methods Approaches , 2010 .

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

[21]  Ralph Lewis,et al.  From Chaos to Complexity , 1994 .

[22]  Helen Sharp,et al.  An Ethnographic Study of XP Practice , 2004, Empirical Software Engineering.

[23]  Edward Uy,et al.  Growing and Sustaining an Offshore Scrum Engagement , 2008, Agile 2008 Conference.

[24]  C. Anderson,et al.  Of Ants and Men: Self-Organized Teams in Human and Insect Organizations , 2003 .

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

[26]  Stuart A. Kauffman,et al.  ORIGINS OF ORDER , 2019, Origins of Order.

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

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

[29]  Deborah G. Ancona,et al.  Beyond Task and Maintenance: Defining External Functions in Groups , 2008 .

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

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

[32]  J. Alexander,et al.  Images of Organization , 1988 .

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

[34]  Laurie A. Williams,et al.  Strengthening the Case for Pair Programming , 2000, IEEE Softw..

[35]  I. Nonaka A Dynamic Theory of Organizational Knowledge Creation , 1994 .

[36]  James E. Tomayko,et al.  Human aspects of software engineering , 2004 .

[37]  Helen Sharp,et al.  Organisational culture and XP: three case studies , 2005, Agile Development Conference (ADC'05).

[38]  Rachel K. E. Bellamy,et al.  Moving into a new software project landscape , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

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

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

[41]  Orit Hazzan,et al.  The Agile Manifesto , 2014 .

[42]  Michael R. Harwell,et al.  Research design: Qualitative, quantitative, and mixed methods: Pursuing ideas as the keystone of exemplary inquir , 2011 .

[43]  Lavanya R. Abraham Cultural differences in software engineering , 2009, ISEC '09.

[44]  Des Greer,et al.  Do agile GSD experience reports help the practitioner? , 2006, GSD '06.

[45]  S. Levin Ecosystems and the Biosphere as Complex Adaptive Systems , 1998, Ecosystems.

[46]  Sanjiv Augustine,et al.  Managing Agile Projects , 2005 .

[47]  Kalpana Sureshchandra,et al.  Adopting Agile in Distributed Development , 2008, 2008 IEEE International Conference on Global Software Engineering.

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

[49]  K. Charmaz,et al.  Constructing Grounded Theory: A practical guide through qualitative analysis Kathy Charmaz Constructing Grounded Theory: A practical guide through qualitative analysis Sage 224 £19.99 0761973532 0761973532 [Formula: see text]. , 2006, Nurse researcher.

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

[51]  R. Meredith Belbin,et al.  Team Roles at Work , 2022 .

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

[53]  James Noble,et al.  The XP customer role in practice: three studies , 2004, Agile Development Conference.

[54]  Ioannis Stamelos,et al.  Investigating the extreme programming system–An empirical study , 2006, Empirical Software Engineering.

[55]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

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

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

[58]  Barry W. Boehm,et al.  Empirical Findings in Agile Methods , 2002, XP/Agile Universe.

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

[60]  James Noble,et al.  Supporting Self-organizing Agile Teams - What's Senior Management Got to Do with It? , 2011, XP.

[61]  Jeff Sutherland,et al.  Fully Distributed Scrum: The Secret Sauce for Hyperproductive Offshored Development Teams , 2008, Agile 2008 Conference.

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

[63]  Viktor Mikhaĭlovich Glushkov,et al.  An Introduction to Cybernetics , 1957, The Mathematical Gazette.

[64]  B. Glaser Doing grounded theory : issues and discussions , 1998 .

[65]  Daniel Robey,et al.  Traditional, iterative, and component-based development: A social analysis of software development paradigms , 2001, Inf. Technol. Manag..

[66]  B. Glaser Naturalist Inquiry and Grounded Theory , 2004 .

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

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

[69]  Donald C. Wells Extreme Programming: A gentle introduction , 2003 .

[70]  Kurt Lewin,et al.  Resolving social conflicts : selected papers on group dynamics , 1948 .

[71]  Venugopal Balijepally,et al.  Theoretical reflections on agile development methodologies , 2007, Commun. ACM.

[72]  Laurie A. Williams,et al.  All I really need to know about pair programming I learned in kindergarten , 2000, Commun. ACM.

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

[74]  Torgeir Dingsøyr,et al.  Scrum and Team Effectiveness: Theory and Practice , 2008, XP.

[75]  Tore Dybå,et al.  A teamwork model for understanding an agile team: A case study of a Scrum project , 2010, Inf. Softw. Technol..

[76]  Steve Sawyer,et al.  Social interactions of information systems development teams: a performance perspective , 2010, Inf. Syst. J..

[77]  E. Trist The Evolution of Socio-Technical Systems: A Conceptual Framework and an Action Research Program , 1981 .

[78]  A. Strauss,et al.  The Discovery of Grounded Theory , 1967 .

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

[80]  Amr Elssamadisy,et al.  Agile Adoption Patterns: A Roadmap to Organizational Success , 2008 .

[81]  Eric Molleman,et al.  VARIETY AND THE REQUISITE OF SELF‐ORGANIZATION , 1998 .

[82]  Andrew Begel,et al.  Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[83]  N. Elliott,et al.  How to recognise a 'quality' grounded theory research study. , 2005, The Australian journal of advanced nursing : a quarterly publication of the Royal Australian Nursing Federation.

[84]  Andraž Cej,et al.  Agile software development with Scrum , 2010 .

[85]  R. Lewin,et al.  Complexity: Life at the Edge of Chaos , 1992 .

[86]  Jason Brownlee,et al.  Complex adaptive systems , 2007 .

[87]  Helen Sharp,et al.  The Social Side of Technical Practices , 2005, XP.

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

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

[90]  Mark Summers Insights into an Agile Adventure with Offshore Partners , 2008, Agile 2008 Conference.

[91]  James Noble,et al.  What Language Does Agile Speak? , 2010, XP.

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

[93]  James E. Tomakyo,et al.  Human Aspects of Software Engineering , 2005 .

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

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

[96]  Michel R. V. Chaudron,et al.  A Survey of the Practice of Design -- Code Correspondence amongst Professional Software Engineers , 2007, ESEM 2007.