Strategies for Reducing Technical Debt in Agile Teams

  • Marcelo M. BomfimJr.Email author
  • Viviane A. Santos
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 680)


As the Technical Debt (TD) management is not yet explicitly part of the software development process, teams need to seek strategies to reduce TD, as well as continue adding value to the customer business. This paper presents a case study of how agile teams deal with TD in their daily work, observing which strategies and TD reduction practices are used. Data were collected through six interviews with Scrum Masters and technical leaders of four different companies. The results suggest that the teams are concerned with the software quality and seek to pay their TD proactively and preventively. However, several factors influence the decision on prioritizing the TD payment, such as lack of test coverage, team engagement, among others.


Technical debt Technical debt payment Technical debt reduction Technical debt management Agile methods 



The authors thank all the companies and professionals who participated in this research.


  1. 1.
    Li, Z., Avgeriou, P., Liang, P.: A systematic mapping study on technical debt and its management. J. Syst. Softw. 101, 193–220 (2015)CrossRefGoogle Scholar
  2. 2.
    Seaman, C., Guo, Y., Izurieta, C., Cai, Y., Zazworka, N., Shull, F., Vetrò, A.: Using technical debt data in decision making: potential decision approaches. In: Proceeding of the 3rd International Workshop on Managing Technical Debt, pp. 45–48. IEEE (2012)Google Scholar
  3. 3.
    Spínola, R.O., Zazworka, N., Vetrò, A., Seaman, C., Shull, F.: Investigating technical debt folklore: shedding some light on technical debt opinion. In: Proceedings of the 4th International Workshop on Managing Technical Debt, pp. 1–7. IEEE (2013)Google Scholar
  4. 4.
    Kruchten, P., Nord, R.L., Ozkaya, I., Falessi, D.: Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt. ACM SIGSOFT Softw. Eng. Notes 38(5), 51–54 (2013)CrossRefGoogle Scholar
  5. 5.
    Codabux, Z. Williams, B.: Managing technical debt: an industrial case study. In: Proceedings of the 4th International Workshop on Managing Technical Debt, pp. 8–15. IEEE (2013)Google Scholar
  6. 6.
    Bavani, R.: Distributed agile, agile testing, and technical debt. IEEE Softw. 29(6), 28–33 (2012)CrossRefGoogle Scholar
  7. 7.
    Lim, E., Taksande, N., Seaman, C.: A balancing act: what software practitioners have to say about technical debt. Softw. IEEE 29(6), 22–27 (2012)CrossRefGoogle Scholar
  8. 8.
    Holvitie, J., Leppanen, V., Hyrynsalmi, S.: Technical debt and the effect of agile software development practices on it-an industry practitioner survey. In: Proceedings of the 6th International Workshop on Managing Technical Debt, pp. 35–42. IEEE (2014)Google Scholar
  9. 9.
    Krishna, V., Basu, A.: Minimizing technical debt: developer’s viewpoint. In: Proceedings of the ICSEMA 2012, Chennai (2012)Google Scholar
  10. 10.
    Kruchten, P.: Strategic management of technical debt: tutorial synopsis. In: Proceedings of the 12th International Conference on Quality Software (2012)Google Scholar
  11. 11.
    Laribbe, D.: Using agile techniques to pay back technical debt. MSDN Mag. (2009).
  12. 12.
    Morgenthaler, J.D., Gridnev, M., Sauciuc, R., Bhansali, S.: Searching for build debt: experiences managing technical debt at Google. In: Proceedings of the Third International Workshop on Managing Technical Debt, pp. 1–6. IEEE (2012)Google Scholar
  13. 13.
    Power, K.: Understanding the impact of technical debt on the capacity and velocity of teams and organizations: viewing team and organization capacity as a portfolio of real options. In: Proceedings of the 4th International Workshop on Managing Technical Debt, pp. 28–31. IEEE (2013)Google Scholar
  14. 14.
    Shriver, R.: Seven strategies for technical debt (2011).
  15. 15.
    Yin, R.: Case Study: Planning and Methods, 4 edn., 248 p. Bookman, Porto Alegre (2010)Google Scholar
  16. 16.
    Kruchten, P.: What colour is your backlog? Agile New England (2012).
  17. 17.
    Seaman, C., Guo, Y.: Measuring and monitoring technical debt. Adv. Comput. 82, 25–46 (2011)CrossRefGoogle Scholar
  18. 18.
    Beck, K., et al.: Manifesto for agile software development.
  19. 19.
    Falessi, D., Kruchten, P., Nord, R.L., Ozkaya, I.: Technical debt at the crossroads of research and practice: report on the fifth international workshop on managing technical debt. ACM SIGSOFT Softw. Eng. Notes 39(2), 31–33 (2014)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  1. 1.Institute of Technical Research of the State of São PauloSão PauloBrazil
  2. 2.Federal University of ParáTucuruíBrazil

Personalised recommendations