CoChat

Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt

Kruchten, Philippe, Nord, Robert L., Ozkaya, Ipek, Falessi, Davide · 2013 · ACM SIGSOFT Software Engineering Notes

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

Abstract

As the pace of software delivery increases and technology rapidly changes, organizations seek guidance on how to insure the sustainability of their software development effort. Over the past four years running the workshops on Managing Technical Debt, we have seen increased interest from the software industry to understanding and managing technical debt. A better understanding of the concept of technical debt, and how to approach it, both from a theoretical and a practical perspective is necessary to advance its state of the art and practice. In this paper, we highlight the current confusion in industry on the definition of technical debt, their contributions that have led to a deeper understanding of this concept and the limits of the metaphor, the criteria to discriminate what is technical debt and not, and areas of further investigation.

Overview

Integrity signals

Registry

Crossref · 10.1145/2507288.2507326

Cites

30 of 30 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

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?

Citations

Cites

Show all 30 references

Research works printed but not linked: 3

  1. I. Gat , Ed. How to settle your technical debt--a manager's guide . Arlington, MA : Cutter Consortium , 2010 . I. Gat, Ed. How to settle your technical debt--a manager's guide. Arlington, MA: Cutter Consortium, 2010.
  2. S. McConnell , " Managing technical debt (slides)," in Workshop on Managing Technical Debt (part of ICSE 2013) : IEEE, 2013 . S. McConnell, "Managing technical debt (slides)," in Workshop on Managing Technical Debt (part of ICSE 2013): IEEE, 2013.
  3. K. Schmid , " On the Limits of the Technical Debt Metaphor ," in Proceedings of the 4th Workshop on Managing Technical Debt , at ICSE 2013 , P. Kruchten, I. Ozkaya, and R. Nord, Eds., IEEE , 2013, pp. 63 -- 66 . K. Schmid, "On the Limits of the Technical Debt Metaphor," in Proceedings of the 4th Workshop on Managing Technical Debt, at ICSE 2013, P. Kruchten, I. Ozkaya, and R. Nord, Eds., IEEE, 2013, pp. 63--66.

Cited by

See all 87

Metadata

Authors
Kruchten, P., Nord, R. L., Ozkaya, I., & Falessi, D.
Affiliations
  • University of British Columbia (CA)
  • Software Engineering Institute (US)
  • Software Engineering Institute Carnegie Mellon University Pittsburgh, PA, USA
  • Fraunhofer USA Center Mid-Atlantic CMA (US)
Venue
ACM SIGSOFT Software Engineering Notes
Published
2013-08-26
Volume
38
Issue
5
Pages
51-54
ISSN
0163-5948 (ISSN-L)
OpenAlex
W2031271477
Cited by
87
References
31
Citations by year
2026: 6 · 2025: 5 · 2024: 6 · 2023: 8 · 2022: 8 · 2021: 9 · 2020: 7 · 2019: 5 · 2018: 2 · 2017: 10 · 2016: 4 · 2015: 12 · 2014: 5
FWCI
20.31
Type
journal article
Language
en
Open access
closed
Locations
ACM SIGSOFT Software Engineering Notes (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
Keywords
technical debt, software sustainability, software maintenance, technical debt management, software quality, software development practices

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: Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt. https://app.cochat.ai/papers/10.1145/2507288.2507326
The paper
Kruchten, P., Nord, R. L., Ozkaya, I., & Falessi, D. (2013). Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt. ACM SIGSOFT Software Engineering Notes. https://doi.org/10.1145/2507288.2507326

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.