Abstract
Technical debt (TD) can be injected at any stage of software development, spreading across other phases and causing various problems. This article presents a model for conceptualizing TD causes, effects, payment practices, and reasons for payment avoidance, with a prioritization schema for technical and nontechnical roles.
| Original language | English |
|---|---|
| Pages (from-to) | 50-58 |
| Number of pages | 9 |
| Journal | IEEE Software |
| Volume | 38 |
| Issue number | 6 |
| DOIs | |
| State | Published - 2021 |
Bibliographical note
Publisher Copyright:© 1984-2012 IEEE.