Logistics of Making Room for UX Work in Agile based Development Process [#Agile #AgileDevelopment #AgileDevelopmentProcess]

LOGISTICS OF MAKING ROOM FOR UX WORK IN AGILE BASED DEVELOPMENT PROCESS [#Agile #AgileDevelopment #AgileDevelopmentProcess]

1. BACKLOG STRUCTURE
2. PRIORITIZING FEATURES
3. PRIORITIZING UX DEBT
4. MAXIMIZING YOUR TIME

1. BACKLOG STRUCTURE
A product backlog is a list of features, bug fixes, and other activities that an Agile team is responsible for delivering.

There are two ways to approach backlogs from a UX perspective.

First approach:
All work (development, UX, quality assurance, and so on) can live in one backlog. This is a useful way to make UX work visible to the whole team.

A downside of this approach, however, is that UX work can easily be deprioritized for new features.

Second approach:
Create multiple backlogs—one for the primary product and one just for UX. In this scenario, the UX team is in charge of their own backlog and have the ability to plan ahead.

A disadvantage of this method is that UX velocity is separated from the rest of the team. Also, the UX team could risk getting too far ahead of the developers’ sprints.

For those who use this approach, focus more of your effort on your current and next sprint.

2. PRIORITIZING FEATURES
Use a prioritization matrix to organize features. A prioritization matrix is a 2D-visual that plots the relative importance of features based on two weighted criteria.

For example, features could be plotted based on criteria such as user value and effort by organization, or UX effort and development effort.

Features closer to the middle of the matrix are the most balanced, and best meet the needs of both criteria.

Using a matrix focuses decision-making on the data, reducing the chances of making decisions based on emotion.

3. PRIORITIZING UX DEBT
UX debt refers to additional time and effort costs that come from cutting corners on product development instead of using a holistic approach. This can result from things such as skipping usability testing or designing by committee.

Some best practices for eliminating UX debt are to identify the debt items and add them to the backlog. Teams can prioritize the debt by ranking it based on severity (low, medium, high) or creating a priority matrix.

Communication with the whole team is key to making this work.

4. MAXIMIZING YOUR TIME
Choose which meetings are most valuable to attend. Block out “heads-down time” for activities like research, design, and prototyping.

ADAPTED FROM
How Agile Teams Can Prioritize UX Work:
Practical Approaches to Integrating UX and Agile
nyu.edu

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Don`t copy text!