Critical success factors for software process improvement implementation: An empirical study

Software Process Improvement and Practice

Volumn 11, Issue 2, 2006, Pages 193-211

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

^a KEELE UNIVERSITY   (United Kingdom)

^b CSIRO   (Australia)

^c UNIVERSITY OF TECHNOLOGY SYDNEY   (Australia)

Author keywords

Critical success factors; Empirical study; Software process improvement

Indexed keywords

COMPUTER OPERATING PROCEDURES; COMPUTER PROGRAMMING; COMPUTER SCIENCE; INFORMATION SCIENCE; INFORMATION TECHNOLOGY; KNOWLEDGE ACQUISITION; PERSONNEL TRAINING;

CRITICAL SUCCESS FACTORS (CSF); EMPIRICAL STUDY; SOFTWARE PROCESS IMPROVEMENT (SPI); SPI IMPLEMENTATION METHODOLOGY;

SOFTWARE ENGINEERING;

EID: 33744790670     PISSN: 10774866     EISSN: 10991670     Source Type: Journal    
DOI: 10.1002/spip.261     Document Type: Article

References (88)

1. Baddoo N. 2001. Motivators and De-Motivators in software process improvement: an empirical study. PhD, University of Hertfordshire, Hertfordshire, UK.
2. Baddoo N, Hall T. 2002. Motivators of software process improvement: An analysis of practitioner's views. Journal of Systems and Software 62: 85-96.
3. Baddoo N, Hall T. 2003. De-Motivators of software process improvement: An analysis of practitioner's views. Journal of Systems and Software 66(1): 23-33.
4. Baddoo N, Hall T, Wilson D. 2000. Implementing a people focused SPI programme, 11th European Software Control And Metrics Conference and The Third SCOPE Conference on Software Product Quality.
5. Basili VR, McGarry FE, Pajerski R, Zelkowitz MV. 2002. Lessons learned from 25 years of process improvement: The rise and fall of the NASA software engineering laboratory. International Conference on Software Engineering. 69-79.
6. Billings C, Clifton J, Kolkhorst B, Lee E, Wingert W. 1994. Journey to a mature software process. IBM Systems Journal 33(1): 46-61.
7. Black T. 1999. Doing Qualitative Research in the Social Sciences: An Integrated Approach to Research Design, Measurement and Statistics. Sage: London.
8. Bullen CV, Rockart JF. 1981. A primer on critical success factor, Centre for information systems research. Sloan School of Management, Working Paper No. 69.
9. Burnard P. 1991. A method of analysing interview transcripts in qualitative research. Nurse Education Today 11:461-466.
10. Butler K. 1995. The economics benefits of software process improvement. CrossTalk July, 14-17.
11. Butler K. 1997. Process lessons learned while reaching Level 4. CrossTalk May, 1-4.
12. Coolican H. 1999. Research Methods and Statistics in Psychology. Hodder and Stoughton: London, UK.
13. Creswell J. 1994. Research Design: Qualitative and Quantitative Approaches. London, Sage.
14. Curtis B. 2000. The global pursuit of process maturity. IEEE Software: 17(4): 76-78.
15. Diaz M, Sligo J. 1997. How software process improvement helped Motorola. IEEE software 14(5): 75-81.
16. Dion R. 1992. Elements of a process-improvement program. IEEE Software: July, 83-85.
17. Dion R. 1993. Process improvement and the corporate balance sheet. IEEE Software 10(4): 28-35.
18. Dyba T. 2000. An instrument for measuring the key factors of success in SPI. Empirical Software Engineering 5: 357-390.
19. El-Emam K, Fusaro P, Smith B. 1999. Success Factors and Barriers for Software Process Improvement. Better Software Practice for Business Benefit: Principles and Experience. IEEE Computer Society.
20. Ferguson P, Leman G, Perini P, Renner S, Seshagiri G. 1999. Software process improvement works. Technical Report No, CMU/SEI-99-TR-027 Software Engineering Institute, USA.
21. Finkelstein A. 1993. Report of the Inquiry Into The London Ambulance Service. Report to the Communications Directorate, South West Thames. 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, 1993.
22. Fitzgerald B, O'Kane T. 1999. A longitudinal study of software process improvement. IEEE Software May/June 37-45.
23. Florence A. 2001. Lessons learned in attempting to achieve software CMM Level 4. CrossTalk August, 29-30.
24. Fowler P, Middlecoat B, Yo S. 1999. Lessons learned collaborating on a process for SPI at Xerox. Technical Report No. CMU/SEI-99-TR-006. Software Engineering Institute, USA.
25. Goldenson DR, Herbsleb JD. 1995. After the Appraisal: A Systematic Survey of Process Improvement, Its Benefits, And Factors That Influence Success. SEI: CMU/SEI-95-TR-009. Software Engineering Institute, USA.
26. Hall T, Beecham S, Rainer A. 2002a. Requirements problems in twelve software companies: An empirical analysis. IEE Proceedings-Software: August, 153-160.
27. Hall T, Rainer A, Baddoo N. 2002b. Implementing software process improvement: an empirical study. Software Process Improvement and Practice 7(1): 3-15.
28. Hall T, Wilson D. 1997. Views of software quality: a field report. IEEE Proceedings on Software Engineering 144(2): 111-118.
29. Hall T, Wilson D. 1998. Perceptions of software quality: a pilot study. Software Quality Journal 7: 67-75.
30. Harrison R, Baddoo N, Barry E, Biffl S, Parra A, Winter B, Wuest J. 1999. Directions and methodologies for empirical software engineering. Empirical Software Engineering 4(4): 405-410.
31. Herbsleb JD, Goldenson DR. 1996. A systematic survey of CMM experience and results. In 18th International Conference on Software Engineering (ICSE-18), Berlin Germany. 323-330.
32. Herbsleb J, Carleton A, Rozum J, Siegel J, Zubrow D. 1994. Benefits of CMM-based software process improvement: Initial results. Technical Report No. CMU/SEI-94-TR-013. Software Engineering Institute, USA.
33. Humphery WS, Synder TR, Willis RR. 1991. Software process improvement at Hughes aircraft. IEEE Software 8(4): 11-23.
34. Huotari M-L, Wilson TD. 2001. Determining organizational information needs: the critical success factors approach. Information Research 6(3). http://www.shef.ac.uk/~is/publications/infres/paper108.html:site visited 31-03-2006.
35. ISO-9000. 2004. International standard organization. http://www.iso.ch/ iso9000-14000/iso9000/iso9000. index, html site visited 23-02 2004.
36. Johnson A. 1994. Software process improvement experience in the DP/MIS function: Experience report. In IEEE International Conference on Software Engineering, ICSE. Sorrento, Italy 323-329.
37. Kaltio T, Kinnula A. 2000. Deploying the defined software process. Software Process-Improvement and Practice 5: 65-83.
38. Kautz K, Nielsen PA. 2000. Implementing software process improvement: Two cases of technology transfer. In Proceedings of the 33rd Hawaii Conference on System Sciences Maui, USA, 7, 1-10.
39. 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 Maui, USA.
40. 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.
41. Khasru BZ. 2001. Former Oxford health directors settle lawsuit. Fairfield County Business Journal: July, 5.
42. Krippendorf K. 1980. Content Analysis: An Introduction to its Methodologies. Sage: London.
43. Laporte C, Trudel S. 1998. Addressing the people issues of process improvement activities at Oerlikon aerospace. Software Process Improvement and Practice 4:187-198.
44. Leedy P, Ormrod J. 2001. Practical Research: Planning and Design. Prentice Hall: New Jersey, USA.
45. Lions JL. 1997. http://www.ima.umn.edu/~arnold/disasters/ariane5rep.html, site visited 4-3-2003.
46. 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).
47. McCabe GP, Moore DS. 2002. Introduction to the Practice of Statistics, 4th edn. W.H.Freeman and Co: New York.
48. Michael S, Lewis B. 1994. Research Practice: International Handbooks of Quantitative Application in Social Sciences. Sage: London.
49. Moitra D. 1998. Managing change for (SPI) initiatives: A practical experience-based approach. Software Process Improvement and Practice 4(4): 199-207.
50. 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), Los vegas, USA, 650-655.
51. Niazi M, Wilson D, Zowghi D. 2003a. Critical success factors and critical barriers for software process improvement: An analysis of literature. In The proceedings of the Australasian Conference on Information Systems (ACIS03), Perth Australia.
52. Niazi M, Wilson D, Zowghi D. 2003b. A model for the implementation of software process improvement: A pilot study. In The Proceedings of the Third International Conference on Software Quality (QSIC03). IEEE Computer Society: Dallas, USA 196-203.
53. Niazi M, Wilson D, Zowghi D. 2005a. A framework for assisting the design of effective software process improvement implementation strategies. Journal of Systems and Software 78(2): 204-222.
54. Niazi M, Wilson D, Zowghi D. 2005b. A maturity model for the implementation of software process improvement: An empirical study. Journal of Systems and Software 74(2): 155-172.
55. Niazi M, Wilson D, Zowghi D, Wong B. 2004. A model for the implementation of software process improvement: An empirical study. In Product Focused Software Process Improvement (Profes 2004), Japan, 1-16.
56. Nolan A. 1999. Learning from success. IEEE Software January/February, 97-105.
57. Paul B. 2002. On for young and old as James and Kerry began to fret. The Sydney morning herald, http://www.smh.com.au/articles/2002/03/20/Pbonetel.htm: Site visited 12-9-2003.
58. Paul O, Webb D. 1995. The race to level 3. CrossTalk.
59. 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, OR. 350-361.
60. Paulk M. 1999. Practices of high maturity organizations. In SEPG Conference. Atlanta, Georgia 1-25.
61. Paulk M, Curds B, Chrissis M, Weber C. 1993. Capability Maturity Model for Software Version 1.1. USA, Software Engineering Institute: CMU/SEI-93-TR-24.
62. Paulk M, Weber C, Curtis B, Chrissis M. 1994. A High Maturity Example: Space Shuttle Onboard Software, in the Capability Maturity Model: Guidelines for Improving Software Process. Addison wesley: CA, USA.
63. Pellow A, Wilson TD. 1993. The management information requirements of heads of university departments: a critical success factors approach. Journal of Information Science 19: 425-437.
64. Perry D, Porter A, Votta L. 2000. Empirical studies of software engineering: a roadmap. In Proceedings of the Twenty-second Conference on Software Engineering, Limerick, Ireland, 347-355.
65. Pitterman B. 2000. Telcordia technologies: The journey to high maturity. July/August IEEE Software 89-96.
66. Quenn E. 1997. My boss needs to hear this: How management can support SPI. CrossTalk May.
67. Rainer A, Hall T. 2002a. Key success factors for implementing software process improvement: a maturity-based analysis. Journal of Systems and Software 62(2): 71-84.
68. Rainer A, Hall T. 2002b. A quantitative and qualitative analysis of factors affecting software processes. Journal of Systems and Software Accepted awaiting publication.
69. Randell B. 1989. Airbus A320, The risks digest: Forum on risks to the public in computers and related systems 8(57). http://catless.ncl.ac.uk/Risks/8. 57.html, site visited 31-02-2006.
70. Reel J. 1999. Critical success factors in software projects. IEEE Software: May/June, 18-23.
71. Rifkin S. 2001. Why software process innovations are not adopted. IEEE Software: July/August, 110-111.
72. Rockart JF. 1979. Chief executives define their own data needs. Harvard Business Review March/April, (2): 81-93.
73. Scott JE. 1999. The FoxMeyer drugs' Bankruptcy: Was it a Failure of ERP? In Proceedings of the Association for Information Systems 5th Americas Conference on IS, Milwaukee, WI, August. 223-225.
74. Seaman C. 1999. Qualitative methods in empirical studies of software engineering. IEEE Transactions on Software Engineering 25(4): 557-572.
75. SEI. 2002. Capability Maturity Model® Integration (CMMISM), Version 1.1. SEI: CMU/SEI-2002-TR-029 Software Engineering Institute, USA.
76. 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, USA.
77. Sommerville I. 1996. Software Engineering, Fifth Edition, Addison Wesley.
78. Stelzer D, Werner M. 1999. Success factors of organizational change in software process improvement. Software Process Improvement and Practice 4(4).
79. Sweeney A, Bustard DW. 1997. Software process improvement: making it happen in practice. Software Quality Journal 6: 265-273.
80. The Royal Academy of Engineering. 2004. The Challenges of Complex IT Projects, The report of a working group from The Royal Academy of Engineering and The British Computer Society: ISBN 1-903496-15-2.
81. Tomsho R. 1994. Real dog: How greyhound lines re-engineered itself right into a deep hole. Wall Street Journal 20: A1-A6.
82. Weigers KE. 1998. Software process improvement: Eight traps to avoid. CrossTalk September, 9-12.
83. Westaway T. 1995. How we achieved level 3. Crosstalk May.
84. Willis RR, Rova RM, Scott MD, Johnson MI, Ryskowski JF, Moon JA, Shumate KC, Winfield TO. 1998. Hughes aircraft's widespread deployment of a continuously improving software process. Technical Report No. CMU/SEI-98-TR-006. Software Engineering Institute, USA.
85. Wohlwend H, Rosenbaum S. 1993. Software improvements in an international company. In International Conference on Software Engineering, Maryland, USA 212-220.
86. Wohlwend H, Rosenbaum S. 1994. Schlumberger's software improvement program. IEEE Transactions on Software Engineering 20(11): 833-839.
87. Yamamura G. 1999. Software process satisfied employees. IEEE Software September/October, 83-85.
88. Yamamura G, Wigle G. 1997. SEI CMM Level 5: For the right reasons. CrossTalk August.