A maturity model for the implementation of software process improvement: An empirical study

Journal of Systems and Software

Volumn 74, Issue 2 SPEC. ISS., 2005, Pages 155-172

  Niazi, Mahmood ^a   Wilson, David ^a   Zowghi, Didar ^a  

^a UNIVERSITY OF TECHNOLOGY SYDNEY   (Australia)

Author keywords

CMMI; Critical success factors; Software process improvement implementation

Indexed keywords

INFORMATION TECHNOLOGY; PLANNING; PROCESS ENGINEERING; PROJECT MANAGEMENT; SOCIETIES AND INSTITUTIONS; STANDARDS;

CMMI; CRITICAL SUCCESS FACTORS (CSF); SOFTWARE PROCESS IMPROVEMENT IMPLEMENTATION;

SOFTWARE ENGINEERING;

EID: 6444239461     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2003.10.017     Document Type: Article

References (92)

1. Baddoo, N., 2001. Motivators and de-motivators in software process improvement: an empirical study. PhD, University of Hertfordshire, UK.
2. Baddoo N., Hall T. Motivators of software process improvement: an analysis of practitioner's views. Journal of Systems and Software. (62):2002;85-96.
3. Baddoo N., Hall T. De-motivators of software process improvement: an analysis of practitioner's views. Journal of Systems and Software. 66(1):2003;23-33.
4. Baddoo, N., Hall, T., Wilson, D., 2000. Implementing a people focused SPI programme. In: 11th European Software Control and Metrics Conference and the Third SCOPE Conference on Software Product Quality.
5. Basili, V.R., McGarry, F.E., Pajerski, R., Zelkowitz, M.V., 2002. Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory. In: International Conference on Software Engineering. pp. 69-79.
6. Beecham, S., Hall, T., 2003. Expert panel questionnaire: validating a requirements process improvement model. http://homepages.feis.herts.ac.uk/~pppgroup/requirements_cmm.htm, visited May 2003.
7. Beecham, S., Hall, T., Rainer, A., 2003. Building a requirements process improvement model. Department of Computer Science, University of Hertfordshire, Technical Report No. 378.
8. Billings C., Clifton J., Kolkhorst B., Lee E., Wingert W. Journey to a mature software process. IBM Systems Journal. 33(1):1994;46-61.
9. Black T. Doing Qualitative Research in the Social Sciences: An Integrated Approach to Research Design, Measurement and Statistics. 1999;Sage.
10. Bullen, C.V., Rockart, J.F., 1981. A primer on critical success factor. Centre for Information Systems research, Sloan School of Management, Working Paper No. 69.
11. Burnard P. A method of analysing interview transcripts in qualitative research. Nurse Education Today. (11):1991;461-466.
12. Butler K. The economics benefits of software process improvement. CrossTalk. (July):1995;14-17.
13. Butler K. Process lessons learned while reaching level 4. CrossTalk. (May):1997;1-6.
14. Coolican H. Research Methods and Statistics in Psychology. 1999;Hodder and Stoughton, London.
15. Creswell J. Research Design: Qualitative and Quantitative Approaches. 1994;Sage.
16. Crosby P. Philip Crosby's Reflections on Quality. 1996;McGraw-Hill.
17. Curtis B. The global pursuit of process maturity. IEEE Software. (July-August):2000;76-78.
18. Daskalantonakis M.K. Achieving higher SEI levels. IEEE Software. 11(4):1994;17-24.
19. Diaz M., Sligo J. How software process improvement helped motorola. IEEE Software. 14(5):1997;75-81.
20. Dion R. Elements of a process-improvement program. IEEE Software. (July):1992;83-85.
21. Dion R. Process improvement and the corporate balance sheet. IEEE Software. 10(4):1993;28-35.
22. Dyba T. An instrument for measuring the key factors of success in SPI. Empirical Software Engineering. (5):2000;357-390.
23. El-Emam K., Fusaro P., Smith B. Success factors and barriers for software process improvement. Better software practice for business benefit: principles and experience. IEEE Computer Society. 1999.
24. Ferguson, P., Leman, G., Perini, P., Renner, S., Seshagiri, G., 1999. Software process improvement works. Technical Report, CMU/SEI-99-TR-027.
25. Finkelstein, A., 1993. Report of the inquiry into the London ambulance service. In: International Workshop on Software Specification and Design Case Study Electronic. http://www.cs.ucl.ac.uk/staff/A.Finkelstein/las/lascase0.9.pdf, site visited 4-3-2003.
26. Fitzgerald B., O'Kane T. A longitudinal study of software process improvement. IEEE Software. (May-June):1999;37-45.
27. Florence A. Lessons learned in attempting to achieve software CMM level 4. CrossTalk. (August):2001;29-30.
28. Fowler, P., Middlecoat, B., Yo, S., 1999. Lessons learned collaborating on a process for SPI at Xerox. Technical Report, CMU/SEI-99-TR-006.
29. Goldenson, D.R., Herbsleb, J.D., 1995. After the appraisal: a systematic survey of process improvement, its benefits, and factors that influence success. SEI, CMU/SEI-95-TR-009.
30. Hall T., Wilson D. Views of software quality: a field report. IEEE Proceedings on Software Engineering. 144(2):1997.
31. Hall T., Wilson D. Perceptions of software quality: a pilot study. Software Quality Journal. (7):1998;67-75.
32. Hall T., Beecham S., Rainer A. Requirements problems in twelve software companies: an empirical analysis. IEE Proceedings - Software. (August):2002.
33. Hall T., Rainer A., Baddoo N. Implementing software process improvement: an empirical study. Software Process Improvement and Practice. 7(1):2002;3-15.
34. Harrison R., Baddoo N., Barry E., Biffl S., Parra A., Winter B., Wuest J. Directions and methodologies for empirical software engineering. Empirical Software Engineering. 4(4):1999;405-410.
35. Herbsleb, J.D., Goldenson, D.R., 1996. A systematic survey of CMM experience and results. In: 18th International Conference on Software Engineering (ICSE-18), Germany.
36. Herbsleb, J., Caarleton, A., Rozum, J., Siegel, J., Zubrow, D., 1994. Benefits of CMM-based software process improvement: initial results. Technical Report, CMU/SEI-94-TR-013.
37. Humphrey W.S. Managing the Software Process. 1989;Addison-Wesley.
38. Humphrey W. A Discipline for Software Engineering. 1995;Addison-Wesley.
39. Humphery W.S., Synder T.R., Willis R.R. Software process improvement at Hughes aircraft. IEEE Software. 8(July):1991;11-23.
40. Huotari M.L., Wilson T.D. Determining organizational information needs: the critical success factors approach. Information Research. 6(3):2001.
41. ISO/DIS-9241-11, 1994. International Standards Organization, ISO DIS 9241-11: Guidance on Usability.
42. ISO/IEC-15504, 1998. Information technology - software process assessment. Technical Report - Type 2.
43. Johnson, A., 1994. Software process improvement experience in the DP/MIS function: experience report. In: IEEE International Conference on Software Engineering, ICSE. pp. 323-329.
44. Kaltio T., Kinnula A. Deploying the defined software process. Software Process Improvement and Practice. (5):2000;65-83.
45. Kautz, K., Nielsen, P.A., 2000. Implementing software process improvement: two cases of technology transfer. In: Proceedings of the 33rd Hawaii Conference on System Sciences.
46. Khandelwal, V., Ferguson, J., 1999. Critical success factors and the growth of IT in selected geographic regions. In: 32nd Hawaii International Conference on System Sciences.
47. Khandelwal, V., Natarajan, R., 2002. Quality IT management in Australia: critical success factors for 2002. Technical Report No. CIT/1/2002, University of Western Sydney.
48. Krippendorf K. Content Analysis: An Introduction to its Methodologies. 1980;Sage, London.
49. Laporte C., Trudel S. Addressing the people issues of process improvement activities at Oerlikon Aerospace. Software Process Improvement and Practice. (4):1998;187-198.
50. Leung H. Slow change of information system development practice. Software Quality Journal. 8(3):1999;197-210.
51. Lions, J.L., 1997. http://www.ima.umn.edu/~arnold/disasters/ariane5rep.html, site visited 4-3-2003.
52. Macfarlane, M., 1996. Eating the elephant one bite at a time: effective implementation of ISO 9001/TickIT. Executive Digest - The ISO 9000 Quality Management System, August.
53. McDermid J., Bennet K. Software engineering research: a critical appraisal. IEE Proceedings on Software Engineering. 146(4):1999;179-186.
54. Michael S., Lewis B. Research Practice: International Handbooks of Quantitative Application in Social Sciences. 1994;Sage.
55. Moitra D. Managing change for (SPI) initiatives: a practical experience-based approach. Software Process Improvement and Practice. (4):1998;199-207.
56. Niazi, M., Wilson, D., 2003. A maturity model for the implementation of software process improvement. In: International Conference on Software Engineering Research and Practice (SERP03). pp. 650-655.
57. Niazi, M., Wilson, D., Zowghi, D., 2003. A framework for guiding the design of effective implementation strategies for software process improvement. In: International Conference on Knowledge Engineering and Software Engineering (SEKE 03). pp. 366-371.
58. Nolan A. Learning from success. IEEE Software. (January-February):1999;97-105.
59. Paul O., Webb D. The race to level 3. CrossTalk. (June):1995.
60. Paulish D., Carleton A. Case studies of software process-improvement measurement. IEEE Computer. 27(9):1994;50-57.
61. Paulk, M., 1998. Using the software CMM in small organizations. In: The Joint 1998 Proceedings of the Pacific Northwest Software Quality Conference and the Eighth International Conference on Software Quality, Portland. pp. 350-361.
62. Paulk, M., 1999. Practices of high maturity organizations. In: SEPG Conference. pp. 8-11.
63. Paulk, M., Curtis, B., Chrissis, M., Weber, C., 1993. Capability Maturity Model for software, Version 1.1. CMU/SEI-93-TR-24, Software Engineering Institute, USA.
64. Paulk M., Weber C., Curtis B., Chrissis M. A High Maturity Example: Space Shuttle Onboard Software, in the Capability Maturity Model: Guidelines for Improving Software Process. 1994;Addison-Wesley.
65. Pellow A., Wilson T.D. The management information requirements of heads of university departments: a critical success factors approach. Journal of Information Science. (19):1993;425-437.
66. Perry, D., Porter, A., Votta, L., 2000. Empirical studies of software engineering: a roadmap. In: Proceedings of the 22nd Conference on Software Engineering, Ireland. pp. 347-355.
67. Pitterman B. Telcordia technologies: the journey to high maturity. IEEE Software. (July-August):2000;89-96.
68. Quenn E. My boss needs to hear this: How management can support SPI. CrossTalk. (May):1997.
69. Rainer A., Hall T. Key success factors for implementing software process improvement: a maturity-based analysis. Journal of Systems and Software. (62):2002;71-84.
70. Rainer A., Hall T. A quantitative and qualitative analysis of factors affecting software processes. Journal of Systems and Software. 66(1):2003;7-21.
71. Randell, B. 1989. Airbus A320. The Risks Digest: Forum on Risks to the Public in Computers and Related Systems 8(57).
72. Reel J. Critical success factors in software projects. IEEE Software. (May-June):1999;18-23.
73. Rifkin S. Why software process innovations are not adopted. IEEE Software. (July-August):2001;110-111.
74. Rockart J.F. Chief executives define their own data needs. Harvard Business Review. (2):1979;81-93.
75. Seaman C. Qualitative methods in empirical studies of software engineering. IEEE Transactions on Software Engineering. 25(4):1999;557-572.
76. SEI, 2002. Capability Maturity Model® Integration (CMMISM), Version 1.1. SEI, CMU/SEI-2002-TR-029.
77. Somers, T., Nelson, K., 2001. The impact of critical success factors across the stages of enterprise resource planning implementations. In: 34th Hawaii International Conference on System Sciences.
78. Sommerville I., Sawyer P., Viller S. Requirements process improvement through the phased introduction of good practice. Software Process Improvement and Practice. (3):1997;19-34.
79. Sommerville, I., Sawyer, P., Viller, S., 1998. Improving the requirements process. In: Fourth International Workshop on Requirements Engineering: Foundation of Software Quality. pp. 71-84.
80. Standish Group., 1995. Chaos - the state of the software industry. Standish group international, Technical Report. pp. 1-11.
81. Stelzer D., Werner M. Success factors of organizational change in software process improvement. Software Process Improvement and Practice. 4(4):1999.
82. Sweeney A., Bustard D.W. Software process improvement: making it happen in practice. Software Quality Journal. (6):1997;265-273.
83. Tyran C., George J. The implementation of expert systems: a survey of successful implementation. Database. (Winter):1993;5-15.
84. Weigers K.E. Software process improvement: eight traps to avoid. CrossTalk. (September):1998;9-12.
85. Westaway T. How we achieved level 3. Crosstalk. (May):1995.
86. Whitten J., Bentley L., Dittman K. Systems analysis and design method. fifth ed. 2001;McGraw-Hill Companies Inc.
87. Willis, R.R., Rova, R.M., Scott, M.D., Johnson, M.I., Ryskowski, J.F., Moon, J.A., Shumate, K.C., Winfield, T.O., 1998. Hughes aircraft's widespread deployment of a continuously improving software process. Technical Report, CMU/SEI-98-TR-006.
88. Wohlwend, H., Rosenbaum, S. 1993. Software improvements in an international company. In: International Conference on Software Engineering. pp. 212-220.
89. Wohlwend H., Rosenbaum S. Schlumberger's software improvement program. IEEE Transactions on Software Engineering. 20(11):1994;833-839.
90. Yamamura G. Software process satisfied employees. IEEE Software. (September-October):1999;83-85.
91. Yamamura G., Wigle G. SEI CMM level 5: for the right reasons. CrossTalk. 1997.
92. Zubrow, D., Hayes, W., Siegel, J., Goldenson, D., 1994. Maturity Questionnaire. CMU/SEI-94-SR-7.