ABSTRACT
The interest of Technical Debt (TD) is difficult to calculate, especially on a project level. Current approaches are based on fine-grain issue assessment, but there is no evidence about how TD is assessed on a project level. A few tools use an aggregation function that sum the TD issues on a project level.
We conducted a multiple case-study on four different projects. We asked the project teams to assess the TD both on an issue level and on a project level. We also asked the product manager and a senior developer to assess the TD on a project level. We found that the function mapping the interest of TD to a project overall is not the sum of issue-level TD.
We report the quantitative results of the performed experiment and we also developed a qualitative explanation of the results based on interviews with the development team. This paper represents a first step towards assessing the interest of TD at a project level.
- Areti Ampatzoglou, Apostolos Ampatzoglou, Alexander Chatzigeorgiou, and Paris Avgeriou. 2015. The financial aspect of managing technical debt: A systematic literature review. Information and Software Technology 64 (Aug. 2015), 52--73. Google ScholarDigital Library
- P. Avgeriou, P Kruchten, I. Ozkaya, and C. Seaman. Managing Technical Debt in Software Engineering (Dagstuhl Seminar 16162).Google Scholar
- ISO International Organization for Standardization. 2015. System and software quality models. (2015). http://www.iso.org/iso/catalogue_detail.htm?csnumber=52075Google Scholar
- Yuepu Guo and Carolyn Seaman. 2011. A Portfolio Approach to Technical Debt Management. In Proceedings of the 2Nd Workshop on Managing Technical Debt. ACM, New York, NY, USA, 31--34. Google ScholarDigital Library
- Yuepu Guo, Carolyn Seaman, Rebeka Gomes, Antonio Cavalcanti, Graziela Tonin, Fabio QB Da Silva, AndrÃl' Luis M. Santos, and Clauirton Siebra. 2011. Tracking technical debt: An exploratory case study. In Software Maintenance (ICSM), 2011 27th IEEE International Conference on. 528--531.Google ScholarDigital Library
- A. Martini, T. Besker, and J. Bosch. 2016. The Introduction of Technical Debt Tracking in Large Companies. In accepted at APSEC 2016. Hamilton, New Zealand. Google ScholarCross Ref
- Antonio Martini and Jan Bosch. 2016. An Empirically Developed Method to Aid Decisions on Architectural Technical Debt Refactoring: AnaConDebt. In Proceedings of the 38th International Conference on Software Engineering Companion (ICSE'16). ACM, New York, NY, USA, 31--40. Google ScholarDigital Library
- A. Martini and J. Bosch. 2017. The Magnificent Seven: Towards a Systematic Estimation of the Technical Debt Interest. In submitted at MTD 2017.Google Scholar
- Ariadi Nugroho, Joost Visser, and Tobias Kuipers. 2011. An empirical model of technical debt and interest. In Proceedings of the 2nd Workshop on Managing Technical Debt (MTD '11). ACM, New York, NY, USA, 1--8. Google ScholarDigital Library
- Klaus Schmid. 2013. A formal approach to technical debt decision making. In Proceedings of the 9th international ACM Sigsoft conference on Quality of software architectures. ACM, 153--162. http://dl.acm.org/citation.cfm?id=2465492 Google ScholarDigital Library
- C. Seaman, Yuepu Guo, Nico Zazworka, F. Shull, C. Izurieta, Yuanfang Cai, and A. Vetro. 2012. Using technical debt data in decision making: Potential decision approaches. In 2012 Third International Workshop on Managing Technical Debt (MTD). 45--48. Google ScholarCross Ref
- Jesse Yli-Huumo, Andrey Maglyas, and Kari Smolander. 2016. How do software development teams manage technical debt? An empirical study. Journal of Systems and Software 120 (Oct. 2016), 195--218. Google ScholarDigital Library
Index Terms
- Technical debt interest assessment: from issues to project
Recommendations
The magnificent seven: towards a systematic estimation of technical debt interest
XP '17: Proceedings of the XP2017 Scientific WorkshopsThe interest of Technical Debt is difficult to assess. The negative effects (severity) of Technical Debt might depend on the context of the organization and the estimations might be subjective. There is a need for assessing Technical Debt interest in a ...
How SonarQube-identified technical debt is prioritized: An exploratory case study
Abstract Context:Repaying all technical debt (TD) in a system may be unviable, as there is typically a shortage of resources allocated for TD repayment activities. Therefore, TD prioritization is essential to best allocate such ...
Understanding the impact of technical debt in coding and testing: an exploratory case study
SER&IP '16: Proceedings of the 3rd International Workshop on Software Engineering Research and Industrial PracticeTechnical Debt (TD) refers to the long-term consequences of shortcuts taken during different phases of software development life cycle. Lack of attention to monitoring and managing testing and development debt can contribute to unexpectedly large cost ...
Comments