Benefits of CMM-Based Software Process Improvement: Initial Results

Abstract : Data from 13 organizations were collected and analyzed to obtain information on the results of CMM-based software process improvement efforts. We report the cost and business value of improvement efforts, as well as the yearly improvement in productivity, early defect detection, time to market, and post- release defect reports. Improvement efforts and results in five organizations are reported in more depth in case studies. In addition, technical issues that we confronted as we tried to measure the results of software process improvement are discussed. We end with conclusions about the results of SPI efforts. Business value, Defect prevention, Capability maturity model for software, Productivity, Case studies, Software process improvement

[1]  Victor R. Basili,et al.  A Methodology for Collecting Valid Software Engineering Data , 1984, IEEE Transactions on Software Engineering.

[2]  James A. Rozum.  Concepts on Measuring the Benefits of Software Process Improvements , 1993 .

[3]  Watts S. Humphrey,et al.  A method for assessing the software engineering capability of contractors , 1987 .

[4]  Susan Rosenbaum,et al.  Software improvements in an international company , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[5]  Norman E. Fenton,et al.  How effective are software engineering methods? , 1993, J. Syst. Softw..

[6]  Shari Lawrence Pfleeger,et al.  Software Metrics , 1991 .

[7]  R. Kaplan,et al.  The balanced scorecard--measures that drive performance. , 2015, Harvard business review.

[8]  Chan S. Park,et al.  Advanced engineering economics , 1990 .

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

[10]  Victor R. Basili,et al.  Paradigms for experimentation and empirical studies in software engineering , 1991 .

[11]  William A. Florac.  Software Quality Measurement: A Framework for Counting Problems and Defects , 1992 .

[12]  Robert B. Grady,et al.  Practical Software Metrics for Project Management and Process Improvement , 1992 .

[13]  L. Delbeke.  Quasi-experimentation - design and analysis issues for field settings - cook,td, campbell,dt , 1980 .

[14]  Suzanne Garcia,et al.  Key Practices of the Capability Maturity Model, Version 1.1 , 1993 .

[15]  Mark C. Paulk,et al.  The Capability Maturity Model , 1991 .

[16]  R. Kaplan,et al.  PUTTING THE BALANCED SCORECARD TO WORK , 1993 .

[17]  Robert E. Park,et al.  Software Size Measurement: A Framework for Counting Source Statements , 1992 .

[18]  Elizabeth K. Bailey,et al.  Software Measurement for DoD Systems: Recommendations for Initial Core Measures. , 1992 .

[19]  Barbara A. Kitchenham,et al.  Critical review of quantitative assessment , 1994, Softw. Eng. J..

[20]  Elizabeth K. Bailey,et al.  Software Effort and Schedule Measurement: A Framework for Counting Staff-Hours and Reporting Schedule Information , 1992 .

[21]  John H. Baumert,et al.  Software Measures and the Capability Maturity Model , 1992 .

[22]  B. Farber.  The Human Element , 1988 .

[23]  W. Edwards Deming,et al.  Out of the Crisis , 1982 .

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

[25]  Michael J. Flaherty,et al.  Review of Practical software metrics for project management and process improvement by Robert B. Grady, Prentice Hall, Englewood Cliffs 1992 , 1993 .

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

[27]  Victor R. Basili,et al.  Experimental Software Engineering Issues: Critical Assessment and Future Directions , 1993, Lecture Notes in Computer Science.

[28]  T. Cook,et al.  Quasi-experimentation: Design & analysis issues for field settings , 1979 .

[29]  Norman E. Fenton,et al.  Software Metrics: A Rigorous Approach , 1991 .