# Integrating Interactive Detection of Code Smells into Scrum: Feasibility, Benefits, and Challenges
## 5 Offline Validation: Insights from a Focus Group
### Results
However, the participants who agreed with the statement likely perceived that the ID technique could enhance software quality by enabling the early detection and resolution of code issues before they can adversely impact the software's functionality. Another critical aspect of integrating the ID technique into Scrum is its adoption by software developers. In the survey, six participants agreed that ID integrated into Scrum could be quickly adopted by software development teams, while one was neutral, and one disagreed with this statement. This suggests that the ID can be successfully implemented in software development teams without significant challenges. A possible explanation is that Scrum is already widely adopted in many software development organizations, and the ID can be easily integrated into the existing processes. Using the Approach: The fourth part of the focus group analysis focused on gathering data regarding the participant perceptions of the demonstrated example of using the ID technique integrated into Scrum, including its benefits, advantages, and disadvantages. _Benefits_: by examining the responses, we identified several benefits of using the ID technique integrated into Scrum, detailed as follows:  
1. Improving code quality: All participants (eight out of eight) highlighted that integrating ID into Scrum directly enhances code quality. Their responses emphasized that continuous detection and correction of code smells result in greater productivity and a more manageable code. One expert (E1) stated that _\"...by using the ID technique integrated into the agile process, we will be able to maintain the code more easily because we will be detecting and correcting the smell, thus having greater productivity when carrying out the activities\"_. Another expert (E2) mentioned that _\"...the adoption of ID will improve quality due to continuous refactoring in software development activities\"_;
2. Improved product delivery: Most participants (six out of eight) acknowledged that integrating ID into Scrum helps improve product delivery. They noted that it enhances security, speed, and overall quality, enabling faster and more reliable software implementations. One expert (E2) stated that _\"...product delivery will be positively affected, as it will provide more security and speed of new implementations\"_. Another expert (E3) mentioned that _\"...the improvement in the delivery of the product at the end of the Sprint is noticeable\"_;
3. Easier maintenance: Participants (four out of eight) emphasized that integrating ID into Scrum leads to easier code maintenance, facilitating faster and more efficient changes. They expressed that continuous feedback accelerates the maintenance process and ensures cleaner and more organized code. One expert (E4) stated that it _\"...also ensures greater ease of maintenance in those codes that do not contain smells\"_. Another expert (E7) mentioned that _\"...because the feedback to the developer is in real time, it speeds up the maintenance process even more\"_. In summary, the experts highlighted that integrating ID into Scrum directly improves software quality, detects problems in the code earlier, and facilitates their correction before they escalate. It promotes the development of a cleaner and more organized code, enables frequent and error-free deliveries, simplifies code maintenance, and allows faster and more efficient changes. These benefits were observed in eight responses for improved code quality, six for improved product delivery, and four for easier maintenance. Difficulties: After a comprehensive analysis of the participant responses, the scientific investigation revealed a series of challenges pertaining to the seamless integration of the ID technique into Scrum, which are enumerated below:  
1. Resistance to change: most participants (seven out of eight) expressed concerns about resistance to change when adopting the ID technique. They highlighted that this resistance could stem from a lack of support from leadership or developers.