Technical Debt Guild

Detofeno, Thober; Reinehr, Sheila; Malucelli, Andreia

doi:10.1145/3493244.3493271

Cited by 3 publications

(1 citation statement)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Other papers presented novel frameworks or models for managing technical debt during the software development process with a more holistic perspective, including several process elements or phases. For example, some authors propose creating a guild, a group of people that help address TD management and guide its payment (Detofeno et al, 2021). Moreover, another paper mentioned encouraging and rewarding incentives for developers to manage technical debt (Besker et al, 2022).…”

Section: Technical Debt Management (Rq3)mentioning

confidence: 99%

Identification and Management of Technical Debt

Murillo,

López,

Spínola

et al. 2023

JSERD

View full text Add to dashboard Cite

Technical debt is a concept used to describe the lack of good practices during software development, leading to several problems and costs. Identification and management strategies can help reduce these difficulties. In a previous study, Alves et al. (2016) analyzed the research landscape of such strategies from 2010 to 2014. This paper replicates and updates their study to explore the evolution of technical debt identification and management research landscape over a decade, including literature from 2010 until 2022. We analyzed 117 papers from the ACM Digital Library, IEEE Xplore, Science Direct, and Springer Link. Newly suggested strategies include automatically identifying admitted debt in comments, commits, and source code. Between 2015 and 2022, more empirical evaluations have been performed, and the general research focus has changed to a more holistic approach. Therefore, the research area evolved and reached a new level of maturity compared to previous results from Alves et al. (2016). Not only are code aspects considered for technical debt, but other aspects have also been investigated (e.g., models for the development process).

show abstract

Section: Technical Debt Management (Rq3)mentioning

confidence: 99%

Identification and Management of Technical Debt

Murillo,

López,

Spínola

et al. 2023

JSERD

View full text Add to dashboard Cite

show abstract

Investigating Communities of Practice in Large-Scale Agile Software Development: An Interview Study

Tobisch,

Schmidt,

Matthes

2024

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Nowadays, responsiveness is essential to be competitive, particularly in software development. Traditional methods face limitations in meeting this demand for agility, which led to the rise of agile practices. Inspired by their success in small projects, organizations have begun to use agile methods in larger contexts. However, scaling agile practices introduces complexities and requires coordinating teams, managing dependencies, and collaboration. Communities of Practices (CoPs) are argued to address these issues and support organizations in adopting agile methods at scale. Still, empirical insights into the establishment of CoPs in scaled agile settings are limited. This study fills this gap by conducting expert interviews, exploring why organizations applying agile methods at scale adopt CoPs, and examining their characteristics. Our key findings include that, next to benefit from known advantages of CoPs, like knowledge sharing, organizations establish them to foster empowerment, strengthen alignment, and drive their agile transformation. Moreover, CoPs focus not only on agile but also on classical themes such as architecture. Communities are not necessarily established bottom-up but are often initiated by management, e.g., to empower employees. In general, CoPs are accepted by management and play an essential role in decision-making.

show abstract