The Community for Technology Leaders
RSS Icon
Issue No.03 - March (2013 vol.39)
pp: 422-444
Rashina Hoda , The University of Auckland, Auckland
James Noble , Victoria University of Wellington, Wellington
Stuart Marshall , Victoria University of Wellington, Wellington
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.
Programming, Organizations, Collaboration, Software, Organizing, Software engineering, grounded theory, Self-organizing, team roles, software engineering, Agile software development
Rashina Hoda, James Noble, Stuart Marshall, "Self-Organizing Roles on Agile Software Development Teams", IEEE Transactions on Software Engineering, vol.39, no. 3, pp. 422-444, March 2013, doi:10.1109/TSE.2012.30
[1] J. Highsmith and M. Fowler, "The Agile Manifesto," Software Development Magazine, vol. 9, no. 8, pp. 29-30, 2001.
[2] T. Chow and D. Cao, "A Survey Study of Critical Success Factors in Agile Software Projects," J. Systems and Software, vol. 81, no. 6, pp. 961-971, 2008.
[3] A. Cockburn and J. Highsmith, "Agile Software Development: The People Factor," Computer, vol. 34, no. 11, pp. 131-133, Nov. 2001.
[4] R. Martin, Agile Software Development: Principles, Patterns, and Practices. Pearson Education, 2002.
[5] K. Schwaber, "Scrum Guide," Scrum Alliance Resources, Scrum%20Guide.pdf, Nov. 2010.
[6] H. Sharp and H. Robinson, "An Ethnographic Study of XP Practice," Empirical Software Eng., vol. 9, no. 4, pp. 353-375, 2004.
[7] J. Highsmith, Agile Project Management: Creating Innovative Products. Addison-Weasley, 2004.
[8] XP, "Extreme Programming: A Gentle Introduction," World Wide Web electronic publication, http:/www.extremeprogramming. org/, Oct. 2010.
[9] S. Augustine, Managing Agile Projects. Prentice Hall PTR, 2005.
[10] R. Hoda, J. Noble, and S. Marshall, "Agile Undercover: When Customers Don't Collaborate," Proc. Int'l Conf. Agile Processes in Software Eng. and Extreme Programming, pp. 73-87, 2010.
[11] R. Hoda, J. Noble, and S. Marshall, "Supporting Self-Organizing Agile Teams—What's Senior Management Got to Do with It?" Proc. Int'l Conf. Agile Processes in Software Eng. and Extreme Programming, pp. 73-87, 2011.
[12] R. Hoda, J. Noble, and S. Marshall, "Impact of Inadequate Customer Involvement on Self-Organizing Agile Teams," J. Information and Software Technology, vol. 53, no. 5, pp. 521-534, 2011.
[13] R. Hoda, "Self-Organizing Agile Teams: A Grounded Theory," PhD dissertation, Eng. and Computer Science, Victoria Univ. of Wellington, New Zealand, 2011.
[14] R. Hoda, J. Noble, and S. Marshall, "Developing a Grounded Theory to Explain the Practices of Self-Organizing Agile Teams," Empirical Software Eng. J., in press, 2011.
[15] R. Hoda, J. Noble, and S. Marshall, "Organizing Self-Organizing Teams," Proc. 32nd ACM/IEEE Int'l Conf. Software Eng., pp. 285-294, 2010.
[16] R. Belbin, Team Roles at Work. Butterworth-Heinemann, 1993.
[17] D.G. Ancona and D.F. Caldwell, "Beyond Task and Maintenance: Defining External Functions in Groups," Group Organization Management, vol. 13, no. 4, pp. 468-494, 1988.
[18] C. Larman and V.R. Basili, "Iterative and Incremental Development: A Brief History," Computer, vol. 36, no. 6, pp. 47-56, June 2003.
[19] M. Lindvall, V.R. Basili, B.W. Boehm, P. Costa, K. Dangle, F. Shull, R. Tesoriero, L.A. Williams, and M.V. Zelkowitz, "Empirical Findings in Agile Methods," Proc. Second XP Universe and First Agile Universe Conf. Extreme Programming and Agile Methods, pp. 197-207, 2002.
[20] D. Robey, R. Welke, and D. Turk, "Traditional, Iterative, and Component-Based Development: A Social Analysis of Software Development Paradigms," Information Technology and Management, vol. 2, no. 1, pp. 53-70, 2001.
[21] J. Stapleton, Dynamic Systems Development Method. Addison Wesley, 1997.
[22] P. Abrahamsson, Agile Software Development Methods: Review and Analysis. VTT Publications, 2002.
[23] A. Cockburn, Crystal Clear: A Human-Powered Methodology for Small Teams. Addison-Wesley Professional, 2004.
[24] S. Palmer and M. Felsing, A Practical Guide to Feature-Driven Development. Pearson Education, 2001.
[25] J. Highsmith, Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. Dorset House Publishing, 2000.
[26] M. Pikkarainen, J. Haikara, O. Salo, P. Abrahamsson, and J. Still, "The Impact of Agile Practices on Communication in Software Development," Empirical Software Eng., vol. 13, no. 3, pp. 303-337, 2008.
[27] Scrum Alliance, World Wide Web electronic publication, , Sept. 2008.
[28] H. Takeuchi and I. Nonaka, "The New New Product Development Game," Harvard Business Rev., vol. 64, no. 1, pp. 137-146, 1986.
[29] Control Chaos, World Wide Web electronic publication, , Sept. 2010.
[30] K. Beck, Extreme Programming Explained: Embrace Change, first ed. Addison-Wesley Professional, 1999.
[31] P. Abrahamsson, J. Warsta, M.T. Siponen, and J. Ronkainen, "New Directions on Agile Methods: A Comparative Analysis," Proc. 25th Int'l Conf. Software Eng., pp. 244-254, 2003.
[32] T. Dybå and T. Dingsoyr, "Empirical Studies of Agile Software Development: A Systematic Review," Information Software Technology, vol. 50, nos. 9/10, pp. 833-859, 2008.
[33] J.E. Tomayko and O. Hazzan, Human Aspects of Software Engineering. Charles River Media, 2004.
[34] S. Nerur, R. Mahapatra, and G. Mangalaraj, "Challenges of Migrating to Agile Methodologies," Comm. ACM, vol. 48, no. 5, pp. 72-78, 2005.
[35] S. Nerur and V. Balijepally, "Theoretical Reflections on Agile Development Methodologies," Comm. ACM, vol. 50, no. 3, pp. 79-83, 2007.
[36] F.P. Brooks, Mythical Man-Month, second ed. Addison-Welsey, 1995.
[37] H.D. Mills, Software Productivity. Little Brown and Company, 1983.
[38] P.S. Taylor, D. Greer, P. Sage, G. Coleman, K. McDaid, and F. Keenan, "Do Agile GSD Experience Reports Help the Practitioner?" Proc. Int'l Workshop Global Software Development for the Practitioner, pp. 87-93, 2006.
[39] A. Cockburn, "People and Methodologies in Software Development," PhD dissertation, Univ. of Oslo, Norway, 2003.
[40] C. Mann and F. Maurer, "A Case Study on the Impact of Scrum on Overtime and Customer Satisfaction," Proc. Agile Development Conf., pp. 70-79, 2005.
[41] E. Whitworth and R. Biddle, "The Social Nature of Agile Teams," Proc. Agile '07, pp. 26-36, 2007.
[42] L. Williams, R.R. Kessler, W. Cunningham, and R. Jeffries, "Strengthening the Case for Pair Programming," IEEE Software, vol. 17, no. 4, pp. 19-25, July/Aug. 2000.
[43] A. Begel and N. Nagappan, "Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study," Proc. First Int'l Symp. Empirical Software Eng. and Measurement, pp. 255-264, 2007.
[44] H. Sharp and H. Robinson, "Collaboration and Co-Ordination in Mature Extreme Programming Teams," Int'l J. Human-Computer Studies, vol. 66, no. 7, pp. 506-518, 2008.
[45] H. Robinson and H. Sharp, "Organisational Culture and XP: Three Case Studies," Proc. Agile Development Conf./Australasian Database Conf., pp. 49-58, 2005.
[46] H. Robinson and H. Sharp, "The Social Side of Technical Practices," Proc. Sixth Int'l Conf. Extreme Programming and Agile Processes in Software Eng., pp. 100-108, 2005.
[47] L.A. Williams and R.R. Kessler, "All I Really Need to Know about Pair Programming I Learned in Kindergarten," Comm. ACM, vol. 43, no. 5, pp. 108-114, 2000.
[48] A. Martin, R. Biddle, and J. Noble, "The XP Customer Role in Practice: Three Studies," Proc. Agile Development Conf., pp. 42-54, 2004.
[49] A. Martin, R. Biddle, and J. Noble, "The XP Customer Role: A Grounded Theory," Proc. AGILE '09, 2009.
[50] P. Sfetsos, L. Angelis, and I. Stamelos, "Investigating the Extreme Programming System—An Empirical Study," Empirical Software Eng., vol. 11, no. 2, pp. 269-301, 2006.
[51] N.B. Moe, T. Dingsoyr, and T. Dybå, "Understanding Self-Organizing Teams in Agile Software Development," Proc. 19th Australian Conf. Software Eng., pp. 76-85, 2008.
[52] E. Trist, "The Evolution of Socio-Technical Systems," Occasional Paper, 1981.
[53] J. Baker, "Tightening the Iron Cage: Concertive Control in Self-Managing Teams," Administrative Science Quarterly, vol. 38, no. 3, pp. 408-437, 1993.
[54] K. Lewin, Resolving Social Conflicts: Selected Papers on Group Dynamics. Harper and Row, 1948.
[55] K. Schwaber, "Agile Processes and Self-Organization," Control Chaos, 20Organization.pdf , Mar. 2010.
[56] J. Hut and E. Molleman, "Empowerment and Team Development," Team Performance Management, vol. 4, no. 2, pp. 53-66, 1998.
[57] E. Molleman, "Variety and the Requisite of Self-Organization," Int'l J. Organizational Analysis, vol. 6, no. 2, pp. 109-131, 1998.
[58] G. Morgan, Images of Organization. Sage Publications, 1986.
[59] "Book Reviews Comptes Rendus," Canadian Public Administration, vol. 32, no. 2, pp. 320-339, 1989.
[60] R. Ashby, An Introduction to Cybernetics. Chapman and Hall, 1956.
[61] I. Nonaka, "A Dynamic Theory of Organizational Knowledge Creation," Organization Science, vol. 5, no. 1, pp. 14-37, 1994.
[62] S.A. Kauffman, The Origins of Order. Oxford Univ. Press, 1993.
[63] S.J. Lansing, "Complex Adaptive Systems," Ann. Rev. Anthropology, vol. 32, pp. 183-204, 2003.
[64] S.A. Levin, "Ecosystems and the Biosphere as Complex Adaptive Systems," Ecosystems, vol. 1, no. 5, pp. 431-436, 1998.
[65] R. Lewin, "From Chaos to Complexity: Implications for Organizations," Executive Development, vol. 7, no. 4, pp. 16-17, 1994.
[66] C. Anderson and E. McMillan, "Of Ants and Men: Self-Organized Teams in Human and Insect Organizations," Emergence: Complexity Organization, vol. 5, no. 2, pp. 29-41, 2003.
[67] R. Lewin, Complexity—Life at the Edge of Chaos. Dent, 1993.
[68] J. Sutherland, "Roots of Scrum: Takeuchi and Self-Organizing Teams," World Wide Web electronic publication, http:/, Mar. 2010.
[69] D. Larsen, "Team Agility: Exploring Self-Organizing Software Development Teams," Industrial Logic and The Agile Times Newsletter, TeamAgilityAgileTimesFeb04.pdf, Nov. 2010.
[70] M. Berteig, "Team Self-Organization," Agile Advice, 12Agile_work_uses_2. html, Nov. 2010.
[71] A. Elssamadisy, Agile Adoption Patterns: A Roadmap to Organizational Success. Addison-Weasley Professional, 2008.
[72] T. Chau and F. Maurer, "Knowledge Sharing in Agile Software Teams," Proc. Logic versus Approximation, pp. 173-183, 2004.
[73] L. Anderson, G. Alleman, K. Beck, J. Blotner, W. Cunningham, M. Poppendieck, and R. Wirfs-Brock, "Agile Management—An Oxymoron?: Who Needs Managers Anyway?" Proc. 18th Ann. ACM SIGPLAN Conf. Object-Oriented Programming, Systems, Languages, and Applications, pp. 275-277,, 2003.
[74] N.B. Moe, T. Dingsøyr, and T. Dybå, "A Teamwork Model for Understanding an Agile Team: A Case Study of a Scrum Project," Information and Software Technology, vol. 52, no. 5, pp. 480-491, 2010.
[75] T. Dickinson and R. McIntyre, "A Conceptual Framework for Teamwork Measurement," Team Performance Assessment and Measurement: Theory, Methods, and Applications, pp. 19-43, Routledge, 1997.
[76] B. Glaser, Basics of Grounded Theory Analysis: Emergence vs. Forcing. Sociology Press, 1992.
[77] B. Glaser and A.L. Strauss, The Discovery of Grounded Theory. Aldine, 1967.
[78] B. Glaser, Theoretical Sensitivity: Advances in the Methodology of Grounded Theory. Sociology Press, 1978.
[79] G. Allan, "The Legitimacy of Grounded Theory," Proc. Fifth European Conf. Business Research Methods, pp. 1-8, 2006.
[80] J.W. Creswell, Research Design: Qualitative, Quantitative, and Mixed Methods and Approaches, second ed. Sage Publications, 2003.
[81] K. Charmaz, Constructing Grounded Theory: A Practical Guide through Qualitative Analysis, first ed. Sage Publications, 2006.
[82] B. Glaser, "Remodeling Grounded Theory," Forum: Qualitative Social Research, vol. 5, no. 2,article 4, 2004.
[83] B. Glaser, "Grounded Theory Institute: Methodology of Barney G. Glaser," http:/, Apr. 2010.
[84] S. Adolph, W. Hall, and P. Kruchten, "A Methodological Leg to Stand On: Lessons Learned Using Grounded Theory to Study Software Development," Proc. Conf. Center for Advanced Studies on Collaborative Research: Meeting of Minds, pp. 166-178, 2008.
[85] J.Q. Benoliel, "Grounded Theory and Nursing Knowledge," Qualitative Health Research, vol. 6, no. 3, pp. 406-428, 1996.
[86] N. Elliot and A. Lazenbatt, "How to Recognize a 'Quality' Grounded Theory Research Study," Australian J. Advanced Nursing, vol. 22, no. 3, pp. 48-52, 2005.
[87] A.K. Nathaniel, "A Grounded Theory of Moral Reckoning in Nursing," PhD dissertation, West Virginia Univ., 2003.
[88] A. Lambert, "Fluid Families: A Theoretical Model for Determining Family Membership within Blended and Ex-Blended Families," Proc. 93rd Ann. Convention Nat'l Comm. Assoc., 2007.
[89] APN "Agile Professionals Network," World Wide Web electronic publication, http:/, Sept. 2010.
[90] ASCI, "Agile Software Community of India," World Wide Web electronic publication, http:/, Sept. 2010.
[91] L. Abraham, "Cultural Differences in Software Engineering," Proc. India Software Eng. Conf., pp. 95-100, 2009.
[92] M. Summers, "Insights into an Agile Adventure with Offshore Partners," Proc. Agile '06, pp. 333-338, 2008.
[93] K. Sureshchandra and J. Shrinivasavadhani, "Adopting Agile in Distributed Development," Proc. IEEE Int'l Conf. Global Software Eng., pp. 217-221, 2008.
[94] J. Sutherland, G. Schoonheim, E. Rustenburg, and M. Rijk, "Fully Distributed Scrum: The Secret Sauce for Hyperproductive Offshored Development Teams," Proc. Agile '08, pp. 339-344, 2008.
[95] E. Uy and N. Ioannou, "Growing and Sustaining an Offshore Scrum Engagement," Proc. Agile '08, 2008.
[96] B. Glaser, The Grounded Theory Perspective III: Theoretical Coding. Sociology Press, 2005.
[97] B. Glaser, Doing Grounded Theory: Issues and Discussions. Sociology Press, 1998.
[98] S. Georgieva and G. Allan, "Best Practices in Project Management through a Grounded Theory Lens," Electronic J. Business Research Methods, vol. 1, pp. 43-52, 2008.
[99] G. Allan, "A Critique of Using Grounded Theory as a Research Method," Electronic J. Business Research Methods, vol. 2, no. 1, pp. 1-10, 2003.
[100] R. Hoda, J. Noble, and S. Marshall, "Balancing Acts: Walking the Agile Tightrope," Proc. Workshop ICSE Co-Operative and Human Aspects of Software Eng., 2010.
[101] S. Fraser, R. Reinitz, J. Eckstein, J. Kerievsky, R. Mee, and M. Poppendieck, "Xtreme Programming and Agile Coaching," Proc. Companion of the 18th Ann. ACM SIGPLAN Conf. Object-Oriented Programming, Systems, Languages, and Applications, pp. 265-267, 2003.
[102] P.S. Grisham and D.E. Perry, "Customer Relationships and Extreme Programming," Proc. Workshop Human and Social Factors of Software Eng., pp. 1-6, 2005.
[103] R. Hoda, J. Noble, and S. Marshall, "What Language Does Agile Speak?" Proc. Int'l Conf. Agile Processes in Software Eng. and Extreme Programming, pp. 387-388, 2010.
[104] R. Hoda, J. Noble, and S. Marshall, "Agility in Context," Proc. ACM Int'l Conf. Object Oriented Programming Systems, Languages, and Applications, pp. 74-88, 2010.
[105] B. Dagenais, H. Ossher, R.K.E. Bellamy, M.P. Robillard, and J.P. de Vries, "Moving into a New Software Project Landscape," Proc. 32nd ACM/IEEE Int'l Conf. Software Eng., pp. 275-284, 2010.
[106] S. Sawyer, P.J. Guinan, and J. Cooprider, "Social Interactions of Information Systems Development Teams: A Performance Perspective," Information Systems J., vol. 20, pp. 81-107, Jan. 2010.
[107] N.B. Moe and T. Dingsoyr, "Scrum and Team Effectiveness: Theory and Practice," Proc. Int'l Conf. Agile Processes in Software Eng. and Extreme Programming, pp. 11-20, 2008.
[108] L. Rising and N.S. Janoff, "The Scrum Software Development Process for Small Teams," IEEE Software, vol. 17, no. 4, pp. 26-32, July/Aug. 2000.
[109] K. Schwaber and M. Beedle, Agile Software Development with SCRUM. Prentice-Hall, 2002.
[110] S. Hastie, "Organizing Self-Organizing Agile Teams," InfoQ article, , Nov. 2010.
[111] A. Kearns, "Converting Waterfall Requirements into Underground Agile Features," World Wide Web electronic publication, Peruse+ Muse+InfuseConverting+Waterfall+Requirements+into+ Underground +Agile+Features.aspx , Nov. 2010.
[112] K.D. Hoeppner, "Agile Undercover," World Wide Web electronic publication, 23Agile-undercover/, Nov. 2010.
[113] Derby, Esther "A Tale of a Too Hands-Off Manager," World Wide Web electronic publication, , Nov. 2010.
[114] S. Mamoli, "Agile Undercover: When Customers Don't Collaborate," World Wide Web electronic publication, http://www. , Nov. 2010.
[115] B. Glaser, "Naturalist Inquiry and Grounded Theory," Forum: Qualitative Social Research, vol. 5, no. 1,article 7, 2004.
4 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool