# FRAMUX-EV: A Framework for Evaluating User Experience in Agile Software Development
## 7 Discussions
### Opportunities to Improve FRAMUX-EV  
As presented in Section 6.2, the experiment conducted to validate the UX components of FRAMUX-EV provided valuable insights and findings on future actions that should be implemented. Suggestions for both UX events and UX artifacts highlight opportunities to improve utility and facilitate integration, so that the framework continues to evolve and can be used to integrate and support the UX evaluation into agile software development.  
Thus, several changes have been identified based on the feedback gathered from experts. For UX artifacts (see Table 10), improvements will include providing more detailed explanations for all UX artifacts, with particular emphasis on the UX design system, UX personas, UX roles and responsibilities, and UX evaluation repository, to avoid confusion and highlight their utility. The feedback also suggested including a consideration for each UX artifact to indicate that; depending on the team's capacity, these could be specified in more or less detail.  
On the other hand, for UX events (see Table 11), modifications include adjusting the frequency of three events: weekly UX meeting, weekly user meeting, and pre-review UX meeting. First, the frequency of the weekly UX meeting will be adjusted to better accommodate the capabilities of different teams. Similarly, the weekly user meeting will be scheduled more flexibly, either by iterations or based on the volume of work completed. Additionally, the frequency of the pre-review UX meeting will be modified to ensure that teams have time to make changes before the sprint review. For this reason, the weekly UXmeeting will be renamed to \"UX meeting\", while the weekly user meeting will be renamed to \"user meeting\" to emphasize the flexibility of its frequency.  
After implementing these changes, FRAMUX will require additional iterations to ensure it can be used to support teams in integrating and evaluating UX in agile software development. Thus, the following FRAMUX-EV iterations include the following stages and activities:  
* Iteration 2: In this phase, the changes identified during this first iteration will be implemented to develop the second version of FRAMUX-EV. This version will need to be validated with UX practitioners by conducting two experiments: (1) an experiment focused on evaluating the specification and detailed content of UX artifacts and (2) an experiment focused on evaluating the specification and feasibility of UX events. Both experiments aim to validate that the proposal meets the industry standards and project needs. Based on these expert evaluations, the necessary refinements will be identified, which will lay the groundwork for the next iteration of the framework.
* Iteration 3: The findings from the second iteration will be applied to further refine the framework, leading to the development of the third version of FRAMUX-EV. This version will be tested in real-world projects with two case studies to validate its effectiveness and applicability. In each experiment, feedback will be collected from UX and development roles to assess the effectiveness of integrating FRAMUX-EV in agile projects. The results of these validations will be used to obtain the final necessary adjustments, preparing the framework for its final iteration.
* Iteration 4: Finally, based on the feedback and improvements from the previous iteration, the necessary adjustments will be made to FRAMUX-EV to present its final version. This version will include all refinements identified during experiments in real-world projects and will represent a mature framework for evaluating and integrating UX into agile software development.
* Following these iterations, FRAMUX-EV will continuously evolve, ensuring the integration of UX evaluation and agile software development processes and providing more robust and effective results.