journal article Nov 01, 2012

Technical Debt: From Metaphor to Theory and Practice

View at Publisher Save 10.1109/ms.2012.167
Topics

No keywords indexed for this article. Browse by subject →

References
10
[1]
gat Cutter IT J (2010)
[2]
fowler "Technical Debt"
[4]
brown "Managing Technical Debt in Software-Intensive Systems" Future of software engineering research
[5]
sterling Managing Software Debt Building for Inevitable Change (2010)
[6]
kruchten "What Colour Is Your Backlog?"
[7]
brown "Enabling Agility through Architecture" Crosstalk (2010)
[8]
mcconnell "Technical Debt"
[9]
kruchten "Report on the 3rd Workshop on Managing Technical Debt" ACM SIGSOFT Software Eng Notes
Cited By
519
Information and Software Technology
Metrics
519
Citations
10
References
Details
Published
Nov 01, 2012
Vol/Issue
29(6)
Pages
18-21
License
View
Cite This Article
Philippe Kruchten, Robert L. Nord, Ipek Ozkaya (2012). Technical Debt: From Metaphor to Theory and Practice. IEEE Software, 29(6), 18-21. https://doi.org/10.1109/ms.2012.167
Related

You May Also Like

Capability maturity model, version 1.1

M.C. Paulk, B. Curtis · 1993

712 citations

Digital Transformation

Christof Ebert, Carlos Henrique C. Duarte · 2018

324 citations

What Makes APIs Hard to Learn? Answers from Developers

Martin P. Robillard · 2009

282 citations

The Art and Science of Software Release Planning

G. Ruhe, M.O. Saliu · 2005

189 citations

A survey of unit testing practices

P. Runeson · 2006

188 citations