An Instrument for Measuring the Key Factors of Successin Software Process Improvement
Empirical Software Engineering
Process Improvement and the Corporate Balance Sheet
IEEE Software
Systematic review: Systematic review of organizational motivations for adopting CMM-based SPI
Information and Software Technology
Empirical studies of agile software development: A systematic review
Information and Software Technology
Motivation in Software Engineering: A systematic literature review
Information and Software Technology
Do software process improvements lead to ISO 9126 architectural quality factor improvement
Proceedings of the 8th international workshop on Software quality
| Hi-index | 0.00 |
This paper presents the results of a systematic review on the impacts of Software Process Improvement (SPI) on developers. This review selected 26 studies from the highest quality journals, conferences, and workshop in the field. The results were compiled and organized following the grounded theory approach. Results from the grounded theory were further categorized using the Ishikawa (or fishbone) diagram. The Ishikawa Diagram models all the factors potentially impacting software developers, and shows both the positive and negative impacts. Positive impacts include a reduction in the number of crises, and an increase in team communications and morale, as well as better requirements and documentation. Negative impacts include increased overhead on developers through the need to collect data and compile documentation, an undue focus on technical approaches, and the fact that SPI is oriented toward management and process quality, and not towards developers and product quality. This systematic review should support future practice through the identification of important obstacles and opportunities for achieving SPI success. Future research should also benefit from the problems and advantages of SPI identified by developers.