Can software risk management improve system development: An exploratory study

European Journal of Information Systems

Volumn 6, Issue 1, 1997, Pages 41-50

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

^a NOKIA RESEARCH CENTER   (United States)

^b UNIVERSITY OF JYVÄSKYLÄ   (Finland)

^c GEORGIA STATE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 21744458498     PISSN: 0960085X     EISSN: 14769344     Source Type: Journal    
DOI: 10.1057/palgrave.ejis.3000253     Document Type: Article

References (36)

1. Alter S and Ginzberg M (1978) Managing uncertainty in MIS implementation. Sloan Management Review, Fall, 23-31.
2. Barki H, Rivard S and Talbot J (1993) Toward an assessment of software development risk. Journal of Management Information Systems 10 (2), Fall, 203-225.
3. Beath CM (1987) Strategies for managing MIS projects: a transaction cost approach. In Proceedings of the 4th International Conference on Information Systems, Texas, Houston, 15-17 Dec, pp 133-147.
4. Beath CM (1987) Managing the user relationship in information systems development projects: a transaction governance approach. In Proceedings of the 8th International Conference on Information Systems, Pittsburgh, 12-14 Dec, pp 415-427.
5. Boehm BW (1989) Software Risk Management, tutorial. IEEE Computer Society Press.
6. Boehm BW (1991) Software risk management: principles and practices. IEEE Software January, pp 32-41.
7. Boehm BW (1995) Personal communication. Helsinki University of Technology, 20 June.
8. Boehm BW and Ross R (1989) Theory-W software project management: principles and examples. IEEE Transactions on Software Engineering 15(7), 902-916.
9. Brooks F (1974) The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley London, Prentice-Hall.
10. Charette RN (1989) Software Engineering Risk Analysis and Management. Intertext Publications McGraw-Hill Book Company.
11. Cronbach LJ (1951) Coefficient alpha and the internal structure of tests. Psychometrika 16(3), 297-334.
12. Curtis B, Krasner H and Iscoe N (1988) A field study of the software design process or large systems. Communications of the ACM 31(11), 68-87.
13. Cody RP and Smith JK (1987) Applied Statistics and the SAS Programming Language. 2nd ed. Elsevier Science Publishing Co, Inc.
14. Davis GB (1982) Strategies for information rquirements determination. IBM Systems Journal 21(1), 4-30.
15. Finnish Information Processing Association (1991) Individual Business Members. In Buyer’s guide 1991. Infoline Oy/Insinöörilehdet Oy, Kustannusosakeyhtio Otava, Keuruu.
16. Genuchten van M (1991) Why is software late? An empirical study of reasons for delay in software development. IEEE Transactions on SE 17(6), 582-590.
17. Haga W and Zviran M (1994) Information systems effectiveness: research design for causal inference. Information Systems Journal 4(2), 141-166.
18. Humphrey WS (1989) Managing the Software Process, Software Engineering Institute. The SEI Series in Software Engineering. Addison-Wesley Publishing Company Inc.
19. Kerzner H (1987) In search of excellence in project management. Journal of Systems Management 38(2), 30-39.
20. Lyytinen K (1987) Different perpectives on information systems: problems and their solutions. ACM Computing Surveys 19(1), 5-44.
21. Lyytinen K (1988) Expectation failure concept and systems analyst’s view of information system failures: results of an exploratory study. Information & Management 14(1), 45-56.
22. Lyytinen K and Hirschheim R (1987) Information systems failures: a survey and classification of the empirical literature. Oxford Surveys in Information Technology. Oxford University Press, Vol. 4, pp 257-309.
23. Lyytinen K, Mathiassen L and Ropponen J (1996) A framework for software risk management. Journal of Information Technology 11, 278-285.
24. Lyytinen K, Mathiassen L and Ropponen J (1996) Attention shaping and software risk: a categorical analysis of four classical approaches. University of Jyvaskyla, Finland, unpublished working paper.
25. Markus L and Keil M (1994) If we build it, they will come: designing information systems that users want to use. Sloan Management Review 35(4), 11-25.
26. Mathiassen L, Seewaldt T and Stage J (1995) Prototyping and specifying: principles and practices of a mixed approach. Scandinavian Journal of Information Systems 7(1), 55-72.
27. McFarlan W (1982) Portfolio approach to information systems. Journal of Systems Management January, 12-19.
28. Mills FC (1965) Statistical Methods 3rd edn, Sir Isaac Pitman and Sons Ltd.
29. Neo BS and Kwong SL (1994) Managing risks in information technology projects: a case study of trade net. Journal of Information Technology Management May.
30. Nunnally JC (1978) Psychometric theory. McGraw-Hill, New York, NY.
31. Ropponen J (1993) Risk management in information system development, technical reports TR-3. Department of Computer Science and Information Systems, University of Jyvaskyla, Finland.
32. Ropponen J (1997) Software Development Risks and Management Practices — a project manager survey. In Beyond the IT Productivity Paradox: Assessment Issues (Willcocks L and Lester S, Eds), McGraw-Hill Inc, forthcoming in September.
33. Schmidt R (1996) Identifying software project risks: an international Delphi study, Hong Kong University of Science and Technology, unpublished working paper.
34. Straub DW (1989) Validating instruments in MIS research. MIS Quarterly June, 147-165.
35. Swede van V and Vlient van J (1994) Consistent development: results of a first empirical study on the relation between project scenario and success. In Wijers G., Brinkkemper S (eds), Proceedings of the 6th CAISE Conference, Springer-Verlag.
36. Willcocks L and Margetts H (1994) Risk assessment and information systems. European Journal of Information Systems 3(2), 127-138.