Issue No. 03 - March (2013 vol. 39)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/TSE.2012.30
James Noble , Victoria University of Wellington, Wellington
Rashina Hoda , The University of Auckland, Auckland
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
James Noble, Rashina Hoda, Stuart Marshall, "Self-Organizing Roles on Agile Software Development Teams", IEEE Transactions on Software Engineering, vol. 39, no. , pp. 422-444, March 2013, doi:10.1109/TSE.2012.30