Technical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced Practitioners

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...

Descripción completa

Detalles Bibliográficos
Autores: Mandić, Vladimir, Taušan, Nebojša, Ramač, Robert, Freire, Sávio, Rios, Nicolli, Pérez, Boris, Castellanos, Camilo, Correal, Darío, Pacheco Hernández, Alexia, López Herrera, Gustavo, Izurieta, Clemente, Falessi, Davide, Seaman, Carolyn, Spínola, Rodrigo
Tipo de recurso: artículo
Fecha de publicación:2021
País:Costa Rica
Institución:Universidad de Costa Rica
Repositorio:Kérwá
Idioma:inglés
OAI Identifier:oai:kerwa.ucr.ac.cr:10669/90345
Acceso en línea:https://ieeexplore.ieee.org/document/9508982
https://hdl.handle.net/10669/90345
Access Level:acceso abierto
Palabra clave:Technical debt (TD)
SOFTWARE DEVELOPMENT
Software quality
Software maintenance
Software prioritization
Descripción
Sumario: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.

Similares en LA Referencia