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.
Mandic, V., Tausan, N., Ramac, R., Freire, S., Rios, N., Perez, B., et al. (2021). Technical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced Practitioners. IEEE SOFTWARE, 38(6), 50-58 [10.1109/MS.2021.3103121].
Technical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced Practitioners
Falessi, D;
2021-01-01
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.File in questo prodotto:
| File | Dimensione | Formato | |
|---|---|---|---|
|
IEEE_Software_08_2021B.pdf
solo utenti autorizzati
Tipologia:
Versione Editoriale (PDF)
Licenza:
Copyright dell'editore
Dimensione
4.41 MB
Formato
Adobe PDF
|
4.41 MB | Adobe PDF | Visualizza/Apri Richiedi una copia |
I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.
