Self-Organizing Agile Teams: A Grounded Theory

Self-organizing teams are a hallmark of Agile software development, directly affecting team effectiveness and project success. Agile software development, and in particular the Scrum method, emphasizes self-organizing teams but does not provide clear guidelines on how teams should become and remain self-organizing. Based on Grounded Theory research involving 58 Agile practitioners from 23 different software organizations in New Zealand and India, this thesis presents a grounded theory of self-organizing Agile teams. The theory of self-organizing Agile teams explains how software development teams take on informal, implicit, transient, and spontaneous roles and perform balanced practices while facing critical environmental factors, in order to become self-organizing. The roles are: Mentor, Co-ordinator, Translator, Champion, Promoter, and Terminator. The practices involve balancing freedom and responsibility, cross-functionality and specialization, and continuous learning and iteration pressure. The factors are senior management support and level of customer involvement. This thesis will help teams and their coaches better understand their roles and responsibilities as a self-organizing Agile team. This thesis will also serve to educate senior management and customers about the importance of supporting these teams.

[1]  Anthony F. Norcio,et al.  Exploring language in software process elicitation: A grounded theory approach , 2009, 2009 3rd International Symposium on Empirical Software Engineering and Measurement.

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

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

[4]  W. Duncan A GUIDE TO THE PROJECT MANAGEMENT BODY OF KNOWLEDGE , 1996 .

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

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

[7]  Stewart Marshall,et al.  Don’t mention the ‘A’ word: Agile undercover , 2009 .

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

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

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

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

[12]  W. Chua Radical Developments in Accounting Thought , 1986 .

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

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

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

[16]  Raul Sidnei Wazlawick,et al.  The influence of organizational culture on the adoption of extreme programming , 2008, J. Syst. Softw..

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

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

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

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

[21]  Nayan B. Ruparelia,et al.  Software development lifecycle models , 2010, SOEN.

[22]  Janice Singer,et al.  Guide to Advanced Empirical Software Engineering , 2007 .

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

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

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

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

[27]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

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

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

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

[31]  Wanda J. Orlikowski,et al.  Studying Information Technology in Organizations: Research Approaches and Assumptions , 1991, Inf. Syst. Res..

[32]  Diane E. Strode,et al.  The Impact of Organizational Culture on Agile Method Use , 2009, 2009 42nd Hawaii International Conference on System Sciences.

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

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

[35]  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.

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

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

[38]  Tore Dybå,et al.  The Future of Empirical Methods in Software Engineering Research , 2007, Future of Software Engineering (FOSE '07).

[39]  Daniela E. Damian,et al.  Selecting Empirical Methods for Software Engineering Research , 2008, Guide to Advanced Empirical Software Engineering.

[40]  Angela Martin The Role of Customers in Extreme Programming Projects , 2009 .

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

[42]  Ali Mohsenzadeh,et al.  The impact of agile methods on software project management , 2005, 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'05).

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

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

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

[46]  SharpHelen,et al.  Collaboration and co-ordination in mature eXtreme programming teams , 2008 .

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

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

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

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

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

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

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

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

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

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

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

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

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

[60]  Esther Derby,et al.  Agile Retrospectives: Making Good Teams Great , 2006 .

[61]  Barry W. Boehm,et al.  Get Ready for Agile Methods, with Care , 2002, Computer.

[62]  B. Tuckman DEVELOPMENTAL SEQUENCE IN SMALL GROUPS. , 1965, Psychological bulletin.

[63]  Tore Dybå,et al.  Understanding Self-Organizing Teams in Agile Software Development , 2008 .

[64]  Jeffrey C. Carver The Impact of Background and Experience on Software Inspections , 2004, Empirical Software Engineering.

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

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

[67]  G. Thomas,et al.  Reinventing grounded theory: some questions about theory, ground and discovery , 2006 .

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

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

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

[71]  Craig Larman,et al.  Agile and Iterative Development: A Manager's Guide , 2003 .

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

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

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

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

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

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

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

[79]  James Noble,et al.  Using grounded theory to study the human aspects of software engineering , 2010, HAoSE '10.

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

[81]  Liisa von Hellens,et al.  Qualitative Research in Information Systems , 2007, Australas. J. Inf. Syst..

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

[83]  Susan M. Merritt,et al.  One XP experience: introducing agile (XP) software development into a culture that is willing but not ready , 2004, CASCON.

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

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

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

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

[88]  JaatunMartin Gilje,et al.  Agile Software Development , 2002, Comput. Sci. Educ..

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

[90]  James Noble,et al.  How much is just enough?: some documentation patterns on Agile projects , 2010, EuroPLoP.

[91]  Barry Boehm,et al.  A view of 20th and 21st century software engineering , 2006, ICSE.

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

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

[94]  Emma Parnell-Klabo Introducing lean principles with agile practices at a Fortune 500 company , 2006, AGILE 2006 (AGILE'06).

[95]  J. Morse Critical Issues in Qualitative Research Methods , 1993 .

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

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

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

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

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

[101]  James Noble,et al.  Negotiating Contracts for Agile Projects: A Practical Perspective , 2009, XP.

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

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

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

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

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

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

[108]  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..

[109]  Michele Sliger,et al.  The Software Project Manager's Bridge to Agility , 2008 .

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

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

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

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

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

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

[116]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

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

[118]  Gerard Meszaros,et al.  Cowboys and Indians: Impacts of Cultural Diversity on Agile Teams , 2008, Agile 2008 Conference.

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

[120]  R. Suddaby From the Editors: What Grounded Theory is Not , 2006 .

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

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

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

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

[125]  Bertrand Meyer,et al.  The Spiral Model , 2008 .

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

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

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

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

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

[131]  B. J. Oates,et al.  Researching Information Systems and Computing , 2005 .

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

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

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

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

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