The DOI matches its Crossref record; 47 of the 47 references it cites were found in a registry or an index.
Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models1, 2
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 control professionals and, to establish a baseline for comparison, the survey was designed to gather data on projects that did not escalate as well as those that did escalate. The results of our research suggest that between 30% and 40% of all IS projects exhibit some degree of escalation. Projects that escalated had project outcomes that were significantly worse in terms of perceived implementation performance and perceived budget/schedule performance, as compared to projects that did not escalate. Using constructs from theories that have been used to explain the escalation phenomenon, we were able to test various logistic regression models for their ability to discriminate between projects that escalate and those that do not. To construct our models, we explored constructs derived from self-justification theory, prospect theory, agency theory, and approach avoidance theory. While constructs derived from all four theories were significant in logistic regression models, the completion effect construct derived from approach avoidance theory provided the best classification of projects, correctly classifying over 70% of both escalated and non-escalated projects.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Theory of the firm: Managerial behavior, agency costs and ownership structure
Jensen, M. C., & Meckling, W. H. (1976) · Journal of Financial Economics · doi:10.1016/0304-405x(76)90026-x · Cited by 71,491
Prospect Theory: An Analysis of Decision under Risk
Kahneman, D., & Tversky, A. (1979) · Econometrica · doi:10.2307/1914185 · Cited by 48,524
Prospect theory: An analysis of decision under risk
Kahneman, D., & Tversky, A. (1988) · Decision, Probability and Utility · doi:10.1017/cbo9780511609220.014 · Cited by 32,474
A Theory of Cognitive Dissonance
Festinger, L. (1957) · doi:10.1515/9781503620766 · Cited by 24,241
The Framing of Decisions and the Psychology of Choice
Tversky, A., & Kahneman, D. (1981) · Science · doi:10.1126/science.7455683 · Cited by 18,497
The Social Psychology of Organizations.
Hackman, J. R., Katz, D., & Kahn, R. L. (1979) · Administrative Science Quarterly · doi:10.2307/2989929 · Cited by 12,235
Brooks, F. P. (1975) · ACM SIGPLAN Notices · doi:10.1145/390016.808439 · Cited by 3,224
Arkes, H. R., & Blumer, C. (1985) · Organizational Behavior and Human Decision Processes · doi:10.1016/0749-5978(85)90049-4 · Cited by 2,573 · cited 2×
“Arkes and Blumer (1985), for example, describe the Tennessee(cid:150)Tombigbee Waterway Project, which was scheduled for Congressional review in 1981.”
BackgroundInfluential(1990) · Computers, Environment and Urban Systems · doi:10.1016/0198-9715(90)90039-v · Cited by 2,468
The mythical man-month: essays on software engineering
(1996) · Choice Reviews Online · doi:10.5860/choice.33-5142 · Cited by 2,452
Cited by
Pavlou, P. A., Liang, H., & Xue, Y. (2007) · MIS Quarterly · doi:10.2307/25148783 · Cited by 2,646
Predictive Analytics in Information Systems Research1
Shmueli, G., & Koppius, O. R. (2011) · MIS Quarterly · doi:10.2307/23042796 · Cited by 1,328
Venkatesh, V., Thong, J. Y. L., Chan, F. K. Y., Hu, P. J.-H., & Brown, S. A. (2011) · Information Systems Journal · doi:10.1111/j.1365-2575.2011.00373.x · Cited by 852
Predictive Analytics in Information Systems Research
Shmueli, G., & Koppius, O. (2010) · doi:10.2139/ssrn.1606674 · Cited by 676
Innovating Mindfully with Information Technology1
Swanson, E. B., & Ramiller, N. C. (2004) · MIS Quarterly · doi:10.2307/25148655 · Cited by 565
Metadata
- Authors
- Keil, M., Mann, J., & Rai, A.
- Venue
- MIS Quarterly
- Publisher
- MIS Quarterly
- Published
- 2000-12-01
- Volume
- 24
- Issue
- 4
- Pages
- 631-647
- ISSN
- 0276-7783 (ISSN-L)
- 2162-9730
- OpenAlex
- W1552413492
- Cited by
- 443
- References
- 47
- FWCI
- 21.60
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models1, 2. https://app.cochat.ai/papers/10.2307/3250950
- The paper
- Keil, M., Mann, J., & Rai, A. (2000). Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models1, 2. MIS Quarterly. https://doi.org/10.2307/3250950
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.