Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 178

The DOI matches its Crossref record.

Blowing the whistle on troubled software projects

Robey, Daniel·2001·Communications of the ACM

Abstract

The article focuses on various challenges of project failure that software development community is facing despite advances in software engineering. According to the Standish Group's 1998 survey, only 26% of such projects were delivered on time, on budget, and with promised functionality, wasting billions of dollars annually. 46% were completed over budget and behind schedule, with fewer functions and features than originally specified. A runaway is a project that has failed significantly to achieve its objectives and/or has exceeded its original budget by at least 30%. When evidence of a failing project may exist in the lower ranks of an organization, accurate information about failure may fail to move up the organizational hierarchy. Consequently, decision makers with the authority to change the direction of the project are too often unaware of its true status. In case of failure many people blame technology, but the mum and deaf effects are likely to be major contributing factors behind runaway projects. INSET: How the Study Was Done.

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.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/367211.367274

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.

A few free checks a day · papers already verified open instantly · results are public

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

Cited by

See all 178

Metadata

Authors
Robey, D.
Venue
Communications of the ACM
Published
2001-04
Volume
44
Issue
4
Pages
87-93
ISSN
  • 0001-0782 (ISSN-L)
  • 1557-7317
OpenAlex
W2081748916
Cited by
178
References
0
FWCI
18.59
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: Blowing the whistle on troubled software projects. https://app.cochat.ai/papers/10.1145/367211.367274
The paper
Robey, D. (2001). Blowing the whistle on troubled software projects. Communications of the ACM. https://doi.org/10.1145/367211.367274

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.