Technical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced Practitioners
Authors:
- Vladimir MandicVladimir Mandic
- Nebojsa TausanNebojsa Tausan
- Robert RamacRobert Ramac
- Savio FreireSavio Freire
- Nicolli RiosNicolli Rios
- Boris PerezBoris Perez
- Camilo CastellanosCamilo Castellanos
- Dario CorrealDario Correal
- Alexia PachecoAlexia Pacheco
- Gustavo LopezGustavo Lopez
- Clemente IzurietaClemente Izurieta
- Davide FalessiDavide Falessi
- 9 August 2021
- journal article
- research article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 38 (6) , 50-58
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.Keywords
This publication has 11 references indexed in Scilit:
- A systematic literature review on Technical Debt prioritization: Strategies, processes, factors, and toolsJournal of Systems and Software, 2021
- Common Causes and Effects of Technical Debt in Serbian IT: InsighTD Survey Replication2020
- The practitioners’ point of view on the concept of technical debt and its causes and consequences: a design for a global family of industrial surveys and its first results from BrazilEmpirical Software Engineering, 2020
- Software developer productivity loss due to technical debt—A replication and extension study examining developers’ development workJournal of Systems and Software, 2019
- A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitionersInformation and Software Technology, 2018
- Reducing Friction in Software DevelopmentIEEE Software, 2015
- Estimating the Principal of an Application's Technical DebtIEEE Software, 2012
- Technical Debt: From Metaphor to Theory and PracticeIEEE Software, 2012
- Experimentation in Software Engineering2012
- A similarity measure for indefinite rankingsACM Transactions on Information Systems, 2010