Technical Debt¶
Kruchten, Nord, & Ozkaya. (2012). Technical Debt: From Metaphor to Theory and Practice. IEEE Software.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Gold Plating
- Because the addition is often invisible to the principal until the downstream costs surface — weeks or months later, attributed to complexity or technical debt rather than to the original unilateral decision
This sourcePaper organising the technical-debt landscape and recounting the metaphor's introduction to explain to nontechnical stakeholders the need for refactoring.
Supported in partVerified against the publisher's abstract
“The metaphor of technical debt in software development was introduced two decades ago to explain to nontechnical stakeholders the need for what we call now "refactoring."”
- Because the addition is often invisible to the principal until the downstream costs surface — weeks or months later, attributed to complexity or technical debt rather than to the original unilateral decision
Verification¶
Does it exist? Not checked yet. This work's DOI is recorded above but has not been resolved against an external catalogue, so nothing here confirms the work exists.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:ce20de9d0aae · see in the full table