Uncertainty profile and software project performance: A cross-national comparison

Journal of Systems and Software

Volumn 70, Issue 1-2, 2004, Pages 155-163

  Na, Kwan Sik ^a   Xiaotong, Li ^b   Simpson, James T ^b   Kim, Ki Yoon ^c  

^a Seowon University   (South Korea)

^b UNIVERSITY OF ALABAMA IN HUNTSVILLE   (United States)

^c Kwangwoon University   (South Korea)

Author keywords

Capability maturity model; Project uncertainty profile; Requirement uncertainty analysis; Software development standards; Software project performance

Indexed keywords

BAGGAGE HANDLING; EMPLOYMENT; INTERNET; PERSONNEL; PROJECT MANAGEMENT; REQUIREMENTS ENGINEERING; RISK MANAGEMENT; SOCIETIES AND INSTITUTIONS; STANDARDIZATION; SYSTEMS ENGINEERING; UNCERTAIN SYSTEMS;

CAPABILITY MATURITY MODEL (CMM); INFORMATION SYSTEMS (IS);

SOFTWARE ENGINEERING;

EID: 0346154888     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0164-1212(03)00014-1     Document Type: Article

References (34)

1. Andres H., Zmud R. A contingency approach to software project coordination. Journal of Management Information Systems. 18(3):2002;41-70.
2. Barki H., Rivard S., Talbot J. Toward an assessment of software development risk. Journal of Management Information Systems. 10(2):1993;203-225.
3. Boehm B. Software risk management: Principles and practices. IEEE Software. 8(1):1991;32-41.
4. Chittister C., Haimes Y. Assessment and management of software technical risk. IEEE Transactions on Systems, Man, and Cybernetics. 24(2):1994;187-202.
5. Chittister C., Haimes Y. System integration via software risk management. IEEE Transactions on Systems, Man, and Cybernetics. 26(5):1996;521-532.
6. Fairley R. Risk management for software projects. IEEE Software. 11(3):1994;57-67.
7. Genuchten M. Why is software late? An empirical study of the reason for delay in software development. IEEE Transactions on Software Engineering. 17(6):1991;582-590.
8. Gibbs W. Software's chronic crisis. Scientific American. 271(3):1994;86-95.
9. Glass R. Software runaways - some surprising findings. The DATABASE for Advances in Information Systems. 28(3):1997;16-19.
10. Henderson J., Lee S. Managing I/S design teams: a control theories perspective. Management Science. 38(6):1992;757-777.
11. Jiang J., Klein G. Software development risks to project effectiveness. The Journal of Systems and Software. 52:2000;3-10.
12. Jiang J., et al. Reducing user-related risks during and prior to system development. International Journal of Project Management. 20:2002;507-515.
13. Keil M., et al. A cross-cultural study on escalation of commitment behavior in software projects. MIS Quarterly. 24(2):2000;299-325.
14. Keil M., Robey D. Blowing the whistle on troubled software projects. Communications of the ACM. 44(4):2001;87-93.
15. Keil M., Tiwana A., Bush A. Reconciling user and project manager perceptions of IT project risk: a Delphi study. Information Systems Journal. 12(2):2002;103.
16. Kitchenham B., Linkman S. Estimates, uncertainty and risk. IEEE Software Magazine. (May/June):1997;69-74.
17. Lee S. Net giants target Korea. Business Korea. 16:1999;7.
18. Meyer A., Loch C., Pich M. Managing project uncertainty: from variation to chaos. Sloan Management Review. 2002;60-67.
19. Moymhan T. How experienced project managers assess risk. IEEE Software. 14(3):1997;35-41.
20. Montealegre R., Keil M. De-escalating information technology projects: lessons from the Denver International Airport. MIS Quarterly. 24(3):2000;417-447.
21. Na, K., 1999. Software quality policy for improving competitiveness in Korea software firms. Government Report, Korea Ministry of Information and Communication.
22. Nidumolu S. The effect of coordination and uncertainty on software project performance: residual risk as an international variable. Information System Research. 6(3):1995;191-219.
23. Nidumolu S. A comparison of the structural contingency and risk-based perspectives on coordination in software-development projects. Journal of Management Information Systems. 13(2):1996;77-113.
24. Nidumolu S. Standardization, requirements uncertainty and software project performance. Information & Management. 31:1996;135-150.
25. Paulk M., et al. The Capability Maturity Model: Guidelines for Improving Software Process. 1995;Addison-Wesley Publishing.
26. Paulk M. Extreme programming from a CMM perspective. IEEE Software. 18(6):2001;1-8.
27. Ropponen J. Software Risk Management - Foundations, Principles and Empirical Findings. 1999;Jyvaskyla University Printing House.
28. Schmidt R., et al. Identifying software project risks: an international Delphi study. Journal of Management Information Systems. 17(4):2001;5-36.
29. SEI, 1998. Process Maturity profile of the Software Community 1998 Mid Year Update. Software Engineering Institute, Carnegie Mellon University.
30. SEI, 2002. Process Maturity profile of the Software Community 2001 Year End Update. Software Engineering Institute, Carnegie Mellon University.
31. Smith H., et al. Keeping mum as the project goes under: towards and explanatory model. Journal of Management Information Systems. 18(2):2001;189-228.
32. Thomas G., Smith S. Using structured benchmarking to fast-track CMM process improvement. IEEE Software. (September/October):2001;48-52.
33. Zhang P., et al. Predicting information technology project escalation: a neural network approach. European Journal of Operational Research. 146(1):2003;115-129.
34. Zmud R. Management of large software development efforts. MIS Quarterly. 4(2):1980;45-55.