A systematic review and an expert survey on capabilities supporting multi product lines
Information and Software Technology
A persona-based approach for exploring architecturally significant requirements in agile projects
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
A taxonomy for requirements engineering and software test alignment
ACM Transactions on Software Engineering and Methodology (TOSEM)
A decision support framework for metrics selection in goal-based measurement programs: GQM-DSFMS
Journal of Systems and Software
| Hi-index | 0.00 |
BACKGROUND—Software Process Improvement (SPI) is a systematic approach to increase the efficiency and effectiveness of a software development organization and to enhance software products. OBJECTIVE—This paper aims to identify and characterize evaluation strategies and measurements used to assess the impact of different SPI initiatives. METHOD—The systematic literature review includes 148 papers published between 1991 and 2008. The selected papers were classified according to SPI initiative, applied evaluation strategies, and measurement perspectives. Potential confounding factors interfering with the evaluation of the improvement effort were assessed. RESULTS—Seven distinct evaluation strategies were identified, wherein the most common one, “Pre-Post Comparison,” was applied in 49 percent of the inspected papers. Quality was the most measured attribute (62 percent), followed by Cost (41 percent), and Schedule (18 percent). Looking at measurement perspectives, “Project” represents the majority with 66 percent. CONCLUSION—The evaluation validity of SPI initiatives is challenged by the scarce consideration of potential confounding factors, particularly given that “Pre-Post Comparison” was identified as the most common evaluation strategy, and the inaccurate descriptions of the evaluation context. Measurements to assess the short and mid-term impact of SPI initiatives prevail, whereas long-term measurements in terms of customer satisfaction and return on investment tend to be less used.