Customer relationships and Extreme Programming
HSSE '05 Proceedings of the 2005 workshop on Human and social factors of software engineering
A risk-driven method for eXtreme programming release planning
Proceedings of the 28th international conference on Software engineering
Information and Software Technology
Identifying some important success factors in adopting agile software development practices
Journal of Systems and Software
On the measurement of agility in software process
ICSP'07 Proceedings of the 2007 international conference on Software process
Successful extreme programming: Fidelity to the methodology or good teamworking?
Information and Software Technology
Empirical Software Engineering
| Hi-index | 0.00 |
The paper describes an experiment carried out duringthe Spring/2002 academic semester with computerscience students at the University of Sheffield. The aim ofthe experiment was to assess extreme programming andcompare it with a traditional approach. With this purposethe students constructed software for real clients. Weobserved 20 teams working for 4 clients. Ten teamsworked with extreme programming and ten with thetraditional approach. In terms of quality and size teamsworking with extreme programming produced similarfinal products to traditional teams. The major implicationfor the current practice of traditional softwareengineering is that in spite of the absence of design andthe presence of testing before coding the product obtainedstill has similar quality and size. The implication forextreme programming is the possibility of growth andmaturation given the fact that it provided results thatwere as good as those from the traditional approach.