Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt
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
Cites
Statistics
Verification
Claims the paper makes
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?
In the citing paper
“In practical use, professionals will be able to use simplified versions of the analysis, while also being aware that such simplification leads to building up sustainability debt [12], just as temporarily disregarding good design and development guidelines leads to technical debt [61], which will need to be addressed at a later time.”
From Lessons learned from developing a sustainability awareness framework for software engineering using design science (2024) · cites this paper as [61]
Citations
Cites
Lakoff, G., & Johnson, M. (2003) · University of Chicago Press eBooks · doi:10.7208/chicago/9780226470993.001.0001 · Cited by 20,632
The WyCash portfolio management system
Cunningham, W. (1992) · Addendum to the proceedings on Object-oriented programming systems, languages, and applications (Addendum) - OOPSLA '92 · doi:10.1145/157709.157715 · Cited by 742 · cited 1×
“INTRODUCTION Technical debt is a metaphor introduced by Ward Cunningham in1992 [3] to help us think about a problem that is crippling many software endeavors.”
BackgroundTechnical Debt: From Metaphor to Theory and Practice
Kruchten, P., Nord, R. L., & Ozkaya, I. (2012) · IEEE Software · doi:10.1109/ms.2012.167 · Cited by 735 · cited 1×
“INTRODUCTION Technical debt is a metaphor introduced by Ward Cunningham in1992 [3] to help us think about a problem that is crippling many software endeavors.”
BackgroundSelf-citationInternational Conference on Software Engineering
(2017) · IEEE Software · doi:10.1109/ms.2017.3571566 · Cited by 622
Managing technical debt in software-reliant systems
Brown, N., Cai, Y., Guo, Y., Kazman, R., Kim, M., Kruchten, P., Lim, E., MacCormack, A., Nord, R., Ozkaya, I., et al. (2010) · Proceedings of the FSE/SDP workshop on Future of software engineering research · doi:10.1145/1882362.1882373 · Cited by 432
Self-citationA Balancing Act: What Software Practitioners Have to Say about Technical Debt
Lim, E., Taksande, N., & Seaman, C. (2012) · IEEE Software · doi:10.1109/ms.2012.130 · Cited by 201 · cited 1×
“This has been confirmed again and again by studies of practitioners [10][11][17].”
ResultAn empirical model of technical debt and interest
Nugroho, A., Visser, J., & Kuipers, T. (2011) · Proceedings of the 2nd Workshop on Managing Technical Debt · doi:10.1145/1985362.1985364 · Cited by 153
Allman, E. (2012) · Communications of the ACM · doi:10.1145/2160718.2160733 · Cited by 151
The SQALE method for evaluating Technical Debt
Letouzey, J.-L. (2012) · IEEE/ACM International Conference on Technical Debt (TechDebt) · doi:10.1109/mtd.2012.6225997 · Cited by 144
A portfolio approach to technical debt management
Guo, Y., & Seaman, C. (2011) · Proceedings of the 2nd Workshop on Managing Technical Debt · doi:10.1145/1985362.1985370 · Cited by 132 · cited 1×
“There is a positive aspect to technical debt, when one looks at it from the perspective of an investment [9].”
Background
Research works printed but not linked: 3
- 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.
- 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.
- 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
A systematic mapping study on technical debt and its management
Li, Z., Avgeriou, P., & Liang, P. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2014.12.027 · Cited by 743
“Similar to Li et al. (2013), we do not use study quality assessment results to filter primary studies.”
An Exploratory Study on Self-Admitted Technical Debt
Potdar, A., & Shihab, E. (2014) · 2014 IEEE International Conference on Software Maintenance and Evolution · doi:10.1109/icsme.2014.31 · Cited by 281
“[15] present an in-depth description of technical debt.”
BackgroundMeasure it? Manage it? Ignore it? software practitioners and technical debt
Ernst, N. A., Bellomo, S., Ozkaya, I., Nord, R. L., & Gorton, I. (2015) · Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2786805.2786848 · Cited by 260
Self-citationUsing Natural Language Processing to Automatically Detect Self-Admitted Technical Debt
Maldonado, E. D. S., Shihab, E., & Tsantalis, N. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2654244 · Cited by 218
“, debt) to maintain this software in the long run [2], [3].”
BackgroundIdentifying self-admitted technical debt in open source projects using text mining
Huang, Q., Shihab, E., Xia, X., Lo, D., & Li, S. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9522-4 · Cited by 194
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.