# FRAMUX-EV: A Framework for Evaluating User Experience in Agile Software Development
## 7 Discussions
### How to Use FRAMUX-EV  
The integration of UX practices into agile development frameworks, such as Scrum, is essential to ensure that software products meet both functional and UX requirements. FRAMUX-EV, a framework proposed for supporting UX evaluation within agile approaches, provides a flexible approach for integrating UX events and artifacts throughout a Scrum iteration. Below, we outline how FRAMUX-EV can be integrated into the traditional Scrum iteration through dedicated UX events and UX artifacts, ensuring that UX is prioritized along with development tasks:  
1. Before the sprint planning, the team conducts a **pre-planning UX meeting**. This event aims to verify whether the prioritized UX work in the **UX backlog** is ready to be undertaken by the development team during the sprint. 2. During the sprint planning, the Scrum team selects items from the product backlog to be developed during the sprint. Simultaneously, the UX tasks from the **UX backlog** are prioritized and integrated into the **UX sprint backlog** to ensure that the UX requirements are covered. 3. The team meets daily during the daily meeting to track the progress of sprint tasks. During this event, both developers and UX roles ensure that any blockers or impediments in the UX work are promptly resolved. If UX team members have questions about any aspect of their tasks, they can refer to **UX roles and responsibilities**. 4. Once per week, a **weekly UX meeting is held**, where the UX team and developers discuss the progress of UX design, review updates to the UX components, and resolve issues related to the feasibility of UX designs. In this meeting, potential changes to the **UX design system** may be reviewed, and the team discusses the evolution of the UX work
5. Once per week, a **weekly user meeting** is held with users to evaluate UX work using some of the methods suggested in **UX evaluation methods**, discuss upcoming tasks, and obtain direct feedback on ongoing designs. The outcomes of these meetings are documented in the **UX evaluation repository** for subsequent analysis and refinement. 6. Just before the sprint review, a **pre-review UX meeting** is conducted, where the UX and development teams validate whether the UX designs and functions implemented during the sprint meet the required standards and objectives. 7. During the sprint review, the Scrum team presents the product increment, including both development and UX implementations. The UX team can demonstrate how the **UX personas**, **UX design system**, and **UX evaluation repository** guided the final design presented to the stakeholders. 8. After the sprint review, the team holds a sprint retrospective to discuss what went well and what could be improved, focusing on both the development and the UX integration aspects. In this event, improvements to UX artifacts, UX events, or UX evaluation methods may be proposed. In addition, we present practical examples illustrating how FRAMUX-EV components (UX events, UX artifacts, and UX evaluation methods) can be applied across three distinct Scrum team scenarios: (1) a team with only developers and no dedicated UX roles, (2) a small team with both developers and one UX role, and (3) a larger team with multiple developers and UX roles working together. Each scenario demonstrates how UX considerations can be adapted to varying team compositions, ensuring that user-centered design remains a priority (see Table 12). \begin{table}
\begin{tabular}{p{113.8 pt} p{113.8 pt} p{113.8 pt} p{113.8 pt}} \hline \hline
**Scenario** & **1** & **2** & **3** \\ \hline Description of roles & No dedicated UX roles. & One UX role is part of the development team (three developers + one UX). The UX role collaborates closely with the developers on UX work. & Three UX roles are part of the development team (six developers + three UX). The UX team works in close collaboration with developers, sharing UX responsibilities across multiple areas. & Three UX roles are part of the development team (six developers + three UX).