Challenges to teamwork: A multiple case study of two agile teams

36Citations
Citations of this article
151Readers
Mendeley users who have this article in their library.
Get full text

Abstract

Agile software development has become the standard in many companies. While there are reports of major improvements with agile development over traditional development, many teams still strive to work effectively as a team. A multiple case study in two companies discovered challenges related to communication, learning and selecting the tasks according to the priority list. For example, the fact that the developers were not actively involved in the planning process, resulted in weak team orientation; even though the teams had identified and discussed recurring problems, they found it difficult to improve their teamwork practices; and because customers and support communicated tasks directly to the developers and developers chose tasks according to interest and expertise, following the priority list became difficult. We provide practical suggestions for teamwork in agile software development that intend to overcome these problems and strengthen team orientation and team learning in order to achieve effective agile teams. © 2011 Springer-Verlag Berlin Heidelberg.

Cite

CITATION STYLE

APA

Gulliksen Stray, V., Moe, N. B., & Dingsøyr, T. (2011). Challenges to teamwork: A multiple case study of two agile teams. In Lecture Notes in Business Information Processing (Vol. 77 LNBIP, pp. 146–161). Springer Verlag. https://doi.org/10.1007/978-3-642-20677-1_11

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free