Evaluating the Effect of Agile Methods on Software Defect Data and Defect Reporting Practices - A Case Study
2012 Eighth International Conference on the Quality of Information and Communications Technology (2010)
Sept. 29, 2010 to Oct. 2, 2010
In large, traditional software development projects, the number of defects can be considerably high. Agile methods promise code quality improvement, but while embracing the agile methods, software development organizations have realized that defects still do exist and must be managed. When the development is distributed over several sites, defect management can become even more challenging. In this study we analyzed defect data in a large multi-site organization during the first twelve months of their agile transformation. Complementing information was gathered by a survey, which was conducted in the organization twice: after six and after twelve months of starting the agile transformation. The results indicate that the defect reporting practices changed after the agile adoption was started, the defect inflow was more stable and the defect closing speed improved.
Defect management, quality, agile transformation, distributed software development
Kirsi Korhonen, "Evaluating the Effect of Agile Methods on Software Defect Data and Defect Reporting Practices - A Case Study", 2012 Eighth International Conference on the Quality of Information and Communications Technology, vol. 00, no. , pp. 35-43, 2010, doi:10.1109/QUATIC.2010.18