Eder Pereira Santos
Manoel Mendonça
ABSTRACT
Context: The literature has proposed different approaches for Agile software development technical debt (ASD-TD) management, they are usually based on the point of view of software developers. Little is known about how project management practitioners actually perceive ASD-TD. Goal: To investigate how managers commonly discuss, experience, and manage ASD-TD, as well as roles, artifacts, and practices affected by ASD-TD extracted from Stack Exchange Project Management (SEPM). Method: We compiled 79 ASD-TD discussions from SEPM, and analyzed them quantitatively and qualitatively. Results: We identified 51 indicators used by managers to recognize ASD-TD items. The most commonly discussed types of TD are process and people debt. In addition, the Product Owner and Development Team are the most important roles with respect to ASD-TD. Sprint Backlog and Sprint Planning are the agile elements most affected by ASD-TD. We organized the TD indicators, roles involved, and agile elements affected by ASD-TD into a Mind Map. Conclusion: The perspective considered by project management practitioners to analyze the ASD-TD phenomenon is different from the one considered by other roles in agile software development.
- Muhammad Ahasanuzzaman, Muhammad Asaduzzaman, Chanchal K Roy, and Kevin A Schneider. 2016. Mining duplicate questions of stack overflow. In 13th Working Conference on Mining Software Repositories (MSR). 402–412.Google Scholar
Digital Library
- Digital Ai. 2021. 15th Annual State Of Agile Report. Retrieved April 13, 2022 from https://digital.ai/resource-center/analyst-reports/state-of-agile-reportGoogle Scholar
- Nicolli SR Alves, Thiago S Mendes, Manoel G de Mendonça, Rodrigo O Spínola, Forrest Shull, and Carolyn Seaman. 2016. Identification and management of technical debt: A systematic mapping study. Inf. Softw. Technol. 70(2016), 100–121.Google ScholarDigital Library
- Anton Barua, Stephen W Thomas, and Ahmed E Hassan. 2014. What are developers talking about? an analysis of topics and trends in stack overflow. Empir. Softw. Eng. 19, 3 (2014), 619–654.Google ScholarDigital Library
- Woubshet Nema Behutiye, Pilar Rodríguez, Markku Oivo, and Ayşe Tosun. 2017. Analyzing the concept of technical debt in the context of agile software development: A systematic literature review. Information and Software Technology 82 (2017), 139–158.Google ScholarCross Ref
- Terese Besker, Antonio Martini, and Jan Bosch. 2018. Managing architectural technical debt: A unified model and systematic literature review. Journal of Systems and Software 135 (2018), 1–16.Google ScholarDigital Library
- Vivyane Caires, Nicolli Rios, Johannes Holvitie, Ville Leppänen, Manoel Mendonça, and Rodrigo Spínola. 2018. Investigating the Effects of Agile Practices and Processes on Technical Debt - The Viewpoint of the Brazilian Software Industry. In 30th International Conference on Software Engineering and Knowledge Engineering (SEKE). 506–559.Google Scholar
- Ward Cunningham. 1992. The WyCash Portfolio Management System. In OOPSLA ’92 Addendum to the proceedings on Object-oriented programming systems, languages, and applications (Addendum). 29–30.Google Scholar
- Georgios Digkas, Nikolaos Nikolaidis, Apostolos Ampatzoglou, and Alexander Chatzigeorgiou. 2019. Reusing code from stackoverflow: the effect on technical debt. In 45th Euromicro Conference on Software Engineering and Advanced Applications (SEAA). 87–91.Google ScholarCross Ref
- Sávio Freire, Nicolli Rios, Boris Gutierrez, Darío Torres, Manoel Mendonça, Clemente Izurieta, Carolyn Seaman, and Rodrigo O. Spínola. 2020. Surveying Software Practitioners on Technical Debt Payment Practices and Reasons for Not Paying off Debt Items. In 20th Proceedings of the Evaluation and Assessment in Software Engineering (EASE). 210–219.Google ScholarDigital Library
- Sávio Freire, Nicolli Rios, Manoel Mendonça, Davide Falessi, Carolyn Seaman, Clemente Izurieta, and Rodrigo O. Spínola. 2020. Actions and Impediments for Technical Debt Prevention: Results from a Global Family of Industrial Surveys. In 35th Annual ACM Symposium on Applied Computing. ACM, 1548–1555.Google ScholarDigital Library
- Sávio Freire, Nicolli Rios, Boris Pérez, Camilo Castellanos, Darío Correal, Robert Ramač, Vladimir Mandić, Nebojša Taušan, Alexia Pacheco, Gustavo López, Manoel Mendonça, Clemente Izurieta, Davide Falessi, Carolyn Seaman, and Rodrigo Spínola. 2021. Pitfalls and Solutions for Technical Debt Management in Agile Software Projects. IEEE Software 38, 6 (2021), 42–49. https://doi.org/10.1109/MS.2021.3101990Google ScholarDigital Library
- Eliakim Gama, Sávio Freire, Manoel Mendonça, Rodrigo O Spínola, Matheus Paixao, and Mariela I Cortés. 2020. Using Stack Overflow to Assess Technical Debt Identification on Software Projects. In 34th Brazilian Symposium on Software Engineering (SBES). 730–739.Google ScholarDigital Library
- Eliakim Gama, Matheus Paixao, Emmanuel Sávio Silva Freire, and Mariela Inés Cortés. 2019. Technical Debt’s State of Practice on Stack Overflow: a Preliminary Study. In 19th Brazilian Symposium on Software Quality (SBQS). 228–233.Google ScholarDigital Library
- Felipe Gomes, Eder Pereira dos Santos, Sávio Freire, Manoel Mendonça, Thiago Souto Mendes, and Rodrigo Spínola. 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). 31–40.Google Scholar
- Isaac Griffith, Hanane Taffahi, Clemente Izurieta, and David Claudio. 2014. A simulation study of practical methods for technical debt management in agile software development. In Proceedings of the Winter Simulation Conference 2014. 1014–1025.Google Scholar
- Johannes Holvitie, Sherlock Licorish, Rodrigo Spínola, Sami Hyrynsalmi, Stephen MacDonell, Thiago Mendes, Jim Buchan, and Ville Leppänen. 2017. Technical Debt and Agile Software Development Practices and Processes: An Industry Practitioner Survey. Information and Software Technology in press (12 2017).Google Scholar
- https://www.scrum.org/. 2018. Scrum And eXtreme Programming (XP). Retrieved April 26, 2022 from https://www.scrum.org/resources/blog/scrum-and-extreme-programming-xpGoogle Scholar
- David Kavaler, Daryl Posnett, Clint Gibler, Hao Chen, Premkumar Devanbu, and Vladimir Filkov. 2013. Using and asking: Apis used in the android market and asked about in stackoverflow. In 5th International Conference on Social Informatics(SocInfo). 405–418.Google ScholarDigital Library
- Steve McConnell. 2008. Productivity Variations Among Software Developers and Teams: The Origin of 10x. 10x Software Development(2008).Google Scholar
- João Eduardo Montandon, Cristiano Politowski, Luciana Lourdes Silva, Marco Tulio Valente, Fabio Petrillo, and Yann-Gaël Guéhéneuc. 2021. What skills do IT companies look for in new developers? a study with Stack Overflow Jobs. Inf. Softw. Technol. 129(2021), 106429.Google ScholarCross Ref
- Stack Overflow. 1999. Extreme Programming (XP). Retrieved April 29, 2022 from https://www.agilealliance.org/glossary/xp/Google Scholar
- Eder Pereira, Felipe Gomes, Sávio Freire, Manoel Mendonça, Thiago Souto, and Rodrigo Spínola. 2022. Technical Debt on Agile Projects: Managers’ point of view at Stack Exchange. https://doi.org/10.5281/zenodo.6570913Google ScholarCross Ref
- Nicolli Rios, Manoel Gomes de Mendonça Neto, and Rodrigo Oliveira Spínola. 2018. A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitioners. Inf. Softw. Technol. 102(2018), 117–145.Google ScholarCross Ref
- Nicolli Rios, Manoel G. Mendonça, Carolyn B. Seaman, and Rodrigo O. Spínola. 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.Google Scholar
- Pilar Rodríguez, Mika Mäntylä, Markku Oivo, Lucy Ellen Lwakatare, Pertti Seppänen, and Pasi Kuvaja. 2019. Chapter Four - Advances in Using Agile and Lean Processes for Software Development. Advances in Computers, Vol. 113. Elsevier, 135–224.Google Scholar
- Ken Schwaber and Jeff Sutherland. 2011. The scrum guide. Scrum Alliance 21, 1 (2011).Google Scholar
- Carolyn B. Seaman. 1999. Qualitative methods in empirical studies of software engineering. IEEE TSE 25, 4 (1999), 557–572.Google ScholarDigital Library
- Subhasree Sengupta and Caroline Haythornthwaite. 2020. Learning with comments: An analysis of comments and community on Stack Overflow. In 53rd Hawaii International Conference on System Sciences (HICSS).Google ScholarCross Ref
- Amjed Tahir, Jens Dietrich, Steve Counsell, Sherlock Licorish, and Aiko Yamashita. 2020. A large scale study on how developers discuss code smells and anti-pattern in stack exchange sites. Inf. Softw. Technol. 125(2020), 106333.Google ScholarCross Ref
- Bogdan Vasilescu, Alexander Serebrenik, Prem Devanbu, and Vladimir Filkov. 2014. How social Q&A sites are changing knowledge sharing in open source software communities. In 17th Computer Supported Cooperative Work and Social Computing (CSCW). 342–354.Google Scholar
- Claes Wohlin, Per Runeson, Martin Höst, Magnus C Ohlsson, Björn Regnell, and Anders Wesslén. 2012. Experimentation in software engineering. Springer Science & Business Media.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 (05 2016).Google Scholar
Index Terms
- Technical Debt on Agile Projects: Managers’ point of view at Stack Exchange
Recommendations
Investigating the point of view of project management practitioners on technical debt: a preliminary study on stack exchange
TechDebt '22: Proceedings of the International Conference on Technical DebtContext: Technical debt (TD) can bring short-term benefits to software projects, but its presence is also associated with issues such as decreasing product quality. Recent literature has proposed indicator-based strategies for TD identification and ...
Technical debt and agile software development practices and processes: An industry practitioner survey
Highlights- Agile software development practices and processes have an effect on technical debt.
AbstractContext: Contemporary software development is typically conducted in dynamic, resource-scarce environments that are prone to the accumulation of technical debt. While this general phenomenon is acknowledged, what remains ...
A dependency taxonomy for agile software development projects
Agile software development is designed to achieve collaborative software development. A supporting pillar of collaboration is effective coordination, which is necessary to manage dependencies in projects. Understanding the dependencies arising in agile ...
Comments