A Practical Guide for Establishing a Technical Debt Management Process (Preprint)
Fuente:
arXiv
Enregistré dans:
| Auteurs principaux: | , , |
|---|---|
| Format: | Preprint |
| Publié: |
2026
|
| Sujets: | |
| Accès en ligne: | |
| Tags: |
Ajouter un tag
Pas de tags, Soyez le premier à ajouter un tag!
|
| _version_ | 1866911482578468864 |
|---|---|
| author | Wiese, Marion Serwa, Kamila Bittner, Eva |
| author_facet | Wiese, Marion Serwa, Kamila Bittner, Eva |
| contents | Context. Technical Debt (TD) refers to short-term beneficial software solutions that impede future changes, making TD management essential. However, establishing a TD management (TDM) process is one of the most pressing concerns in practice. Goal. We plan to identify which previously researched TDM approaches are feasible in practice and what typical challenges emerge to create a guideline for establishing a TDM process. Method. We replicated our previously published action research study by conducting five workshops introducing TDM with two teams from different companies. To determine the feasibility of TDM approaches, we presented the teams with approaches for various TD activities and let them decide which to adopt. Overall, we conducted 19 workshops and retrospectives, analyzing 108 meetings (96 hours) over a 30-month period. Results. The adopted TD prevention strategies and documentation were similar in all teams. The teams utilized their respective backlogs and created a new backlog item type for TD, incorporating similar attributes such as interest, contagiousness, a resubmission date, and reminders to discuss drawbacks and risks. However, they used different prioritization approaches and deviating repayment methods. The teams had to overcome similar challenges during the establishment, which we list in this paper. Conclusions. We identified the TDM approaches used by all teams as a starting point for best practices. For challenges, we provided solutions or identified them as research gaps. Issue tracking system vendors should implement TD issue types employing the identified attributes. Finally, we created a white paper for practitioners to establish a TDM process based on our results. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2603_03085 |
| institution | arXiv |
| publishDate | 2026 |
| record_format | arxiv |
| spellingShingle | A Practical Guide for Establishing a Technical Debt Management Process (Preprint) Wiese, Marion Serwa, Kamila Bittner, Eva Software Engineering Context. Technical Debt (TD) refers to short-term beneficial software solutions that impede future changes, making TD management essential. However, establishing a TD management (TDM) process is one of the most pressing concerns in practice. Goal. We plan to identify which previously researched TDM approaches are feasible in practice and what typical challenges emerge to create a guideline for establishing a TDM process. Method. We replicated our previously published action research study by conducting five workshops introducing TDM with two teams from different companies. To determine the feasibility of TDM approaches, we presented the teams with approaches for various TD activities and let them decide which to adopt. Overall, we conducted 19 workshops and retrospectives, analyzing 108 meetings (96 hours) over a 30-month period. Results. The adopted TD prevention strategies and documentation were similar in all teams. The teams utilized their respective backlogs and created a new backlog item type for TD, incorporating similar attributes such as interest, contagiousness, a resubmission date, and reminders to discuss drawbacks and risks. However, they used different prioritization approaches and deviating repayment methods. The teams had to overcome similar challenges during the establishment, which we list in this paper. Conclusions. We identified the TDM approaches used by all teams as a starting point for best practices. For challenges, we provided solutions or identified them as research gaps. Issue tracking system vendors should implement TD issue types employing the identified attributes. Finally, we created a white paper for practitioners to establish a TDM process based on our results. |
| title | A Practical Guide for Establishing a Technical Debt Management Process (Preprint) |
| topic | Software Engineering |
| url | https://arxiv.org/abs/2603.03085 |