# FRAMUX-EV: A Framework for Evaluating User Experience in Agile Software Development
## 6 Validating the Framework
### Qualitative Results
#### 6.2.3 Qualitative Results: UX Events  
In addition to the UX events presented in the survey, 10 additional events were suggested for consideration. The most mentioned events were \"UX feedback meeting\" (P4, P19, P21) and \"daily UX meeting\" (P5, P7). Surprisingly, 20 practitioners considered it unnecessary to include any additional UX events beyond those mentioned in the survey. The majority of respondents seemed satisfied with the events presented, indicating that they would not eliminate any of the artifacts proposed (25 of 34 participants). However, some practitioners suggest eliminating the \"pre-review UX meeting\" because it is not the right time to do it (P30) and it should be done with the whole team (P19), as well as the \"weekly UX meeting\", where it is mentioned that they would not do it weekly (P32) as it is unnecessary (P4) given the time they have within the sprint (P26). Although few comments were obtained, there were different opinions regarding the proposal. For instance, it was stressed that the \"weekly UX meeting\" should not have to be weekly as it takes too much time and could be unnecessary (P4, P16, P20, P32). On the other hand, it was mentioned that events and meetings should be held with the entire team (P14, P32). Table 11 presents additional comments related to each UX event and future actions to be considered. The recommendations and comments of the experts will be considered. We will change the name of the event to User Meeting. In addition, we will define that the ideal frequency of the event would be one or two sprints. Finally, we will include a consideration that, instead of using weeks, the event could be held after a certain volume of work has been completed. Some recommendations and comments from experts will be considered. We will keep the event since only two comments refer to the fact that it could be unnecessary. In addition, we will define the ideal frequency of the event to be one or two days before the sprint review. The expert's comment will not be considered. In agile environments, the backlog is an artifact that must always be refined and updated, never remaining static. The expert's comment will be considered. We will change the name of the event to \"UX meeting\". In addition, we will define the ideal frequency of the event to be one or two weeks. \begin{table}
\begin{tabular}{c c} \hline
**UX Artifact** & **Additional Comments** & **Future Actions** \\ \hline - \"The weekly user meeting seems unnecessary to me\". (P4) - \"The meeting with users would not be weekly\". (P20) - \"Testing with users takes time, so I do not consider that doing it weekly would bring many benefits or differences because if you consider the time in which users test, analyze the information and make changes could take more than a week. So, I think that testing once a month or after a certain number of changes in the interface would be more enriching\". (P26) - \"Given the time we have for the sprint we don’t get to have weekly meetings with users\". (P32) - \"I don’t see the sense of a meeting with UX before the sprint review\". (P17) - \"The UX meeting before the review can be useful if there was no communication during the development to explain how it works before showing it in the review. But if there is constant communication, it may be unnecessary\". (P20) - \"While it is always useful to hold meetings, holding them just before the review may not be the best time in my personal opinion\". (P30) - \"If the backlog is defined from the beginning and is kept in a static way, this event is very unnecessary\". (P20) - \"Perhaps a biweekly UX meeting would be appropriate to keep pace with the development of the sprint and reduce costs\". (P16) \\ \hline \end{tabular}
\end{table} 
Table 11: Additional comments and future actions for UX events. In summary, there were no significant negative comments regarding proposed UX events. However, it is necessary to adjust the frequency of certain events to better align with agile environments (P16, P20, P26, P32).