Turning the Knobs: A Coaching Pattern for XP through Agile Metrics
Proceedings of the Second XP Universe and First Agile Universe Conference on Extreme Programming and Agile Methods - XP/Agile Universe 2002
Top Management-Team Diversity and Firm Performance: Examining the Role of Cognitions
Organization Science
Extreme Programming Refactored: The Case Against XP
Extreme Programming Refactored: The Case Against XP
A Formal Experiment Comparing Extreme Programming with Traditional Software Construction
ENC '03 Proceedings of the 4th Mexican International Conference on Computer Science
Analyses of an Agile Methodology Implementation
EUROMICRO '04 Proceedings of the 30th EUROMICRO Conference
Exploring Extreme Programming in Context: An Industrial Case Study
ADC '04 Proceedings of the Agile Development Conference
Introducing an Agile Process in a Software Maintenance and Evolution Organization
CSMR '05 Proceedings of the Ninth European Conference on Software Maintenance and Reengineering
Development Life Cycle Management: A Multiproject Experiment
ECBS '05 Proceedings of the 12th IEEE International Conference and Workshops on Engineering of Computer-Based Systems
Challenges of migrating to agile methodologies
Communications of the ACM - Adaptive complex enterprises
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
Personality characteristics in an XP team: a repertory grid study
HSSE '05 Proceedings of the 2005 workshop on Human and social factors of software engineering
Customising agile methods to software practices at Intel Shannon
European Journal of Information Systems - Including a special section on business agility and diffusion of information technology
The Social Nature of Agile Teams
AGILE '07 Proceedings of the AGILE 2007
Empirical studies of agile software development: A systematic review
Information and Software Technology
Empirical Software Engineering
Running an Agile Software Development Project
Running an Agile Software Development Project
The effectiveness of pair programming: A meta-analysis
Information and Software Technology
Information Systems Research
ACM Transactions on Software Engineering and Methodology (TOSEM)
Measuring fidelity to extreme programming: a psychometric approach
Empirical Software Engineering
Proceedings of the ACM international conference on Object oriented programming systems languages and applications
Hi-index | 0.00 |
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.