# Integrating Interactive Detection of Code Smells into Scrum: Feasibility, Benefits, and Challenges
## 6 Online Validation: Insights from a Controlled Experiment
### Results
#### 6.3.3 Post-Experiment Results (Phase 3)
The results can be summarized as follows: (i) 55% fully agreed that the ID technique enabled the identification and understanding of code smell instances. They reported that the technique provided a more effective approach for detecting and understanding smells, allowing an in-depth analysis and a clearer view of problematic code; (ii) 33% partially agreed, indicating ID technique brought some benefit in identifying and understanding smells but also faced specific difficulties during the process. These participants emphasized that, despite some challenges, the technique still proved helpful in improving smell detection in the code; and (iii) 12% disagreed, stating that the ID technique did not facilitate the identification and understanding of code smell instances. These participants mentioned that the approach was unsuitable for their specific needs or did not notice a significant improvement compared to traditional smell detection methods. The participants expressed their opinions regarding the influence of applying the ID technique on the quality of the produced code. The results can be summarized as follows: (i) 67% fully agreed that using the ID technique positively influenced the quality of the produced code. They mentioned that the technique helped identify and fix code issues more efficiently, resulting in higher-quality code at the end of the development process; (ii) 25% partially agreed, acknowledging that the ID technique had some positive impact on the quality of the produced code but also noting that other factors, such as the team's experience and the project's context, played an essential role in overall code quality; (iii) 8% disagreed, stating that applying the ID technique did not have a positive influence on the quality of the produced code. They pointed out that other existing methods or practices were already in place to ensure code quality, and the ID technique did not bring additional improvements in this aspect. Next, the participants were asked to share the main benefits of using the proposed approach integrating ID into Scrum. The participants' responses can be grouped as Better identification of smells (62%), In-depth code understanding (54%), Early smell detection (45%), and Improved collaboration and communication (38%). Finally, the participants shared the challenges and difficulties encountered when applying the ID technique during development. Their responses can be summarized as follows: Learning curve (58%), Change resistance (50%), Cognitive overload (38%), and Integration with existing tools (30%). _Final Considerations_: The participants were asked if applying the proposed approach could contribute to communication and collaboration among team members. From the participant answer analysis, we determined that they emphasized that the proposed approach prioritizes communication, facilitates information exchange, and promotes collaborative work. They also highlighted that frequent meetings and interactions among team members in the Scrum approach foster alignment, engagement, and a conducive environment for teamwork, idea sharing, and solution finding. Finally, they pointed out that clear and open communication in Scrum with interactive detection enhances task understanding and minimizes communication gaps. Finally, participants were asked to share their recommendations regarding the use of the proposed approach for other development teams. Their responses can be summarized as follows: (1) Positive recommendation: 79% of the participants highly recommended using the approach for other development teams. They emphasized the observed benefits, such as the ease of identifying and understanding smell instances, the positive influence on the quality of the produced code, and the improved collaboration and communication among team members; (2) Neutral recommendation: 13% of the participants expressed impartial advice regarding using the approach.