A Comprehensive View on TD Prevention Practices and Reasons for Not Preventing It
Authors:
- Sávio FreireSávio Freire
- Alexia PachecoAlexia Pacheco
- Nicolli RiosNicolli Rios
- Boris PérezBoris Pérez
- Camilo CastellanosCamilo Castellanos
- Darío CorrealDarío Correal
- Robert RamačRobert Ramač
- Vladimir MandićVladimir Mandić
- Nebojša TaušanNebojša Taušan
- Gustavo LópezGustavo López
- Manoel MendonçaManoel Mendonça
- Davide FalessiDavide Falessi
Open Access
- 27 September 2024
- journal article
- research article
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
- Vol. 33 (7) , 1-44
Abstract
Context . Technical debt (TD) prevention allows software practitioners to apply practices to avoid potential TD items in their projects. Aims . To uncover and prioritize, from the point of view of software practitioners, the practices that could be used to avoid TD items, the relations between these practices and the causes of TD, and the practice avoidance reasons (PARs) that could explain the failure to prevent TD. Method . We analyze data collected from six replications of a global industrial family of surveys on TD, totaling 653 answers. We also conducted a follow up survey to understand the importance level of analyzed data. Results . Most practitioners indicated that TD could be prevented, revealing 89 prevention practices and 23 PARs for explaining the failure to prevent TD. The article identifies statistically significant relationships between preventive practices and certain causes of TD. Further, it prioritizes the list of practices, PARs, and relationships regarding their level of importance for TD prevention based on the opinion of software practitioners. Conclusion . This work organizes TD prevention practices and PARs in a conceptual map and the relationships between practices and causes of TD in a Sankey diagram to help the visualization of the body of knowledge reported in this study.Keywords
Funding Information
- Coordenação de Aperfeiçoamento de Pessoal de Nível Superior - Brasil (CAPES) Finance Code 001
- Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq).
This publication has 60 references indexed in Scilit:
- Technical Debt Payment Practices and Rationales Behind Payment Avoidance in the Serbian IT Industry2022
- Technical debt payment and prevention through the lenses of software architectsInformation and Software Technology, 2021
- TestDCat 3.0: catalog of test debt subtypes and management activitiesSoftware Quality Journal, 2021
- 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
- Hearing the Voice of Software Practitioners on Causes, Effects, and Practices to Deal with Documentation Debt2020
- Technical Debt in Costa Rica: An InsighTD Survey ReplicationLecture Notes in Computer Science, 2019
- A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitionersInformation and Software Technology, 2018
- Investigating the Identification of Technical Debt Through Code Comment Analysis2017
- A systematic mapping study on technical debt and its managementJournal of Systems and Software, 2015
- The Sources and Approaches to Management of Technical Debt: A Case Study of Two Product Lines in a Middle-Size Finnish Software Company2014