# FRAMUX-EV: A Framework for Evaluating User Experience in Agile Software Development
## 3 Need for a UX Evaluation Framework  
Agile approaches are increasingly being used by companies for software development. This iterative development approach helps teams to deliver value to their customers faster and with fewer headaches [22]. Given frequent deliveries, it is important to check that what users need is actually being developed. Therefore, it is necessary to include the UX in agile software development, specifically the UX evaluation, to avoid neglecting the needs of end-users. However, some problems can be observed when integrating and evaluating UX within agile software development:  
* Difficulty in selecting the best method: Owing to the large number of UX evaluation methods, it is difficult to understand when it is convenient to apply some evaluation methods [23]. This becomes more difficult in changing and agile environments [24; 25; 26]. \begin{table}
\begin{tabular}{p{113.8 pt} p{113.8 pt} p{113.8 pt} p{113.8 pt} p{113.8 pt}} \hline \hline
**Authors** & **Type of Study** & **Stages** & **UX Evaluation Methods** & **UX Artifacts or UX Events** \\ \hline \multirow{4}{*}{[PERSON] et al. [2]} & Integration of elements to Scrum & 1. Scrum events & 1. Paper prototypes & \\  & Integration of elements to Scrum & 2. Formative UX evaluation & 3. RITE method & Not mentioned \\  & Integration of elements to & 1. Context of use & 4. Brief-regular tests & \\  & Integration of elements to & 2. User and organizational requirements & 1. Heuristic evaluation & \\  & Human-Centered Design & 3. Design \& prototype & 3. Labs tests/field trials & Not mentioned \\  & & 1. Sprim 0 & & \\  & Integration of elements to Scrum & 2. Scrum events & & \\  & & 3. A UX cycle embedded in the sprint & Not mentioned & UX event: 1. Lean UX cycle \\  & & & & \\  & & 1. Phase 1 & 2. (Un)moderated usability test & UX artifacts: 1. Documented ‘lessons \\ [PERSON] et al. [19] & Integration of elements to Scrum & 2. Phase 2 & test & 1. Documented ‘lessons \\  & & 3. Phase 3 & 3. Cognitive walkthrough & learned’ \\  & & 4. Phase 4 & 4. Card sorting & 2. User story map \\  & & & 5. Eye tracking & \\ [PERSON] et al. [20] & Integration of elements to Scrum & 1. Initiation Phase & 1. Design Evaluation & \\  & & 2. Planning Phase & 2. User Test (Thinking aloud) & Not mentioned \\  & & 3. Implementation phase & 3. Pair Design & \\  & & 1. Understand & \\ [PERSON] and [PERSON] [21] & Sequential and /or iterative activities for agile in general & 2. Ideate & \\  & & 3. Decide & 1. User testing & Not mentioned \\  & & 4. Prototype & \\  & & 5. Test & & \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Characteristics and limitations of the related works reviewed. Users are not actively incorporated: When working in an agile way, teams often neglect to incorporate users to evaluate an idea or decide what to implement. User feedback is often ignored or considered only in specific instances such as sprint reviews [25; 27; 28]. Prioritization of design over evaluation: Practices such as software design (user-centered design) are prioritized over evaluation (evaluation-centered evaluation). Thus, the team develops software primarily by considering what users want (functionalities) rather than how they want it (needs and goals) [26]. Communication problems: There is a lack of communication between the design/UX team and the development team, resulting in misunderstandings in the design and loss of important information [26; 27; 28]. Lack of early UX evaluation: In agile software development, it is believed that UX can (or should) be evaluated only in the final stages. Therefore, in the early stages, decisions are made without considering users' needs [27]. Difficulty in prioritizing UX work: No backlog is used to highlight user stories focused on UX. In addition, sprint goals are typically focused on development rather than UX, making it difficult to manage and check UX work [25; 27]. Most of these problems arise because agile approaches present a set of recommendations or guidelines for iterative development.