Successful extreme programming: fidelity to the methodology or good teamworking?

Wood, S. and Michaelides, George and Thomson, C. (2013) Successful extreme programming: fidelity to the methodology or good teamworking? Information and Software Technology 55 (4), pp. 660-672. ISSN 0950-5849.

Full text not available from this repository.

Official URL: http://dx.doi.org/10.1016/j.infsof.2012.10.002

Abstract

Context: Developing a theory of agile technology, in combination with empirical work, must include assessing its performance effects, and whether all or some of its key ingredients account for any performance advantage over traditional methods. Given the focus on teamwork, is the agile technology what really matters, or do general team factors, such as cohesion, primarily account for a team’s success? Perhaps the more specific software engineering team factors, for example the agile development method’s collective ownership and code management, are decisive. Objective: To assess the contribution of agile methodology, agile-specific team methods, and general team factors in the performance of software teams. Method: We studied 40 small-scale software development teams which used Extreme Programming (XP). We measured (1) the teams’ adherence to XP methods, (2) their use of XP-specific team practices, and (3) standard team attributes, as well as the quality of the project’s outcomes. We used Williams et al.’s (2004a) [33] Shodan measures of XP methods, and regression analysis. Results: All three types of variables are associated with the project’s performance. Teamworking is important but it is the XP-specific team factor (continuous integration, coding standards, and collective code ownership) that is significant. Only customer planning (release planning/planning game, customer access, short releases, and stand-up meeting) is positively related to performance. A negative relationship between foundations (automated unit tests, customer acceptance tests, test-first design, pair programming, and refactoring) is found and is moderated by craftsmanship (sustainable pace, simple design, and metaphor/system of names). Of the general team factors only cooperation is related to performance. Cooperation mediates the relationship between the XP-specific team factor and performance. Conclusion: Client and team foci of the XP method are its critical active ingredients.

Metadata

Item Type:	Article
Keyword(s) / Subject(s):	Software development, Extreme programming, Agile methods, Teamwork, Cooperation, Performance
School:	Birkbeck Faculties and Schools > Faculty of Business and Law > Birkbeck Business School
Depositing User:	Administrator
Date Deposited:	19 Dec 2012 14:26
Last Modified:	02 Aug 2023 17:01
URI:	https://eprints.bbk.ac.uk/id/eprint/5908

Statistics

Archive Staff Only (login required)

Edit/View Item