# Integrating Interactive Detection of Code Smells into Scrum: Feasibility, Benefits, and Challenges
## 5 Offline Validation: Insights from a Focus Group
### Results
One expert (E8) mentioned that _\"...the only difficulty I observe at first would be adapting the teams to the ID technique\"_. Another expert (E5) stated that _\"...as the use of this type of integration is not widely used today, there would be an initial implementation barrier there\"_;2. Lack of knowledge and skills: Participants (four out of eight) emphasized a lack of knowledge and skills as a significant challenge in applying the ID technique. They pointed out that developers may detect code smells but may not possess the technical expertise to address them effectively. One expert (E1) mentioned that _\"...the smells can be detected, but the developer may not have enough technical knowledge to correct them\"_. Another expert (E4) stated that _\"...I believe that the greatest difficulty that will be encountered will be the resistance of the people who will use this approach\"_;
3. Organizational difficulties: Participants (four out of eight) highlighted organizational constraints as potential barriers to implementing the ID technique. These difficulties may include limited budgets, resource constraints, and company culture. One expert (E6) stated the following: _\"...I believe that as this is ongoing research, there may be resistance to change on the part of some organizations.\"_ Another expert (E7) mentioned that _\"...maybe the Product Owner can prioritize demands above the resolution proposed by ID\"_. In summary, the challenges associated with implementing the ID technique in Scrum include resistance to change, a lack of knowledge and skills, and organizational difficulties. Focus group participants noted that resistance may arise due to a lack of support from leadership and developers, as well as a preference for routine and comfort in following established development processes. Insufficient knowledge and skills can pose an initial barrier to implementing the ID technique, and the need for adequate training and capacity building is crucial. Additionally, organizational difficulties may involve limited budgets, resource availability, company culture, and the potential burden of tasks and projects on developers. Disadvantages: Upon analyzing the participants' responses, several categories of disadvantages associated with implementing the ID technique integrated into Scrum were identified and are detailed as follows:  
1. No disadvantages: a significant number of participants (five out of eight) stated they did not perceive any disadvantages. They did not identify specific drawbacks or negative aspects of integrating the ID technique into Scrum. Experts (E5 and E8) mentioned _\"...none\"_ and _\"...I couldn't see any disadvantages\"_, respectively;
2. Difficulty in adoption: some participants (three out of eight) acknowledged the potential difficulty in adopting the ID technique, particularly when the team is accustomed to using alternative approaches or development methods. They highlighted that resistance to change within the team could pose challenges. One expert (E1) stated the following: _\"...I believe that due to resistance to changes in the team, we may have difficulty with adoption\"_ and another expert (E2) mentioned that _\"...due to cultural issues of organizations, the difficulty of adoption can be faced\"_;
3. Tool dependency: a couple of participants (two out of eight) expressed concerns about the ID technique integrated into Scrum requiring specific tools and technologies, potentially limiting developers' options. They questioned why this approach should be used instead of the already established code quality tools. One expert (E4) asked: _\"...why use this approach and not an already established code quality tool?\"_, and another expert (E1) mentioned that _\"...we may have difficulty adopting the tool\"_. Most participants did not perceive any disadvantages in integrating the ID technique into Scrum. However, some experts mentioned potential challenges in adopting the approach, particularly in teams accustomed to different techniques or development methods.