2023-11-092023-11-092021-08-09https://ieeexplore.ieee.org/document/95089820740-7459https://hdl.handle.net/10669/90345Technical 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.engacceso abiertoTechnical debt (TD)SOFTWARE DEVELOPMENTSoftware qualitySoftware maintenanceSoftware prioritizationTechnical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced PractitionersartÃculo original10.1109/MS.2021.3103121