Understanding Self-Organizing Teams in Agile Software Development
Moe, N.B.
Dingsoyr, T.
Dyba, T.
SINTEF ICT, Trondheim;
This paper appears in: Software Engineering, 2008. ASWEC 2008. 19th Australian Conference on
Publication Date: 26-28 March 2008
On page(s): 76-85
Location: Perth, WA,
ISSN: 1530-0803
ISBN: 978-0-7695-3100-7
INSPEC Accession Number: 9913073
Digital Object Identifier: 10.1109/ASWEC.2008.4483195
Current Version Published: 2008-04-03
Abstract
Traditional software teams consist of independently focused self-managing professionals with high individual but low team autonomy. A challenge with introducing agile software development is that it requires a high level of both individual and team autonomy. This paper studies the barriers with introducing self-organizing teams in agile software development and presents data from a seven month ethnographic study of professional developers in a Scrum team. We found the most important barrier to be the highly specialized skills of the developers and the corresponding division of work. In addition we found a lack of system for team support, and reduced external autonomy to be important barriers for introducing self- organizing teams. These findings have implications for software development managers and practitioners.
Index
Terms
Available to subscribers and IEEE members.
References
Available to subscribers and IEEE members.
Citing Documents
Available to subscribers and IEEE members.