Calculating Software Process Improvement's Return on Investment

Abstract Many organizations and firms invest in software process improvement (SPI). They do this in order to satisfy business goals for customer satisfaction, time-to-market, cost, quality, and reliability. Return on investment (ROI) is a traditional approach for measuring the business or monetary value of an investment. As such, it can be used for measuring the economic benefit of investing in SPI. Measuring the ROI of SPI is still in its early infancy, in spite of the fact that ROI has been around for many decades and the discipline of SPI itself has also been popular for at least 20 years. It is important to note that ROI is a metric that can be used before and after an investment in SPI. ROI can be used to evaluate (a priori) investment opportunities and make a proper selection and ROI can be used to evaluate (a posteriori) the extent to which an investment was legitimate. Although the value of using ROI for SPI calculations seems self evident, using ROI in practice often proves difficult. In this chapter we provide an overview of how to apply ROI calculations to enhance decision making processes involving SPI. We approach these calculations from two dimensions: modelling and measuring. For each of these dimensions we provide pragmatic approaches for real-life decision making, all illustrated with actual case studies. The chapter contains guidelines, approaches, and experiences on how to do this in practice. It supports making simple but sound financial evaluations when using SPI to improve organizational performance. The main message of this chapter is that ROI can and must be calculated for most SPI investment decisions as a means of ultimately satisfying business goals and objectives. ROI can and should be an explicit part of software management and engineering decision making processes when it comes to SPI, which can minimize effort, costs, and financial investments. Software managers and engineers should include financial considerations such as ROI in their decisions, as well as technical ones, in order to satisfy business goals and objectives for SPI.

[1]  Hylton Boothroyd Image Theory: Decision Making in Personal and Organizational Contexts. , 1990 .

[2]  Mary Beth Chrissis,et al.  CMMI: Guidelines for Process Integration and Product Improvement , 2003 .

[3]  Steve Tockey,et al.  Return on Software: Maximizing the Return on Your Software Investment , 2004 .

[4]  J. Bach Enough About Process: What We Need are Heroes , 1995, IEEE Softw..

[5]  James D. Herbsleb,et al.  After the Appraisal: A Systematic Survey of Process Improvement, its Benefits, and Factors that Influence Success. , 1995 .

[6]  Capers Jones,et al.  The Economics of Software Process Improvement , 1996, Computer.

[7]  R. R. Willis,et al.  Hughes Aircraft's Widespread Deployment of a Continuously Improving Software Process , 1998 .

[8]  Tom DeMarco,et al.  Peopleware: Productive Projects and Teams , 1987 .

[9]  John Snyder,et al.  Quantitative evaluation of software process improvement , 1995, J. Syst. Softw..

[10]  Watts S. Humphrey,et al.  Comments on 'A Critical Look' , 1991, IEEE Softw..

[11]  Robert B. Grady,et al.  Software Metrics: Establishing a Company-Wide Program , 1987 .

[12]  Egon Berghout,et al.  Integrating goal-oriented measurement in industrial software engineering: industrial experiences with and additions to the Goal/Question/Metric method (GQM) , 2001, Proceedings Seventh International Software Metrics Symposium.

[13]  Michiel van Genuchten,et al.  Software Quality in Consumer Electronics Products , 1996, IEEE Softw..

[14]  Hakan Erdogmus,et al.  Keep Your Options Open: Extreme Programming and the Economics of Flexibility , 2002 .

[15]  Susan Rosenbaum,et al.  Schlumberger's Software Improvement Program , 1994, IEEE Trans. Software Eng..

[16]  Khaled El Emam The ROI from Software Quality , 2005 .

[17]  James D. Herbsleb,et al.  Software quality and the Capability Maturity Model , 1997, CACM.

[18]  Raymond Dion,et al.  Process improvement and the corporate balance sheet , 1993, IEEE Software.

[19]  Rini van Solingen,et al.  Measuring the ROI of Software Process Improvement , 2004, IEEE Softw..

[20]  Donald J. Reifer,et al.  Let the Numbers Do the Talking , 2002 .

[21]  Terry Bollinger,et al.  A critical look at software capability evaluations , 1991, IEEE Software.

[22]  Watts S. Humphrey,et al.  Software process improvement at Hughes Aircraft , 1991, IEEE Software.

[23]  van Dm Rini Solingen,et al.  Product focused software process improvement : SPI in the embedded software domain , 2000 .

[24]  Egon Berghout,et al.  Interrupts: Just a Minute Never Is , 1998, IEEE Softw..

[25]  Vijay Sikka Maximizing ROI on Software Development , 2004 .

[26]  Michael E. Fagan Advances in software inspections , 1986, IEEE Transactions on Software Engineering.

[27]  Giancarlo Succi,et al.  Extreme Programming Perspectives , 2002 .

[28]  Jack J. Phillips,et al.  Return on Investment in Training and Performance Improvement Programs , 1997 .

[29]  David F. Rico ROI of Software Process Improvement: Metrics for Project Managers and Software Engineers , 2004 .

[30]  Mark C. Paulk,et al.  Capability Maturity Model for Software, Version 1.1 , 1993 .

[31]  Jim Highsmith,et al.  Agile Software Development Ecosystems , 2002 .

[32]  Thomas Gilb,et al.  Software Inspection , 1994 .

[33]  Watts S. Humphrey,et al.  Introduction to the Team Software Process , 1999 .

[34]  Watts S. Humphrey,et al.  A discipline for software engineering , 2012, Series in software engineering.

[35]  Egon Berghout Evaluation of Information System Proposals - Design of a decision support method , 1997 .

[36]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[37]  Thomas J. Haley,et al.  Software Process Improvement At Raytheon , 1996, IEEE Softw..

[38]  Michael Diaz,et al.  How CMM Impacts Quality, Productivity, Rework, and the Bottom Line , 2002 .

[39]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.

[40]  Ware Myers,et al.  Measures for Excellence: Reliable Software on Time, Within Budget , 1991 .

[41]  Watts S. Humphrey,et al.  Results of Applying the Personal Software Process , 1997, Computer.

[42]  Peter Kulik,et al.  Software Metrics "State of the Art" - 2000 , 2000 .

[43]  Michael Daskalantonakis,et al.  A Practical View of Software Measurement and Implementation Experiences Within Motorola , 1992, IEEE Trans. Software Eng..

[44]  Lowell Jay Arthur Quantum improvements in software system quality , 1997, CACM.

[45]  Marvin V. Zelkowitz,et al.  SEL's Software Process Improvement Program , 1995, IEEE Softw..

[46]  Mayuram S. Krishnan,et al.  Evaluating the cost of software quality , 1998, CACM.

[47]  Donna K. Dunaway,et al.  Why Do Organizations Have Assessments? Do They Pay Off? , 1999 .

[48]  R. Kaplan,et al.  The Balanced Scorecard: Translating Strategy into Action , 1996 .

[49]  Michael Diaz,et al.  How Software Process Improvement Helped Motorola , 1997, IEEE Softw..

[50]  Donald J. Reifer Making the software business case : improvement by the numbers , 2002 .

[51]  James D. Herbsleb,et al.  Benefits of CMM-Based Software Process Improvement: Executive Summary of Initial Results , 1994 .