Empirical Evaluation of Agile Software Development: The Controlled Case Study Approach
O. Salo, and P. Abrahamsson. Product Focused Software Process Improvement, page 408--423. Kansai Science City, Japan, (April 2004)
Abstract
Agile software development, despite its novelty, is an important domain of research within software engineering discipline. Agile proponents have put forward a great deal of anecdotal evidence to support the application of agile methods in various application domains and industry sectors. Scientifically grounded empirical evidence is, however, still very limited. Most scientific research to date has been conducted on focused practices performed in university settings. In order to generate impact on both the scientific and practical software engineering community, new approaches are needed for performing empirically validated agile software development studies. To meet these needs, this paper presents a controlled case study approach, which has been applied in a study of extreme programming methodology performed in close-to-industry settings. The approach considers the generation of both quantitative and qualitative data. Quantitative data is grounded on three data points (time, size, and defect) and qualitative data on developers’ research diaries and post-mortem sessions.
ER -
%0 Conference Paper
%1 salo04
%A Salo, Outi
%A Abrahamsson, Pekka
%B Product Focused Software Process Improvement
%C Kansai Science City, Japan
%D 2004
%K case-study should-read
%P 408--423
%T Empirical Evaluation of Agile Software Development: The Controlled Case Study Approach
%U http://www.springerlink.com/content/ql4cwua10aghv6pc
%X Agile software development, despite its novelty, is an important domain of research within software engineering discipline. Agile proponents have put forward a great deal of anecdotal evidence to support the application of agile methods in various application domains and industry sectors. Scientifically grounded empirical evidence is, however, still very limited. Most scientific research to date has been conducted on focused practices performed in university settings. In order to generate impact on both the scientific and practical software engineering community, new approaches are needed for performing empirically validated agile software development studies. To meet these needs, this paper presents a controlled case study approach, which has been applied in a study of extreme programming methodology performed in close-to-industry settings. The approach considers the generation of both quantitative and qualitative data. Quantitative data is grounded on three data points (time, size, and defect) and qualitative data on developers’ research diaries and post-mortem sessions.
ER -
@inproceedings{salo04,
abstract = {Agile software development, despite its novelty, is an important domain of research within software engineering discipline. Agile proponents have put forward a great deal of anecdotal evidence to support the application of agile methods in various application domains and industry sectors. Scientifically grounded empirical evidence is, however, still very limited. Most scientific research to date has been conducted on focused practices performed in university settings. In order to generate impact on both the scientific and practical software engineering community, new approaches are needed for performing empirically validated agile software development studies. To meet these needs, this paper presents a controlled case study approach, which has been applied in a study of extreme programming methodology performed in close-to-industry settings. The approach considers the generation of both quantitative and qualitative data. Quantitative data is grounded on three data points (time, size, and defect) and qualitative data on developers’ research diaries and post-mortem sessions.
ER -},
added-at = {2008-05-22T22:33:41.000+0200},
address = {Kansai Science City, Japan},
author = {Salo, Outi and Abrahamsson, Pekka},
biburl = {https://www.bibsonomy.org/bibtex/2eae2b1e34649d60a5a60484a9c0f8628/neilernst},
booktitle = {Product Focused Software Process Improvement},
interhash = {e36d75525668852d2b9b25e40e577b88},
intrahash = {eae2b1e34649d60a5a60484a9c0f8628},
keywords = {case-study should-read},
month = {April},
pages = {408--423},
timestamp = {2008-05-22T22:33:42.000+0200},
title = {Empirical Evaluation of Agile Software Development: The Controlled Case Study Approach},
url = {http://www.springerlink.com/content/ql4cwua10aghv6pc},
year = 2004
}