A Framework for software risk management

Journal of Information Technology

Volumn 11, Issue 4, 1996, Pages 275-285

  Lyytinen, Kalle ^a   Mathiassen, Lars ^b   Ropponen, Janne ^c  

^a UNIVERSITY OF JYVÄSKYLÄ   (Finland)

^b AALBORG UNIVERSITY   (Denmark)

^c NOKIA SIEMENS NETWORKS   (Finland)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 0030366929     PISSN: 02683962     EISSN: 14664437     Source Type: Journal    
DOI: 10.1057/jit.1996.2     Document Type: Article

References (46)

1. Alter, A. and Ginzberg, M. (1978) Managing uncertainty in MIS implementation. Sloan Management Review, Fall20(1), 23-31.
2. Andersen, N. E., Kensing, F., Lundin, J., Mathiassen, L., Munk-Madsen, A., Rasbech, M. and Snrgaard, P. (1990) Professional Systems Development: Experience, Ideas and Action, (Prentice Hall, Hemel Hempstead, Hertfordshire).
3. Barki, H., Rivard, S. and Talbot, J. (1993) Toward an assessment of software development risk. Journal of Management Information Systems, 10 (2), 203-25.
4. Boehm, B. W. (1989) Software Risk Management. Tutorial, IEEE Computer Society Press, Los Alamitos, California.
5. Boehm, B. W. (1991) Software risk management: principles and practices. IEEE Software, January 12, 32-41.
6. Boehm, B. W., Gray, T. and Seewaldt, T. (1984) Prototyping versus specifying: a multiproject experiment. IEEE Transactions on Software Engineering, 10 (3).
7. Boehm, B. W. and Ross, R. (1989), Theory-W software project management: principles and examples IEEE Transactions on software engineering, 15 (7), 902-16.
8. Burns, R. and Dennis, A. (1985) Selecting an • appropriate application development Database, Fall, 17, 19-23.
9. Charette, R. N. (1989) Software Engineering Risk Analysis and Management (Intertext Publications, McGraw-Hill, New York).
10. Checkland, P. (1981) Systems Thinking, Systems Practice (John Wiley, Chichester).
11. Constantine, L. (1993) Work organization: paradigms for project management and organization Communications of the ACM, 36 (10), 32-43.
12. Cooprider, J. G. and Henderson, J. C. (1991) Technology - process fit: perspectives on achieving prototyping effectiveness. Journal of Management Infonnation Systems, 7(3), 67-87.
13. Curtis, B., Krasner, H. and Iscoe, N. (1988) A field study of the software design process for large systems. Communications of the ACM, 31 (11), 1268-87.
14. Davis, G. B. (1982) Strategies for information requirements determination. IBM Systems Journal, 21 (1), 4-30.
15. Davis, G. B., Lee, A. S., Nickles, K. R., Chatterjee, S., Hartung, R. and Wu, Y. (1990) Diagnosis of an Infonnation System Failure: A Framework and Interpretive Process, Management Infonnation Systems Research Centre, WP-O1-06, University of Minnesota.
16. Earl, M. (1989) Management Strategies for Infonnation Technology (Prentice Hall, London).
17. Fairly, R. (1994) Risk management for software projects. IEEE Software, 11 (3), 57-67.
18. Galliers, R. D. and Sutherland, A. R. (1991) Infonnation systems management and strategy fonnulation: the ‘stages of growth’ model revisited. Journal of Infonnation Systems 1 (2).
19. Gjesing, M. V. (1993) Risk-based Project Management-An example. The Danish Bank Academy (in Danish).
20. Heiskanen, A. (1994) Issues and Factors Affecting the Success and Failure of a Student Record System Development Process- a Longitudinal Investigation Based on Reflection-inAction. PhD Dissertation, Department of Computer Science, University of Tampere.
21. Humphrey, W. S. (1989) Managing the Software Process. Software Engineering Institute, The SEI Series in Software Engineering (Addison-Wesley, Reading, Mass., USA).
22. Keil, M. (1995) Pulling the plug: software project management and the problem of project escalation. MISQ 19 (4), 421-47.
23. Leavitt, H. J. (1964) Applied organization change in industry: structural, technical and human approaches in, Leavitt, H. J. (ed), New Perspectives in Organizational Research(John Wiley, Chichester), 55-71.
24. Lyytinen, K. (1991) Penetration of infonnation technology in organizations: a comparative study using stage models and transaction costs. Scandinavian Journal of Infonnation Systems, 3, 87-109.
25. Lyytinen, K. and Hirschheim, R. (1987) Information systems failures - a survey and classification of the empirical literature. Oxford surveys in Infonnation Technology Vol 4., (Oxford University Press, Oxford), 257-309.
26. Lyytinen, K., Mathiassen, L. and Ropponen, J. (1996), Attention shaping and software risk - A categorical analysis of four classical approaches, submitted for publication.
27. March, J., Sproull, L. and Tamuz, M. (1991) Learning from samples of one or fewer. Organization Science, 2 (1), 1-13.
28. Mc Farlan, W. (1982) Portfolio approach to information systems. Journal of Systems Management, January 33(1), 12-19.
29. Markus, L. and Keil, M. (1994) If we build it, they will come: designing information systems that users want to use. Sloan Management Review.
30. Mathiassen, L. Seewaldt, T. and Stage, J. (1995) Prototyping and specifying: principles and practices of a mixed approach. Scandinavian Journal of Infonnation Systems, 7(1), 55-72.
31. Mumford, E. (1983) Designing Human Systems (Manchester Business School, Manchester).
32. Mumford, E. and Mc Donald, B. W. (1989) XSEL’s progress- the continuing journey of an expert system (John Wiley, Chichester).
33. Neo, B. S. and Leong, K. S. (1994) Managing risks in information technology projects: a case study of TradeNet. Journal of Infonnation Technology Management, May 5(3), 29-45.
34. Nolan, R. L. (1973), Managing the computer resource: a stage hypothesis. Communications of the ACM, 16 (7), 399-405.
35. Parnas, R. and Clemens, P. (1986) A rational design process: how and why to fake it. IEEE transactions on Software Engineering, SE-12, (2), 251-7.
36. Roberts, K. ed. (1993) New Challenges to Understanding Organizations, (Macmilian, New York).
37. Rochlin, G. (1993) Defining ‘high reliability’ organizations in practice: a taxo-nomic prologue, in New Challenges to Understanding Organizations, Roberts, K. (ed) (Macmillan), 11-32.
38. Ropponen, J. (1993) Risk Management in Infonnation System Development, Licentiate thesis, Department of Computer Science and Infonnation Systems, University of Jyvaskyla, Finland.
39. Ropponen, J. and Lyytinen, K. (1996) How Software Risk Management Can Improve Systems Development: An exploratory Study, accepted for publication in European Journal of Infonnation Systems.
40. Simon, H. (1979) Rational decision making in business organizations. American Economic Review, 69 (4), 493-513.
41. Simon, H. (1983) Theories of Bounded Rationality, Behavioural Economics and Business Organization, Vol. 1-2 (MUTT Press, Cambridge), 160-176.
42. Willcocks, L. and Margetts, H. (1994) Risk assessment and information systems. European Journal of Infonnation Systems, 3 (2).
43. Weick, K. (1979) The Social Psychology of Organizing (Addison-Wesley, Reading, MASS).
44. Weick, K. and Daft, R. (1983) The effectiveness of interpretation systems, in Organizational Effectiveness: A Comparison of Multiple Models, Cameron K. and fretten D. (eds) (Academic Press, New York).
45. Weinberg, G. M. (1986) Becoming A Technical Leader - An Organic Problem Solving Approach (Dorset House Publishing).
46. Van de Swede, V. and van Vliet, J. (1994) Consistent development: results of a first empirical study on the relation between the project scenario and success, in Proceedings of the 6th CAiSE conference, Wijers, G. and Brinkkemper, S. (eds), (Springer Verlag, Uttrecht, The Netherlands), 80-93.