A proposed Approach for Managing Technical Debt in Software Projects

preprint OA: closed
📄 Open PDF View at publisher

Abstract

Technical debt (TD) is a metaphor for technical problems that are hidden from customers and end users but hinder development efforts during system evolution and future improvements. TD is frequently incurred due to tight budgets and timelines, which lead to financial, quality, and technical issues that make future maintenance more costly or impossible. Project management concentrates on external issues related to customer satisfaction and does not concentrate on system internal software quality defects and maintenance that be subject to future interest payments. In this paper, we highlight and investigate, in detail, an overview of the Technical Debt items for the software development team in SMEs. In addition, we present a TD management (TDM) approach with best practices for each step, provided with studied cases for applying the TDM approach at software industrial companies. The study shows that the proposed approach to measuring the impact of internal / external software quality leads to increased awareness of TD’s occurrence and provides processes to identify, prevent, monitor, prioritize, and repay TD to satisfy both software technical requirements and customer value and halt project failures and overruns. The analysis of applying our TDM approach leads to a better comprehension of TD contraction in selected software companies, improvements in team morale and motivation, and an increase in its maintainability.

My notes (saved in your browser only)

Citation neighborhood (no data yet)

We don't have any in-corpus citations linked to this paper yet. The paper's references may be in our DB but unresolved to ``paper_id`` (resolution happens at ingest when the cited DOI matches a row we already have). Run the cross-source citation reconcile pass to retry.

Source provenance

europepmc
last seen: 2026-05-19T01:45:01.086888+00:00
unpaywall
last seen: 2026-06-02T02:00:03.124865+00:00