P1: IML/FFX P2: IML/FFX QC: IML/FFX T1: IML
Management WL040/Bidgoli-Vol III-Ch-19 June 23, 2003 16:22 Char Count= 0
236 RISKMANAGEMENT ININTERNET-BASEDSOFTWAREPROJECTSHighsmith, J. (2000).Adaptive software development: a col-
laborative approach to managing complex systems.New
York: Dorset House.
Keil, M., Cule, P., Lyytinen, K., Schmidt, R. (1998). A
framework for identifying software project risks.Com-
munications of the ACM, 41,76–83.
Kumar, R. (2002). Managing risks in IT projects: An
options perspective.Information & Management 40,
63–74.
Lyytinen, K., & Hirschheim, R. (1987). Information sys-
tems failures—A survey and classification of the empir-
ical literature. In Zorkoczy, P. I. (Ed.),Oxford surveys
in information technology(Vol. 4, pp. 257–309). Oxford,
UK: Oxford University Press.
Lyytinen, K., Mathiassen, L., & Ropponen, J. (1998). At-
tention shaping and software risk: A categorical anal-
ysis of four classical risk management approaches.In-
formation Systems Research, 9,233–255.March, J., & Shapira, Z. (1987). Managerial perspectives
on risk and risk taking.Management Science, 33,1404–
1418.
Phelps, J., Chan, C., & Kapsalis, S. (2001). Does scenario
planning affect performance? Two explanatory studies.
Journal of Business Research, 51,223–232.
Schmidt, R., Lyytinen, K., Keil, M., & Cule, P. (2001). Iden-
tifying software project risks: An international Delphi
study.Journal of Management Information Systems, 17,
5–36.
van Genuchten, M. (1991). Why is software late? An em-
pirical study of the reason for delay in software devel-
opment.IEEE Transactions on Software Engineering,
17,582–590.
Walkerden, F., & Jeffery, R. (1997). Software cost estima-
tion: A review of models, processes, and practice. In
Advances in Computers(Vol. 44, pp. 62–94). San Diego,
CA: Academic Press.