- Research needs to be done before development so we can make sure we are later developing the “right” thing.
- Research takes a lot of time and it is almost impossible to have our findings in one single sprint. Design researchers need to plan & logistics (sometimes we might need to buid a prototype to test experiments) + recruit participants (dependency on participant’s availability here) + run the research study (where some are longer than a sprint! Especially if you are running an ethnography or an observational study) + do the data analysis (which also depending on the study can take time) + create a report or some way to communicate the findings to your team. As you can see, Research effort really needs to be broken down into smaller steps.
- The way I've always worked in an agile team was using the Dual track agile approach but I’ve been seeing from SCRUM specialists that it isn’t a good approach because it puts design and research one sprint ahead of development which makes it a bit waterfall.
So, What is the best way to include UX research (and even UX design) tasks in an agile team’s backlog? How can we make research and design work better with development in agile teams? Did you encounter the same situation with your teams? If so, how did you solve it?
I initially thought spikes could also be an answer for UX research but I’ve learned they aren’t because spikes should be done as exceptions. Besides spikes should be time-boxed and they shouldn't take more than 1 sprint.
Thank you so much in advance for your help,