# Integrating Interactive Detection of Code Smells into Scrum: Feasibility, Benefits, and Challenges
###### Abstract  
(Context) Code smells indicate poor coding practices or design flaws, suggesting deeper software quality issues. While addressing code smells promptly improves software quality, traditional detection techniques often fail in continuous detection during software development. (Problem Statement) More recently, Interactive Detection (ID) technique has been proposed, enabling the detection of code smells continuously. Although the use of this technique by developers and organizations is promising, there are no practical recommendations for its use in the context of software development. (Goal) The objective of this study was to propose and evaluate the integration of ID into the widely adopted Scrum framework for agile software development. (Method) To achieve this objective, we utilized a mixed-method approach that combined a comprehensive literature review and expert knowledge to propose the integration. Furthermore, we conducted a focus group and a controlled experiment involving software development activities to evaluate this integration. (Results) The findings revealed that this integration significantly benefitted software development, such as early detection of code smells, increased effectiveness in code smell detection, and improved code quality. These findings shed light on the potential benefits of adopting this integration, offering valuable insights for developers and researchers. (Conclusions) This research emphasized the importance of continuous code smell detection as an integral part of agile development and opened avenues for further research in code quality management within agile methodologies. code smell; detection techniques; agile software development; empirical evaluation 2023  
[PERSON], [PERSON], [PERSON], [PERSON], [PERSON], [PERSON], [PERSON], [PERSON], [PERSON], [PERSON], [PERSON]  
Interactive Detection (ID) techniques have been proposed to help reveal smell instances in code fragments without an explicit request from the developer [7]. In contrast to NID, the ID technique allows developers interact with smelly code elements as they edit or browse their program statements [6]. This feature can help the developer be aware of new occurrences of code smells as soon as they are introduced [10]. Empirical studies show that the sooner code smells are removed, the less effort and time is spent on this activity [2; 11]. The Scrum framework has gained widespread adoption in agile software development due to its flexible and iterative approach [12]. Scrum promotes collaboration, adaptability, and continuous improvement, aligning well with the dynamic nature of software development projects [13]. By integrating the ID technique, which enables continuous detection of code smells, into the Scrum framework, developers can address code smells promptly, resulting in enhanced software quality. Despite the popularity of the Scrum framework, integrating the ID technique into Scrum remains relatively unexplored [6]. The lack of comprehensive studies and practical guidelines on integrating continuous code smell detection into Scrum creates a knowledge gap within the software engineering community. Integrating ID into Scrum addresses continuous code smell detection challenges during agile development [10]. It provides just-in-time feedback, enabling early identification and resolution of code quality issues [14]. ID fosters collaborative development and supports a culture of continuous inspection and improvement, promoting high code quality and software maintainability in an agile environment [3; 15; 16]. In summary, the integration of ID into Scrum applies to a wide range of scenarios within agile software development (e.g., Code Review, Collaborative Development, Large and Complex Software Systems, and Legacy Code Refactoring), helping development teams to proactively address code quality issues and maintain high software standards throughout the development lifecycle. The primary goal of this study is to propose an approach that integrates the ID technique into Scrum to enhance software quality.