Mark Keil
- 1 Alter, S. and Ginzberg, M. Managing uncertainty in MIS implementation. Sloan Manage. Rev. 20, 1 (1978), 23-31.]]Google Scholar
- 2 Barki, H., Rivard, S., and Talbot, J. Toward an Assessment of Software Development Risk.J. Manage. Info. Syst. 10, 2 (1993), 203-225.]] Google ScholarDigital Library
- 3 Boehm, B. and Ross, R. Theory-W software project management: principles and examples. IEEE Trans. Softw. Eng. 15, 7 (1989), 902-916.]] Google ScholarDigital Library
- 4 Boehm, B.W. Software Risk Management: Principles and Practices. IEEE Softw. 8, 1 (1991), 32-41.]] Google ScholarDigital Library
- 5 Charette, R.N. Software Engineering Risk Analysis and Management. Intertext, New York, 1989.]] Google ScholarDigital Library
- 6 Johnson, j. Chaos: The dollar drain of IT project failures. Applic. Den. Trends 2, 1 (1995), 41-47.]]Google Scholar
- 7 Jones, C. Assessment and Control of Software Risks. Prentice-Hall, Englewood Cliffs, N.J., 1994.]] Google ScholarDigital Library
- 8 McFarlan, F.W. Portfolio approach to information systems. Harvard Bus. Rev. 59, 5 (1981), 142-150.]]Google Scholar
- 9 Newman, M. and Sabherwal, R. Determinants of commitment to information systems development: A longitudinal investigation. MIS Q. 20,1 (1996).]] Google ScholarDigital Library
- 10 Sauer, C. Understanding support--Lessons from a case study. AustrailianJ. Info. Syst. 1, 1 (1993), 63-74.]]Google Scholar
- 11 Schmidt, R.C. Managing Delphi surveys using nonparametric statistical techniques. Decision Sciences, 28 3 (Summer 1997), 763-774.]]Google ScholarCross Ref
- 12 Schmidt, R.C., Lyytinen, K., Keil, M., and Cule, P. Identifying Software Project Risks: An International Delphi Study. Hong Kong University of Science and Technology Working Paper (1997).]]Google Scholar
Index Terms
- A framework for identifying software project risks
Recommendations
Identifying Software Project Risks: An International Delphi Study
Advocates of software risk management claim that by identifying and analyzing threats to success (i.e., risks) action can be taken to reduce the chance of failure of a project. The first step in the risk management process is to identify the risk itself,...
Identifying software project risks in Nigeria: an international comparative study
We report a study where software project risk factors were solicited in Nigeria. The study repeats a research design, which has been used in a Delphi study in the U.S., Finland, and Hong Kong to rank software development risks. The study produces a rank-...
Controlling software project risks: an empirical study of methods used by experienced project managers
SAICSIT '02: Proceedings of the 2002 annual research conference of the South African institute of computer scientists and information technologists on Enablement through technologyThe failure rate of software projects has been proven to be very high, and the incidence of failure is becoming worse as more companies venture into software development. Risk management is a collection of methods aimed at minimising or reducing the ...
Reviews
Sumit Sircar
Software project failures are a critically important problem in industry. Unfortunately, the authors do not clarify what they mean by “failure.” Does it simply refer to canceled software projects, or does it also include projects that do not deliver what the users who commissioned them asked for__?__ Some people may be tempted to define failure as projects that are delivered over budget and after the promised delivery date, but this definition would include most computer systems! The authors conducted an international Delphi study of 40 managers in the US, Finland, and Hong Kong. The most important risk factors in all three locations were remarkably consistent: lack of top management commitment to the project; failure to gain user commitment; and misunderstanding the requirements. The approach uses a 2×2 matrix framework for viewing all risks; that is, it considers four risk categories. This allows all of the risk factors to be categorized according to two factors—perceived level of control <__?__Pub Caret>and perceived relative importance. The authors also provide some strategies for reducing the risk, even though many of the highest risks are in a category considered beyond the manager's control. Interestingly, only one of the final risk factors had to do with the technology itself. Although the topic is not explicitly addressed, the study also provides some insight into the skills project managers need in order to reduce the risk of failure.
Access critical reviews of Computing literature here
Become a reviewer for Computing Reviews.
Comments