The impact of Software Process Maturity on Software Project Performance: The Contingent Role of Software Development Risk
Keywords:Software process maturity, software development risk, software project performance
Despite growing efforts to improve software development processes, recurring concerns about software project performance remain largely present. The rate of software development project failure rate has been routinely documented in information systems (IS) research (Wallace, 2004; El-Masry and Rivard, 2010). The management of software development projects is often marked by inadequate planning, a poor grasp of the overall development process, and no clear management framework, even as the focus in software development shifts from a technology perspective to a more process-centric view (Slaughter, 2006). To address such concerns few CMM-based studies have examined the benefits and direct impact of software process maturity on software project performance but with mixed results. The present paper attempts to systematically examine the contingent role of software development risk on the impact of software process maturity level on software project performance. Guided by risk-based perspective in Software Engineering and CMM-based framework, an exploratory model was developed and tested. The premise of this paper is that software development risk plays a contingent role in the relationship between software process maturity and software project performance. Drawing on a sample of 107 organizations that have undergone official CMM appraisals, the results of partial least squares analysis of the data reveal initial evidence that (1) a positive effect of software process maturity level on software project performance while underscoring the negative effect of software development risk on software project performance, and (2) more importantly, the findings show that software development risk plays a contingent role software process maturity level on software project performance. For researchers, the integration of software development risk can provide a much needed linkage in the three fundamental constructs of CMM. From a managerial perspective, in order to foster a better software project performance, IS project leaders and managers should strongly emphasize devising effective software development risk assessment since a variation of this construct’s level may strengthen or weaken the relationship between software development process maturity and software project performance.
Aladwani, A.M. (2002), “An Integrated Performance Model of Information Systems Projects”, Journal of Management Information Systems, Vol 19, no 1, p. 185-210
Arrow, K.J. (1965), “Aspects of the Theory of Risk Bearing”, Yrjö Janssonin Säätiä, Helsinki, Finland.
Ashrafi, N. (2003), “The impact of software process improvement on quality: in theory and practice”
Information & Management, Vol. 40, no. 7, p. 677-690.
Bagozzi, R. P., J. R. Edwards, J.R. (1998), “A general approach for representing constructs in organizational research”, Organizational Research Methods, Vol. no. 1, p. 45-87.
Barki, H., Rivard, S., and Talbot, J. (1993), “Toward an Assessment of Software Development Risk,” Journal of Management Information Systems, Vol. 10, no. 2, p. 203-225.
Barki, H., Rivard, S., and Talbot, J. (2001), “An Integrative Contingency Model of Software Project Risk Management,” Journal of Management Information Systems, Vol. 17, no. 4, p. 37-69.
Boehm, B.W. (1991). “Software Risk Management”, Los Alamitos, CA: IEEE Computer Society Press.
Boehm, B.W. & Ross, R. (1989), “Theory-W Software Project Management: Principles and Examples,” IEEE Transactions on Software Engineering, Vol. 15, no. 7, p. 902-916.
Canfora, G., Garcìa, F., Piattini, M., Ruiz, F., & Visaggio, C.A.(2005), “A Family of Experiments to Validate Metrics for Software Process Models,” The Journal of Systems and Software ,Vol. 77, p. 113-129.
Cater-Steel, A. P., Tan, W. -G., & Toleman, M. A. (2006). “Challenge of adopting multiple
process improvement frameworks”, European Conference on Information Systems, Goteborg,
Sweden, 12–14 June, 2006.
Chen, L. 52010), “Business-IT alignment maturity of companies in China”, Informtion&Management, Vol. 47, no. 1, p. 9-16.
Chin, W.W. (1998), “Structural Equation Modeling in IS Research”, ISWorld Net Virtual Meeting Center at Temple University, [On-Line]. Available at http://www.interact.cis.temple.edu/~vmc.
Clark, B. (2000), “Quantifying the effects on effort of software process maturity”. IEEE Software Journal, Vol. 17, no. 6, p. 65-70.
Cooprider, J., & Henderson, J.A. (1991), “Technology-Process Fit: Perspectives on Achieving Prototyping Effectiveness,” Journal of Management Information Systems, Vol. 7, no. 3, p. 67-87.
Damian. D., & Chisan, J., (2006), “An Empirical Study of the Complex Relationships between Requirements Engineering Processes and Other Processes that Lead to Payoffs in Productivity”, IEEE Transactions on Software Engineering, Vol. 32, no. 7, p. 433 - 453.
Diaz, M. & Sligo, J. (1997), “How Software Process Improvement Helped Motorola”, IEEE Software,
Vol. 14, No. 5. p.
Dillman, D.A. (2000), “Mail and Internet Surveys: The Tailored Design Method”, Second Revision, John Wiley & Sons, 2000.
Dybå, T., Kitchenham, B. A. & Jorgensen, M. (2005), “Evidence-based software engineering for practitioners”, IEEE Software, Vol. 22, no. 1, p. 58-65.
Ebert C, Parro C H, Suttels R & Kolarczyk H. (2001), “Improving validation activities in a global software development”, IEEE Software, p. 545-554.
El Amrani, R & Saint-Léger, G. (2011), “Le pari des centres de competences dans la stabilization des organisations en phase post-projet ERP “, Systèmes d’Information et Management, Vol. 16, no. 1, p. 69-112.
El-Masri, M & Rivard, S. (2010), “Specifying the Software Project Risk Construct”, AMCIS 2010, Lima, Perou.
Fitzgerald, B. & O’Kane, T. (1999), “A Longitudinal Study of Software Process Improvement,” IEEE Software, Vol. 16, no. 3, p. 37-45.
Fornell C & Larcker D. (1981), “Evaluating structural equation models with unobserved variables and measurement error,” Journal of Marketing Research, Vol. 18, p. 39-50.
Guinan, P.J., Cooprider, J.G., & Faraj, S. (1998), "Enabling Software Development Team Performance
During Requirements Definition: A Behavioral Versus Technical Approach," Information Systems Research, Vol. 9, no. 2, p 101-125.
Hair, J.F., Anderson, R.L., Tatham, R.L., Black, W.C. (1998), Multivariate Data Analysis, Prentice Hall.
Harter, D.E., Krishnan, M.S., & Slaughter, S.A. (2000), “Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development,” Management Science (Vol. 46, no. 4, p. 451-466.
Harter, D., & Slaughter. S. (2003), “Quality improvement and infrastructure activity costs in software
Development”. Management Science, Vol. 49, no. 6, p. 784-796.
Herbsleb, J., Carleton, A., Rozum, J., Siegel, J., & Zubrow, D. (1994), “Benefits of CMM-Based Software Process Improvement: Initial Results,” Technical Report CMU/SEI-94-TR-13, Software Engineering Institute, p. 1-64.
Herbsleb, J., & Goldenson, D.R. (1996), “A Systematic Survey of CMM Experience and Results,” Proceedings of International Conference on Software Engineering, Berlin, p. 25-30.
Herbsleb, J., Zubrow, D., Goldenson, D., Hayes, W., & Paulk, M. (1997), “Software Quality and the Capability Maturity Model,” Communications of the ACM, Vol. 40, no. 6, p. 30-40.
Huang, S. & Han, W. (2006), “Selection priority of process areas based on CMMI continuous representation”, Information & Management, Vol. 43, no. 3, p. 297-307.
Iacovou, C. & Nakatsu, R. (2008), “A risk profile of offshore outsourced development projects”, Communications of ACM, Vol. 51, no. 6, p. 89-94.
Ibbs, C.W., & Kwak, Y.H. (2000), “Assessing Project Management Maturity,” Project Management Journal, Vol. 31, no. 1, p. 32-43.
Ingalsbe, J., Shoemaker, D., & Jovanovic, V. (2001), “A Metamodel for the Capability Maturity Model for Software,” Seventh Americas Conference on Information Systems, p. 1305-1313.
Iversen, J.H., Mathiassen, L., & Nielsen, P.A. (2004), “Managing Risk in Software Process Improvement: An Action Research Approach,” MIS Quarterly, Vol. 28, no. 3, p. 395-433.
Iversen, J.H. & Ngwenyama, O. (2006), “Problems in Measuring Effectiveness in Software Process Improvement: A Longitudinal Study of Organizational Change at Danske Data,” International Journal of Information Management ,Vol. 26, p. 30-43.
Jalote, P. (2000), CMM in Practice: Processes for Executing Software Projects at InfoSys, Reading, Mass: Addison-Wesley.
Jiang, J.J., Klein, G., Hwang, H.G., Huang, J., & Hung, S.Y.(2004), “An Exploration of the Relationship between Software Development Process Maturity and Project Performance,” Information & Management Vol. 41, p. 279-288.
Jung, H & Goldenson, D. (2009), “Evaluating the relationship between process improvement and schedule deviation in software maintenance,” Information and Software Technology, Vol. 51, p. 351-361.
Krishnan, M. S., C. H. Kriebel, S. Kekre, T. Mukhopadhyay. (2000), “An empirical analysis of productivity and quality in software products”, Management Science. Vol. 46, no. 6, p. 745–759.
Krishnan, M. S. & Kellner, M. (1999). "Measuring Process Consistency: Implications for Reducing Software Defects." IEEE Transactions on Software Engineering, Vol. 25, no. 6, p. 800-815.
Lawlis, P.K., Flowe, R.M., & Thordahl, J.B. (1995), “A Correlational Study of the CMM and Software Development Performance,” Cross Talk, p. 21-25.
Lesca, N & Caron-Fasan, M-L. (2008), “Facteurs d’échec et d’abandon d’un projet de veille stratégique: retour d’expériences“, Systèmes d’Information et Management, Vol. 13, no. 3. p. 17-42.
Lyytinen, K., Mathiassen, L., & Ropponen, J. (1998), “Attention Shaping and Software Risk- A Categorical Analysis of Four Classical Risk Management Approaches,” Information Systems Research, Vol. 9, no. 3, p. 233-255.
March, J.G. & Shapira, Z. (1987), “Managerial Perspectives on Risk and Risk Taking,” Management Science, Vol. 33, no. 11, p.1404-1418.
Myers, W. (1994), “Hard data will lead managers to quality,” IEEE Software (Vol. 11, no. 2, p. 100-101.
Na, K.S., Li, X., Simpson, J.T., & Kim, K.Y., (2004), “Uncertainty Profile and Software Project Performance: A Cross-National Comparison”, The Journal of Systems and Software, Vol. 70, no. 2, p. 155-163.
Nidumolu, S., (1996), “A Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination in Software Development Projects”, Journal of Management Information Systems, Vol. 13, no. 2, p. 77-113
Nidumolu, S. (1995), “The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable,” Information Systems Research, Vol. 6, no. 3, p.191-219.
Nunnally, J.C., 1978. Psychometric Theory, McGraw-Hill, NY.
Paulish, D., J. & A. D. Carleton. (1994). “Case Studies Of Software-Process-Improvement
Measurement.” IEEE Computer, Vol. 27, no. 9, p. 50-57.
Paulk, M., Curtis, B., Chrissis, M. B. & Weber, C. (1993), “Capability Maturity Model for Software, Version 1.1,” CMU/SEI-93-TR-024, Software Engineering Institute, Pittsburgh, PA, p. 1-82.
Paulk, M., Weber, C., Curtis, B. & Chrissis, M. B. (1995), “The Capability Maturity Model for Software: Guidelines for Improving the Software Process”, Addison-Wesley.
Poeppelbuss, J., Niehaves, B., Simons, A., and Becker, J. (2011), “Maturity Models in Information Systems Research: Literature Search and Analysis”, Communications of the Association for Information Systems, Vol. 29, no. 27, p. 505-532.
Post, G.V., & Diltz, D.J. (1986), “A Stochastic Dominance Approach to Risk Analysis of Computer Systems,” MIS Quarterly, Vol. 10, no. 4, p. 363-375.
Rai, A. & Al-Hindi, H. (2000), “The Effects of Development Process Modeling and Task Uncertainty on Development Quality Performance,” Information & Management, Vol. 37, no. 6, p. 335-346.
Ravichandran, T., & Rai, A. (2000), “Quality Management in Systems Development: An Organizational System Perspective,” MIS Quarterly, Vol. 24, no. 3, p. 38 1-416.
Rivard, S., Huff, S. (1988), “Factors of Success for End-User Computing”, Communications of ACM, Vol. 31, no. 5, p. 552-561
Rivard, S & Mignerat, M. (2010), “Between Aquiescence and Manipulation: IS Project Managers Responses to Institutionalized Practices”, Systèmes d’Information et Management, Vol. 15,no. 2, p. 9-44.
Robey, D., Smith, L.A., & Vijayasarathy, L.R., (1993), “Perceptions of Conflict and Success in Information Systems Development Projects”, Journal of Management Information Systems, Vol. 10, no. 1, p. 123-139.
Ropponen, J. & Lyytinen, K. (2000), “Components of software development risk: how to address them”, IEEE Transactions on Software Engineering, Vol. 26, no. 2, p. 98-112.
Sauer, C., Gemino, A. & Reich, B. (2007), “The impact of size and volatility on IT project performance”, Communications of the ACM, Vol. 50, no. 11, p. 79-84.
Schalken, J. J. P., Brinkkemper, S., & van Vliet, H. (2006). “A method to draw lessons from project postmortem databases”. Software. Process Improvement. Practices., p. 35–46.
Schmidt, R., Lyytinen, K., Keil, M., & Cule, P. (2001), “Identifying Software Project Risks: An International Delphi Study,” Journal of Management Information Systems, Vol. 17, no. 4, p. 5-36.
Shih, C. and Huang, S. (2010), “Exploring the relationship between organizational culture and Software Process Improvement Deployment”, Information & Management,
Slaughter, S., Levine, L., Ramesh, R., Pries-Heje, J. (2006), “Aligning software processes and strategy”, MIS Quarterly, Vol. 30, no. 4,2, p. 891-918.
Spears, J. L., & Barki, H. (2010), “User Participation in Information Systems Security Risk Management,” MIS Quarterly, Vol. 34, no. 3, p. 503-522.
Staples , M., Niazi , M., Jeffery, R., Abrahams , A., Byatt, P., Murphy, R. (2007), “An exploratory study of why organizations do not adopt CMMI”, Journal of Systems and Software, Vol. 80, no. 6, p. 883-895.
Subramanian, G; Jiang, J; Klein, G. (2007), “Software quality and IS project performance improvements from software development process maturity and IS implementation strategies”. The Journal of Systems and Software, Vol. 80, p. 616-627.
The Standish Group. The Standish Group Research Report. 2009. www.standishgroup.com
Trienekens J., Kusters, R. & van Solingen, R. (2001), “Product focused software process improvement: concepts and experiences from industry”, Software Quality Journal, Vol. 9, p. 269–281.
Unterkalmsteiner, M; Gorschek, T; Islam, A; Cheng, C; Permadi, R and Feldt, R. (2012), "Evaluation and Measurement of Software Process Improvement - A Systematic Literature Review", IEEE Transactions on Software Engineering, Vol. 38, no. 2, p. 398-482.
Venkatraman, N. (1989), “The concept of fit in strategy research: toward verbal and statistical correspondence”, Academy of Management Review, Vol. 9, p. 513- 525.
Wallace, L., Keil, M., Rai, A. (2004), “How Software Project Risk Affects Project Performance: An Investigation of the Dimensions of Risk and an Exploratory Model”, Decision Sciences, Vol. 35, no. 2, p. 289-321.
Wang, E., Ju, P., Jiang, J., Klein, G. (2008), “The effects of change control and management review on software flexibility and project performance”. Information & Management, Vol. 45, no. 7, p. 438-443
Yates, J.F. (1992). Risk Taking Behavior, Wiley, Chichester.
The author bears the responsibility for checking whether material submitted is subject to copyright or ownership rights (e.g. figures, tables, photographs, illustrations, trade literature and data). The author will need to obtain permission to reproduce any such items, and include these permissions with their final submission.
It is our policy to ask all contributors to transfer for free the copyright in their contribution to the journal owner. There are two broad reasons for this:
- ownership of copyright by the journal owner facilitates international protection against infringement of copyright, libel or plagiarism;
- it also ensures that requests by third parties to reprint or reproduce a contribution, or part of it, in either print or electronic form, are handled efficiently in accordance with our general policy which encourages dissemination of knowledge within the framework of copyright.
In conformity with the French law, the author keeps the 'moral rights' related to the article:
- The 'authorship right': It is the author's right to have his name associated with each publication and exploitation of the article.
- The 'integrity right': It can be claimed by the author if he finds that during an exploitation, his work has been distorted (cutting, reassembly...).