Szczegóły publikacji
Opis bibliograficzny
Business-driven technical debt management using Continuous Debt Valuation Approach (CoDVA) / Marek G. STOCHEL, Tomasz Borek, Mariusz R. Wawrowski, Piotr CHOŁDA // Information and Software Technology ; ISSN 0950-5849. — 2023 — vol. 164 art. no. 107333, s. 1–21. — Bibliogr. s. 19–21, Abstr. — Publikacja dostępna online od: 2023-09-21. — M. G. Stochel - dod. afiliacja: Motorola Solutions, Krakow
Autorzy (4)
- AGHStochel Marek G.
- Borek Tomasz
- Wawrowski Mariusz R.
- AGHChołda Piotr
Słowa kluczowe
Dane bibliometryczne
ID BaDAP | 149275 |
---|---|
Data dodania do BaDAP | 2023-11-10 |
Tekst źródłowy | URL |
DOI | 10.1016/j.infsof.2023.107333 |
Rok publikacji | 2023 |
Typ publikacji | artykuł w czasopiśmie |
Otwarty dostęp | |
Czasopismo/seria | Information and Software Technology |
Abstract
Context: Despite the increasing research on Technical Debt Management (TDM), there is still a need for empirical studies that take a comprehensive approach to managing Technical Debt (TD) and consider the business perspective. Objectives: We introduce an empirically evaluated methodology called Continuous Debt Valuation Approach (CoDVA), which improves business value, team productivity, and developer morale. Methods: CoDVA prioritizes TD against a predicted product roadmap, quantifying potential benefits based on their impact on the future state of the product and profitability of the investments. This approach enables a relative comparison among TD items and justifies a budget for TD repayment. The methodology was validated through a survey and a three-year-long case study on TDM practices driven by an engineering team responsible for development and maintenance of a telecommunication software. Results: The results of the study show that the CoDVA approach has a positive impact, as the perceived business value from TD refactorings grew by 27%, the engineering team velocity improved by 39%, predictability of the engineering team increased by 60%, the effort spent on product release stabilization decreased by 50%, and overall developer satisfaction increased in 86% of the cases. The majority of the developers found that the applied TDM strategy was beneficial in terms of technical decisions made, the ability to develop a new functionality, and experience while working with the product code. Conclusion: The results prove that the approach is expedient across realized business value, software engineering team productivity, and satisfaction of the engineers responsible for development and maintenance of the software product. © 2023 Elsevier B.V.