Continuous Debt Valuation Approach (CoDVA) for Technical Debt Prioritization

Stochel, Marek G.; Chołda, Piotr; Wawrowski, Mariusz R.

doi:10.1109/seaa51224.2020.00066

Cited by 5 publications

(7 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…External validity addresses the generalisability, i.e., the extent to which the results and conclusions of a case study can be applied in different contexts. The CoDVA prioritisation method presented in this case study was already applied in another software domain, addressing prioritisation of technical debt in the large wireless telecommunication system [4]. The effectiveness of the approach was confirmed there as well; it was defined as the profitability of technical debt repayment (actual implementation of changes perceived as the most beneficial taking into account business financial perspective).…”

Section: Threats To Validitymentioning

confidence: 70%

“…Moreover, the technical debt term also indicates the set of all technical debt items associated with the system [2]. An atomic technical debt item (TDI) points to an immature software development artefact indicating the difference between its current and desired state [4]. The act of reducing technical debt is called refactoring [8] or remediation [2].…”

Section: Related Workmentioning

confidence: 99%

“…The Continuous Debt Valuation Approach (CoDVA) for technical debt prioritisation was introduced in our previous work [4]. For completeness of the overview, the most important facts are quoted in this subsection, and clarifications are added when some modifications were applied.…”

Section: Codvamentioning

confidence: 99%

“…Secondly, the prioritised business roadmap was discussed with the Product Managers. The differences between the CoDVA approach presented in our previous work [4] and the currently used one were briefly described earlier. The most important one referred to the refined valuation process.…”

Section: Technical Debt Identification and Prioritizationmentioning

confidence: 99%

“…This paper presents the initial results from an over one-year-long case study, and describes the application of the technical debt prioritisation technique to a product managing a fleet of connected devices for a video surveillance system. We decided to use the modified Continuous Debt Valuation Approach (CoDVA) technique for technical debt valuation and prioritisation, which we developed earlier [4]. Additionally, a prerequisite to successful application of CoDVA method was a robust technical debt identification step; in our case, it was executed according to the Wisdom of Crowds approach [5], which proved to be effective in other experiments [6].…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

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

Stochel

Wawrowski²,

Chołda

2022

Applied Sciences

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Section: Threats To Validitymentioning

confidence: 70%

Section: Related Workmentioning

confidence: 99%

Section: Codvamentioning

confidence: 99%

Section: Technical Debt Identification and Prioritizationmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations