skip to main content
10.1145/3120459.3120467acmotherconferencesArticle/Chapter ViewAbstractPublication PagesxpConference Proceedingsconference-collections
short-paper

The magnificent seven: towards a systematic estimation of technical debt interest

Authors Info & Claims
Published:22 May 2017Publication History

ABSTRACT

The 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 more systematic way.

Based on the results of previous research, we have developed and used a lightweight tool, AnaConDebt, to assess the severity of the interest of 9 Technical Debt items with the stakeholders in 3 Agile teams. The systematic and semi-automatic assessment of seven factors and their growth has been compared to the stakeholders' intuitive estimations.

The results show that the outcome of the tool is very close to the estimation given by the stakeholders. The implications are that, if further data support the hypothesis, the severity of the interest can be systematically assessed by the stakeholders by estimating only seven factors in a cost-effective manner with acceptable results.

References

  1. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  2. P. Avgeriou, P Kruchten, I. Ozkaya, and C. Seaman. Managing Technical Debt in Software Engineering (Dagstuhl Seminar 16162).Google ScholarGoogle Scholar
  3. ISO International Organization for Standardization. 2015. System and software quality models. (2015). http://www.iso.org/iso/catalogue_detail.htm?csnumber=52075Google ScholarGoogle Scholar
  4. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  5. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  6. Philippe Kruchten, R.L. Nord, and I. Ozkaya. 2012. Technical Debt: From Metaphor to Theory and Practice. IEEE Software 29, 6 (2012), 18--21.Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. 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 ScholarGoogle ScholarCross RefCross Ref
  8. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  9. Antonio Martini and Jan Bosch. 2016. A Multiple Case Study of Continuous Architecting in Large Agile Companies: Current Gaps and the CAFFEA Framework. IEEE, 1--10.Google ScholarGoogle Scholar
  10. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  11. 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 ScholarGoogle ScholarCross RefCross Ref
  12. 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. 05.018 Google ScholarGoogle ScholarCross RefCross Ref

Index Terms

  1. The magnificent seven: towards a systematic estimation of technical debt interest

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Other conferences
      XP '17: Proceedings of the XP2017 Scientific Workshops
      May 2017
      124 pages
      ISBN:9781450352642
      DOI:10.1145/3120459

      Copyright © 2017 ACM

      Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 22 May 2017

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • short-paper

      Acceptance Rates

      Overall Acceptance Rate11of15submissions,73%

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader