|
|
Article: WHY SOFTWARE PROJECTS ESCALATE: AN EMPIRICAL ANALYSIS AND TEST OF FOUR THEORETICAL MODELS [1,2].
- Article from:
- MIS Quarterly
- Article date:
- December 1, 2000
- Author:
CopyrightCOPYRIGHT 2000 University of Minnesota, MIS Research Center. This material is published under license from the publisher through the Gale Group, Farmington Hills, Michigan. All inquiries regarding rights should be directed to the Gale Group. (Hide copyright information)
|
Abstract
Software projects can often spiral out of control to become "runaway systems" that far exceed original budget and schedule projections. The behavior that underlies many runaway systems can best be characterized as "escalation of commitment to a failing course of action." The objectives of this study were to: (1) understand the extent to which IS projects are prone to escalate, (2) compare the outcomes of projects that escalate with those that do not, and (3) test whether constructs associated with different theories of escalation can be used to discriminate between projects that escalate and those that do not. A survey was administered to IS audit and ...
Related newspaper, magazine, and journal articles:
|
|
Article: County Software Project Gets Go-Ahead for Standards
Targeted News Service;
November 25, 2008 ;
561 words
... ... the criminal justice system. The county officials and information technology department heads on the CIRA board voted to authorize ... participate by obtaining commissioners court approval of the software project resolution that is available online at www.cira.state ...
|
|