Investigating the Point of View of Project Management Practitioners on Technical Debt - A Study on Stack Exchange
DOI:
https://doi.org/10.5753/jserd.2023.3191Keywords:
Technical debt, Project management practitioners, Stack ExchangeAbstract
Context: Technical debt (TD) can bring short-term benefits to software projects, but its presence is associated with issues such as decreasing product quality. Recent literature has proposed various approaches for identifying and managing TD, but most of them focus on the software developers’ point of view. Little is known about how project management practitioners perceive and manage TD items. Goal: This work aims to investigate how project management practitioners discuss and experience TD. Method: To achieve this goal, our work mines, curates, and selects a total of 108 TD-related discussions on the Stack Exchange Project Management (SEPM) Q&A site. These discussions amount to 547 posts and 882 text comments on the subject. We analyze this data set quantitatively and qualitatively, using open coding to derive TD types, indicators, and management practices. Results: We identified 74 indicators used for recognizing debt items and 126 TD management practices. The types of debt most discussed at SEPM are process and people debts. This contradicts studies done with developers where code and design debts are most discussed. Conclusion: The perspective considered by project management practitioners to analyze the TD phenomenon is different from the one considered by other roles in the software development process. Our work organizes the identified TD indicators and management practices into a Sankey diagram, which may assist TD management practitioners and serve as guidance for future research on the subject.
Downloads
References
Agile_Alliance (1999). Extreme programming (XP). Available at: [link] [Last accessed: April 29, 2022].
Ahasanuzzaman, M., Asaduzzaman, M., Roy, C. K., and Schneider, K. A. (2016). Mining duplicate questions of stack overflow. In 2016 IEEE/ACM 13th Working MSR, pages 402–412. IEEE.
Ai, D. (2021). 15th annual state of agile report.
Alves, N. S., Mendes, T. S., de Mendonça, M. G., Spínola, R. O., Shull, F., and Seaman, C. (2016). Identification and management of technical debt: A systematic mapping study. Inf. Softw. Technol., 70:100–121.
Barua, A., Thomas, S. W., and Hassan, A. E. (2014). What are developers talking about? an analysis of topics and trends in stack overflow. Empir. Softw. Eng., 19(3):619–654.
Behutiye, W. N., Rodríguez, P., Oivo, M., and Tosun, A. (2017). Analyzing the concept of technical debt in the context of agile software development: A systematic literature review. Information and Software Technology, 82:139–158.
Berenguer, C., Borges, A., Freire, S., Rios, N., Ramač, R., Taušan, N., Pérez, B., Castellanos, C., Correal, D., Pacheco, A., López, G., Mendonça, M., Falessi, D., Seaman, C., Mandić, V., Izurieta, C., and Spínola, R. (2023). Investigating the relationship between technical debt management and software development issues. Journal of Software Engineering Research and Development, 11(1):3:1 – 3:21.
Bohnet, J. and Döllner, J. (2011). Monitoring code quality and development activity by software maps. In Proceedings of the 2nd Workshop on Managing Technical Debt, MTD ’11, pages 9–16, New York, NY, USA. ACM.
C., S. and R., S. (2013). Managing technical debt. In (Short Course) XVII Brazilian Symposium on Software Quality, Salvador, Brazil.
Codabux, Z. and Williams, B. (2013). Managing technical debt: An industrial case study. In Proceedings of the 4th International Workshop on Managing Technical Debt, MTD ’13, pages 8–15, Piscataway, NJ, USA. IEEE Press.
Digkas, G., Nikolaidis, N., Ampatzoglou, A., and Chatzigeorgiou, A. (2019). Reusing code from stackoverflow: the effect on technical debt. In 45th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), pages 87–91.
dos Santos, E. P., Gomes, F., Freire, S., Mendonça, M., Mendes, T., and Spínola, R. (2022). Technical debt on agile projects: Managers point of view at stack exchange. In SBQS 2022 - Research Track.
Freire, S., Rios, N., Gutierrez, B., Torres, D., Mendonça, M., Izurieta, C., Seaman, C., and Spínola, R. O. (2020a). Surveying software practitioners on technical debt payment practices and reasons for not paying off debt items. EASE ’20, page 210–219. ACM.
Freire, S., Rios, N., Mendonça, M., Falessi, D., Seaman, C., Izurieta, C., and Spínola, R. O. (2020b). Actions and Impediments for Technical Debt Prevention: Results from a Global Family of Industrial Surveys, page 1548–1555. ACM.
Freire, S., Rios, N., Pérez, B., Castellanos, C., Correal, D., Ramač, R., Mandić, V., Taušan, N., López, G., Pacheco, A., Mendonça, M., Falessi, D., Izurieta, C., Seaman, C., and Spínola, R. (2023). Software practitioners’ point of view on technical debt payment. Journal of Systems and Software, 196:111554.
Gama, E., Freire, S., Mendonça, M., Spínola, R. O., Paixão, M., and Cortés, M. I. (2020). Using stack overflow to assess technical debt identification on software projects. In 34th Brazilian Symposium on Software Engineering (SBES), pages 730–739.
Gama, E., Paixao, M., Freire, E. S. S., and Cortés, M. I. (2019). Technical debt’s state of practice on stack overflow: a preliminary study. In Proceedings of the XVIII SBQS, pages 228–233.
Garousi, V., Felderer, M., and Mäntylä, M. (2019). Guidelines for including grey literature and conducting multivocal literature reviews in software engineering. Information and Software Technology, 106(2):101–121.
Gomes, F., dos Santos, E. P., Freire, S., Mendonça, M., Mendes, T. S., and Spínola, R. (2022). Investigating the point of view of project management practitioners on technical debt - a preliminary study on stack exchange. In 2022 IEEE/ACM International Conference on Technical Debt (TechDebt), pages 31–40.
Greening, D. R. (2013). Release duration and enterprise agility. In System Sciences (HICSS), 2013 46th Hawaii International Conference on, pages 4835–4841.
Guo, Y. and Seaman, C. (2011). A portfolio approach to technical debt management. In Proceedings of the 2Nd Workshop on Managing Technical Debt, MTD ’11, pages 31–34, New York, NY, USA. ACM.
Holvitie, J., Licorish, S., Spínola, R., Hyrynsalmi, S., MacDonald, S., Mendes, T., Buchan, J., and Leppänen, V. (2017). Technical debt and agile software development practices and processes: An industry practitioner survey. Information and Software Technology, in press.
Izurieta, C., Vetró, A., Zazworka, N., Cai, Y., Seaman, C., and Shull, F. (2012). Organizing the technical debt landscape. In Proceedings of the Third International Workshop on Managing Technical Debt, MTD ’12, pages 23–26, Piscataway, NJ, USA. IEEE Press.
Kavaler, D., Posnett, D., Gibler, C., Chen, H., Devanbu, P., and Filkov, V. (2013). Using and asking: APIs used in the android market and asked about in stackoverflow. In SocInfo, pages 405–418. Springer.
Klinger, T., Tarr, P., Wagstrom, P., and Williams, C. (2011). An enterprise perspective on technical debt. In Proceedings of the 2nd Workshop on Managing Technical Debt (MTD), pages 35–38.
Kruchten, P., Nord, R. L., and Ozkaya, I. (2012). Technical debt: From metaphor to theory and practice. Ieee software, 29(6):18–21.
Li, Z., Avgeriou, P., and Liang, P. (2015). A systematic mapping study on technical debt and its management. Journal of Systems and Software, 101:193–220.
Lupton, R. C. and Allwood, J. M. (2017). Hybrid Sankey diagrams: Visual analysis of multidimensional data for understanding resource use. Resources, Conservation and Recycling, 124:141–151.
McConnell, S. (2008). Productivity variations among software developers and teams: The origin of 10x. 10x Software Development.
Montandon, J. E., Politowski, C., Silva, L. L., Valente, M. T., Petrillo, F., and Guéhéneuc, Y.-G. (2021). What skills do IT companies look for in new developers? a study with stack overflow jobs. Inf. Softw. Technol., 129:106429.
Partogi, J. (2018). Scrum and extreme programming (XP). Available: [link] [Last accessed: April 26, 2022].
Rios, N., de Mendonça Neto, M. G., and Spínola, R. O. (2018). A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitioners. Inf. Softw. Technol., 102:117–145.
Rios, N., Freire, S., Perez, B., Castellanos, C., Correal, D., Mendonca, M., Falessi, D., Izurieta, C., Seaman, C. B., and Spinola, R. O. (2021). On the relationship between technical debt management and process models. IEEE Software, 38(5):56–64.
Rios, N., Mendonça, M. G., Seaman, C. B., and Spínola, R. O. (2019). Causes and effects of the presence of technical debt in agile software projects. In 25th Americas Conference on Information Systems, AMCIS 2019, Cancún, Mexico, August 15-17, 2019. Association for Information Systems.
Rosen, C. and Shihab, E. (2016). What are mobile developers asking about? a large scale study using stack overflow. Empir. Softw. Eng., 21(3):1192–1223.
Schwaber, K. and Sutherland, J. (2011). The scrum guide. Scrum Alliance, 21(1).
Seaman, C. B. (1999). Qualitative methods in empirical studies of software engineering. IEEE TSE, 25(4):557–572.
Sengupta, S. and Haythornthwaite, C. (2020). Learning with comments: An analysis of comments and community on stack overflow. In 53rd HICSS.
Snipes, W., Robinson, B., Guo, Y., and Seaman, C. (2012). Defining the decision factors for managing defects: A technical debt perspective. In Proceedings of the Third International Workshop on Managing Technical Debt, MTD ’12, pages 54–60, Piscataway, NJ, USA. IEEE Press.
Stack_Overflow (2021). 2021 developer survey. Available at: [link] [Last accessed: January 2, 2022].
Tahir, A., Dietrich, J., Counsell, S., Licorish, S., and Yamashita, A. (2020). A large scale study on how developers discuss code smells and anti-pattern in stack exchange sites. Inf. Softw. Technol., 125:106333.
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., and Wesslén, A. (2012). Experimentation in software engineering. Springer Science & Business Media.
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2023 Felipe Gomes, Eder Santos, Sávio Freire, Thiago Souto Mendes, Manoel Mendonça, Rodrigo Spínola
This work is licensed under a Creative Commons Attribution 4.0 International License.
