Supporting Self-organizing Agile Teams - What's Senior Management Got to Do with It?

Self-organizing Agile teams need a supportive environment to emerge and flourish. Through a Grounded Theory study of 58 Agile practitioners across 23 different software organizations in New Zealand and India, we found that senior management support is a critical environmental factor influencing self- organizing Agile teams. We describe the influence of senior management, and show how their support can create and sustain a supportive environment for self- organizing Agile teams.

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

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

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

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

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

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

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

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

[9]  Alberto Sillitti.  Agile Processes in Software Engineering and Extreme Programming, 11th International Conference, XP 2010, Trondheim, Norway, June 1-4, 2010. Proceedings , 2010, XP.

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

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

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

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

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

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

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

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

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

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

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

[21]  Shawn A. Bohner,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).

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

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

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

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

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

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

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

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

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

[31]  E. Schein.  Organizational Culture and Leadership , 1991 .

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

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

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

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

[36]  H. Tohidi,et al.  Organizational culture and leadership , 2012 .

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

[38]  Wolfgang Lenski,et al.  Logic versus Approximation , 2004, Lecture Notes in Computer Science.

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

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

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

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

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

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

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

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

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