%0 Conference Paper %1 abrahamsson04ese %A Abrahamsson, P. %A Koskela, J. %B International Symposium on Empirical Software Engineering %C Redondo Beach, CA %D 2004 %K agile extreme productivity programming %P 73-82 %T Extreme programming: a survey of empirical data from a controlled case study %U http://dx.doi.org/10.1109/ISESE.2004.1334895 %X Extreme programming (XP) is a well known agile software development method. While a number of experience reports have been published in recent years, agile software development in general and XP in particular have strongly been criticized for the lack of empirical data. This paper reports a survey of the empirical data obtained from a controlled case study on extreme programming in practical settings. Thus, no hypotheses were set a priori. Four software engineers were acquired to implement a Web-based system (7698 Locs, 820 hours) for data management in a delivery schedule of eight weeks. Development environment was close to the agile home ground. Collected empirical data is grounded on three basic data points: time, size and defects. Data is organized around five system releases, each which were tested by 17 customer testers. System release defect-density was 1.43 defects/KLOC, team overall productivity 16.90 Locs/hour and rework costs were 9.8% of the total development effort. The implications of this study are discussed.

@inproceedings{abrahamsson04ese, abstract = { Extreme programming (XP) is a well known agile software development method. While a number of experience reports have been published in recent years, agile software development in general and XP in particular have strongly been criticized for the lack of empirical data. This paper reports a survey of the empirical data obtained from a controlled case study on extreme programming in practical settings. Thus, no hypotheses were set a priori. Four software engineers were acquired to implement a Web-based system (7698 Locs, 820 hours) for data management in a delivery schedule of eight weeks. Development environment was close to the agile home ground. Collected empirical data is grounded on three basic data points: time, size and defects. Data is organized around five system releases, each which were tested by 17 customer testers. System release defect-density was 1.43 defects/KLOC, team overall productivity 16.90 Locs/hour and rework costs were 9.8% of the total development effort. The implications of this study are discussed.}, added-at = {2008-05-22T22:29:19.000+0200}, address = {Redondo Beach, CA}, author = {Abrahamsson, P. and Koskela, J.}, biburl = {https://www.bibsonomy.org/bibtex/215ff6d3aa52ddf097c7f905d1919f380/neilernst}, booktitle = {International Symposium on Empirical Software Engineering}, interhash = {579fe5d3d3e6be550ee7b49f4b4369ff}, intrahash = {15ff6d3aa52ddf097c7f905d1919f380}, keywords = {agile extreme productivity programming}, month = {August}, pages = {73-82}, timestamp = {2008-05-22T22:29:20.000+0200}, title = {Extreme programming: a survey of empirical data from a controlled case study}, url = {http://dx.doi.org/10.1109/ISESE.2004.1334895}, year = 2004 }