Specifying the software project risk construct

16th Americas Conference on Information Systems 2010, AMCIS 2010

Volumn 2, Issue , 2010, Pages 1394-1406

  El Masri, Mazen ^a   Rivard, Suzanne ^a  

^a HEC MONTRÉAL   (Canada)

Author keywords

Information systems project risk; Risk definition; Risk factors; Risk management

Indexed keywords

MANAGEMENT MECHANISMS; PREDICTIVE POWER; PROJECT RISK; RISK DEFINITION; RISK EXPOSURE; RISK FACTORS; RISK SOURCES; SOFTWARE PROJECT RISKS;

INFORMATION SYSTEMS; RISK MANAGEMENT; SEMANTICS; SPECIFICATIONS;

RISKS;

EID: 84870433662     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (39)

1. Akmajian, A, Demers R, Farmer, A. and Harnish, R. (2001) Linguistics: An Introduction to Language and Communication, Fifth Edition, MIT Press.
2. Barki, H. (2008) Thar's Gold in Them Thar Constructs, Data Base, 39, 2, 9-20.
3. Barki, H., Rivard, S., and Talbot, J. (200l) An Integrative Contingency Model of Software Project Risk Management, Journal of MIS, 17, 4, 37-69.
4. Barki, H., Rivard, S., and Talbot, J. (1993) Toward an Assessment of Software Development Risk, Journal of MIS 10, 2, 203-225.
5. Benaroch M.(2002) Managing Information Technology Investment Risk: A Real Options Perspective, Journal of MIS, 19, 2,43-84.
6. Benaroch M., Lichtenstein Y. and Robinson K. (2006) Real Options in IT Risk Management: An Empirical Validation of Risk-Option Relationships, MIS Quarterly, 30, 4, 827-864.
7. Ben-David, I., Raz, T. (2001) An integrated approach for risk response development in project planning. Operational Research Society, 52, 1, 14-25.
8. Boehm, B.W. (1991) Software Risk Management: Principles and Practices, IEEE Software (32-41).
9. Charette, R.N., Adams K.M., and White M.B. (1997), Managing risk in software maintenance. IEEE Software, 14, 3, 43-50
10. Charette, R.N. (1989), Software Engineering Risk Analysis and Management, New York: Multiscience Press Inc.
11. Clemons, E.K. (1995), Using Scenario Analysis to Manage the Strategic Risks of Reengineering, Sloan Management Review, 61-71.
12. Cruse, A. (2004) Meaning in Language: An Introduction to Semantics and Pragmatics. (Second edition.) Oxford: Oxford University Press.
13. Davis, C.R. (2002), Calculated risk: a framework for evaluating product development, MIT Sloan Management Review, 43, 4, 71-77.
14. Gefen, D., Wyss, S., and Lichtenstein, Y., (2008) Business Familiarity as Risk Mitigation in Software Development Outsourcing Contracts, MIS Quarterly, 32, 3, 531-551.
15. Gluch, D. (1994) A Construct for Describing Software Development Risks (CMU/SEI-94-TR-14). Pittsburgh, Pa.: Software Engineering Institute, Carnegie Mellon University.
16. Han W., Huang S, (2007) An empirical analysis of risk components and performance on software projects, Journal of Systems and Software, 80, 1, 42-50.
17. Heemstra. R. and Kusters, R. (1997), Dealing with risk: a practical approach, Journal of Information Technology, 11, 4, 333-346.
18. Higuera, R. and Haimes Y. (1996), Software Risk Management, Carnegie Mellon. Software Engineering Institute.
19. Jackendoff, Ray, (1990). Semantic Structures. Cambridge, MA: MIT Press.
20. Jiang, J. J; Klein G. and Ellis. T.S. (2002), A Measure of Software Development Risk, Project Management Journal, 33,3,30-41
21. Jiang, J.J. and Klein, G., (1999) Risks to different aspects of system success, Information & Management Journal, 36,263-272.
22. Jiang, J.J., and Klein, G. (2000) Software development risks to project effectiveness, Journal of Systems and Software, 52, 3-10.
23. Keil, M., Cule P., Lyytinen K., and Schmidt R. (1998) A Framework for Identifying Software Project Risks, Communications of the ACM, 41, 11, 76-83.
24. Kumar, R., (2002) Managing risks in IT projects: an options perspective, Information & Managements, 40,63-74.
25. Lu, X.N., and Ma, Q.G. (2004) Risk Analysis in Software Development Project with Owners and Contractors, IEEE Engineering Management Conference, 2,789-793.
26. Lyytinen, K., Mathiassen, L. Ropponen, J.(1998) Attention shaping and software risk: a categorical analysis of four classical risk management approaches, Information Systems Research 9,3,233-55.
27. Madachy R. (1997). Heuristic risk assessment using cost factors. IEEE Software, 14, 3, 51-59.
28. Moynihan, T. (2002) Coping With Client-Based People Problems: The Theories of Action of Experienced IS/Software Project Management, Information and Management, 39, 377-390.
29. Mursu, A. Lyytinen, K. Soriyan H.A. and Korpela M., (2003) Identifying software project risks in Nigeria: an international comparative study. European Journal of Information Systems 12, 3, 182-194.
30. Nidumolu, S.R. (1996) Standardization, Requirements, Uncertainty, and Software Project Performance, Information and Management 31, 3, 135-150.
31. Purao, S., Paul, S., and Smith, S. (2007) Understanding enterprise integration project risks: A focus group study, 18th International Workshop on Database and Expert Systems Applications, 850-854.
32. Ropponen, J. and Lyytinen, K., (2000) Component of Software Development Risk: How to address them? IEEE, 26, 2, 98-111.
33. Robey, D., Boudreau, M., and Rose, G.M. (2000) Information Technology and Organizational Learning: A Review and Assessment of Research, Accounting, Management and Information Technology 10:2,125-155.
34. Royer P.S., (2000) Risk management: The undiscovered dimension of project management, Project Management Journal, 31,6-13.
35. Schmidt, R., Lyytinen K., et al. (2001) Identifying software project risks: An international Delphi study, Journal of Management Information Systems, 17,4,5-36
36. Sauer, C., Gemino, A., and Reich, B.H. (2007) The Impact of Size and Volatility on IT Project Performance, Communications of the ACM, 50, 11, 79-84.
37. Wallace, L., Keil, M., and Rai, A. (2004) How Software Project Risk Affects Project Performance: An Investigation of the dimension of risk and an exploratory model, Decision Sciences, 35, 2, 289-321.
38. Wallace, L., Keil, M., (2004), Software project risks and their effect on outcomes, Communications of the ACM, 47, 68-73.
39. Wallace, L., Keil, M. and Rai, A. (2004) Understanding software project risk: a cluster analysis, Information and Management, 42, 1, 115-125.