The IRMA Community
Newsletters
Research IRM
Click a keyword to search titles using our InfoSci-OnDemand powered search:
|
Recognizing Runaway IS Projects When They Occur: The Bank Consortium Case
Author(s): Joan Ellen Cheney Mann (Old Dominion University, USA)
Copyright: 2002
Pages: 8
EISBN13: 9781599046914
Purchase
View Sample PDF
Abstract
Runaway projects have been a problem in information systems (IS) for quite some time. In 1988, KPMG found that 35% of their largest clients currently had a runaway project, and in 1991 the percentage of firms increased to 60%. Plus, over 50% of the respondents considered this to be normal (Rothfeder, 1988; Cringely, 1994). The traditional definition of a runaway is any project that grossly exceeds budget and time targets but yet has failed to produce an acceptable deliverable. Given that each runaway project is a dysfunctional use of organizational resources, it is important for practitioners to be able to identify them early and react appropriately. On the other hand, this case will help practitioners realize that the issues within runaway projects are complex and difficult. The case could be used in MIS courses for non-IS majors, systems analysis and project management classes for IS majors or EDP auditing courses in accounting.
Related Content
|
Vedran Mornar, Krešimir Fertalj, Damir Kalpić, Slavko Krajcar.
© 2002.
19 pages.
|
|
Elayne Coakes, Anton Bradburn, Cathy Black.
© 2005.
8 pages.
|
|
John H. Heinrichs, William J. Doll.
© 2001.
21 pages.
|
|
Gerald C. Campbell, Christopher L. Huntley, Michael R. Anderson.
© 2003.
12 pages.
|
|
Roberto Vinaja.
© 2002.
18 pages.
|
|
|