This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Follow-Up Reflection on Software Process Improvement ROI
September/October 2009 (vol. 26 no. 5)
pp. 77-79
ASCII Text
x 
 
Rini van Solingen, "A Follow-Up Reflection on Software Process Improvement ROI," IEEE Software, vol. 26, no. 5, pp. 77-79, September/October, 2009.
 
 
BibTex
x
 
@article{ 10.1109/MS.2009.120,
author = {Rini van Solingen},
title = {A Follow-Up Reflection on Software Process Improvement ROI},
journal ={IEEE Software},
volume = {26},
number = {5},
issn = {0740-7459},
year = {2009},
pages = {77-79},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2009.120},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - A Follow-Up Reflection on Software Process Improvement ROI
IS - 5
SN - 0740-7459
SP77
EP79
EPD - 77-79
A1 - Rini van Solingen,
PY - 2009
KW - software process improvement
KW - return on investment
KW - value-based software engineering
KW - Six Sigma
KW - management commitment
KW - benefit measurement
VL - 26
JA - IEEE Software
ER -
 
Rini van Solingen, Delft University of Technology
The software engineering discipline's continuing growth urges a shift toward value-based software engineering, to prove its contributions to the bottom line. However, the number of studies containing return-on-investment (ROI) data on software process improvement (SPI) hasn't grown much in the five years following the 2004 IEEE Software article "Measuring the ROI of Software Process Improvement." Because software engineering is so strongly related to the success and failure of business, we must find a way to measure value. The adoption of Six Sigma might just be the catalyst needed for the software engineering discipline. Software companies that embrace Six Sigma to structure their improvements will outclass competitors because of their skill in having their improvement efforts contribute directly to the financial bottom line.

1. R. van Solingen, "Measuring the ROI of Software Process Improvement," IEEE Software, May/June 2004, pp. 32–38.
2. V. Ramesh, R.L. Glass, and I. Vessey, "Research in Computer Science: An Empirical Study," J. Systems and Software, vol. 70, nos. 1–2, 2004, pp. 165–176.
3. B. Boehm, "Value-Based Software Engineering: Overview and Agenda," Value-Based Software Engineering, S. Biffl et al., eds., Springer, 2005, pp. 3–14.
4. R. van Solingen, and D.F. Rico, "Calculating Software Process Improvement's Return on Investment," Advances in Computers 66: Quality Software Development, Elsevier, 2006, pp. 2–43.
5. D.F. Rico, H.H. Sayani, and S. Sone, The Business Value of Agile Software Methods: Maximizing ROI with Just-in-Time Processes and Documentation, J. Ross, 2009.
6. K. Hyde and D. Wilson, "Intangible Benefits of CMM-Based Software Process Improvement," Software Process: Improvement and Practice, vol. 9, no. 4, 2004, pp. 217–228.
7. J. Siviy, M.L. Penn, and E. Harper, "Relationships between CMMI and Six Sigma," tech. note CMU/SEI-2005-TN-005, Software Eng. Inst., Carnegie Mellon Univ., 2005.
8. C.B. Tayntor, Six Sigma Software Development, CRC Press, 2007.

Index Terms:
software process improvement, return on investment, value-based software engineering, Six Sigma, management commitment, benefit measurement
Citation:
Rini van Solingen, "A Follow-Up Reflection on Software Process Improvement ROI," IEEE Software, vol. 26, no. 5, pp. 77-79, Sept.-Oct. 2009, doi:10.1109/MS.2009.120
Usage of this product signifies your acceptance of the Terms of Use.