Szczegóły publikacji
Opis bibliograficzny
Technical debt prioritization in telecommunication applications: why the actual refactoring deviates from the plan and how to remediate it? : case study in the COVID era / Marek G. STOCHEL, Mariusz R. Wawrowski, Piotr CHOŁDA // Applied Sciences (Basel) [Dokument elektroniczny]. — Czasopismo elektroniczne ; ISSN 2076-3417. — 2022 — vol. 12 iss. 22 art. no. 11347, s. 1-19. — Wymagania systemowe: Adobe Reader. — Bibliogr. s. 18-19, Abstr. — Publikacja dostępna online od: 2022-11-08. — M. Stochel - dod. afiliacja: Motorola Solutions
Autorzy (3)
- AGHStochel Marek G.
- Wawrowski Mariusz R.
- AGHChołda Piotr
Słowa kluczowe
Dane bibliometryczne
| ID BaDAP | 143637 |
|---|---|
| Data dodania do BaDAP | 2022-11-18 |
| Tekst źródłowy | URL |
| DOI | 10.3390/app122211347 |
| Rok publikacji | 2022 |
| Typ publikacji | artykuł w czasopiśmie |
| Otwarty dostęp |  |
| Creative Commons | |
| Czasopismo/seria | Applied Sciences (Basel) |
Abstract
This paper focuses on application of a technical debt prioritisation technique in telecommunication software managing a fleet of devices for a video surveillance system. Technical debt for this application was gathered, categorised and prioritised according to the Continuous Debt Valuation Approach (CoDVA), previously proposed by the authors. The following research question was posed: Is prioritising technical debt reduction based on CoDVA effective (i.e., executed as per plan, bringing tangible benefits)? The outbreak of COVID-19 pandemic caused unprecedented disturbance to the engineering organisations worldwide, therefore the technical debt identification phase had to be adapted to cope with a switch to forced working-from-home mode. This was achieved by applying the Wisdom of Crowds method, ensuring broad participation of engineers, and providing a fairly complete picture of the accrued technical debt. Nevertheless, the actual technical debt reduction activities did not follow exactly the expected guidelines. The three main causes of this phenomenon were discovered: continuous refactoring approach, sizing of technical debt items, and the broadened scope of refactoring activities. Therefore, as a result of this case study we propose to adopt a specific broadened definition of technical debt and follow a few rules for defining its scope and granularity.
