Managing Technical Debt Research Articles

Lean and Agile Software Development for Managing Technical Debt on A Large-scale Software: A Systematic Literature Review

Agile methodologies are employed by software development teams for collaboration and adapting to changing requirements. However, this flexibility may lead to technical debt (TD), causing potential bugs in the long term. Lean principles, focusing on waste elimination and continuous process improvement, can be applied to manage TD in agile software development. This research conducts a systematic literature review on using lean and agile methodologies for TD management. The review identifies 34 papers, categorizing TD types, pinpointing lean and agile principles, and aligning technical debt categories with suitable lean and agile principles. Additionally, three existing technical debt management frameworks are identified: the TAP framework, the LTD framework, and the CoDVA framework. The study concludes that integrating lean principles into agile software development assists organizations in effectively managing technical debt. Furthermore, the research offers insights into selecting the most suitable TD management framework based on an organization's needs and available resources.

The role of awareness and gamification on technical debt management

Managing technical debt and developing easy-to-maintain software are very important aspects for technological companies. Integrated development environments (IDEs) and static measurement and analysis tools are used for this purpose. Meanwhile, gamification also is gaining popularity in professional settings, particularly in software development.

Reproducibility in the technical debt domain

Abstract Context It is crucial to understand how reproducible the measurement results in the scientific publications are, as reproducibility is one of the cornerstones of engineering. Objective The goal of this study is to investigate the scientific publications presented at the premier technical debt conferences by understanding how reproducible the reported findings are. Method We conducted a systematic literature review of 135 unique papers published at the “International Workshop on Managing Technical Debt” and the “International Conference on Managing Technical Debt”, the premier scientific conference series on technical debt. Results Only 44 of the investigated 135 papers presented numerical evidence and only 5 papers listed the tools, the availability of the tools, and the version of the tools used. For the rest of the papers additional information would have been needed for the potential reproducibility. One of the published papers even referred to a pornographic site as a source of a toolset for empirical research.

Technical Debt in Agile Development

We report on the Ninth International Workshop on Managing Technical Debt, collocated with the 18th International Conference on Agile Software Development (XP 2017) in Cologne. The technical debt research community continues to expand through collaborations of industry, tool vendors, and academia. The theme of this year's workshop was on technical debt in agile development. Presentations and discussion centered on the topics: technical debt at the code level, architectural technical debt assessment, agile approaches and their impact on technical debt management, and selling the business case of technical debt management.

Technical Debt

We report here on the Eighth International Workshop on Managing Technical Debt, collocated with the International Conference on Software Maintenance and Evolution (ICSME 2016). The technical debt research community continues to expand through collaborations of industry, tool vendors, and academia. The major themes of discussion this year indicate convergence on a common definition on technical debt and its elements which drive the maturation of a research roadmap, demonstrating that managing technical debt is a mainstream topic in software engineering research bringing empirical analysis, data science, software design and architecture analysis and automation among other challenges together.

Technical Debt

Increasingly software engineers use the metaphor of technical debt to communicate issues related to the growing cost of change. In this article, we report on the Seventh Workshop on Managing Technical Debt (MTD 2015), held in Bremen, Germany, on October 2, 2015, collocated with the International Conference on Software Maintenance and Evolution (ICSME). The 30 workshop participants from industry and academia engaged in lively discussions, which helped clarify issues, refine questions, and promote common understanding about technical debt in software.

Technical Debt

We report here on the Sixth International Workshop on Managing Technical Debt, collocated with the International Conference on Software Maintenance and Evolution (ICSME 2014). The major themes of discussion this year indicate a growing maturity in this area of investigation and the desire to move beyond definitional issues to impact.

Technical debt at the crossroads of research and practice

Increasingly, software developers and managers use the metaphor of technical debt to communicate key trade-offs related to release and quality issues. We report here on the Fifth International Workshop on Managing Technical Debt, collocated with the Seventh International Symposium on Empirical Software Engineering and Measurement (ESEM 2013). The workshop participants reiterated the usefulness of the metaphor, shared emerging practices used in software development organizations, and emphasized the need for more research and better means for sharing emerging practices and results.