CoChat

No Single Metric Captures Productivity

Open access
Jaspan, Ciera, Sadowski, Caitlin · 2019 · Rethinking Productivity in Software Engineering

The DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.

Abstract

The urge to measure the productivity of developers is not new. Since it is often the case at organizations that more code needs to be written, many attempts have been made to measure productivity based on lines of code (LOC). For example, in early 1982, the engineering management of developers working on software for the Apple Lisa computer decided to start tracking LOC added by each developer. One week, the main user interface designer, Bill Atkinson, optimized Quickdraw’s region calculation machinery and contributed -2000 LOC. The management stopped asking for his LOC. Although measuring engineer productivity by LOC is clearly fraught, anecdotes like this abound on the internet. Organizations have continued to search for better easy ways to measure developer productivity. We argue that there is no metric that adequately captures the full space of developer productivity, and that attempting to find one is counter-productive. Instead, we encourage the design of a set of metrics tailored for answering a specific goal.

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

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

Integrity signals

Registry

Crossref · 10.1007/978-1-4842-4221-6_2

Cites

4 of 4 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

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

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

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

Show all 4 references

Cited by

See all 31

Metadata

Authors
Jaspan, C., & Sadowski, C.
Affiliations
Google (United States) (US)
Venue
Rethinking Productivity in Software Engineering
Publisher
Apress
Published
2019
Pages
13-20
OpenAlex
W2944429713
Cited by
20
References
4
Citations by year
2026: 2 · 2025: 2 · 2024: 4 · 2023: 5 · 2022: 3 · 2021: 1 · 2020: 3
FWCI
5.26
Type
book chapter
Language
en
Open access
Licence
  • cc-by-nc-nd
  • creativecommons.org/licenses/by-nc-nd/4.0 (tdm)
Locations
Apress eBooks (publishedVersion, cc-by-nc-nd)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
Keywords
developer productivity, productivity indicators, lines of code, software metrics, software engineering management

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: No Single Metric Captures Productivity. https://app.cochat.ai/papers/10.1007/978-1-4842-4221-6_2
The paper
Jaspan, C., & Sadowski, C. (2019). No Single Metric Captures Productivity. Rethinking Productivity in Software Engineering. https://doi.org/10.1007/978-1-4842-4221-6_2

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.