Cómo usar la investigación de experiencia de usuario para guiar un proceso ágil

En este estudio de caso, la autora analiza cómo trabajó con su equipo para integrar la investigación en un proceso de desarrollo ágil. El proceso ágil actualizado dio como resultado un rol fundamental de la investigación de experiencia de usuario en el comienzo de un sprint ágil para ayudar a alinear el equipo con los problemas de usuario que resolverían. Y la investigación de experiencia de usuario también ayudó al final de un ciclo a validar si las funciones creadas durante el sprint solucionaron o no los problemas de usuario previstos.

La versión completa de este artículo está sólo disponible en inglés

Ho, L. (2018). Cómo usar la investigación de experiencia de usuario para guiar un proceso ágil. User Experience Magazine, 18(2).
Retrieved from https://uxpamagazine.org/how-to-use-ux-research-to-guide-an-agile-process/?lang=es

4 Responses

  1. Alex dice:


    Thanks for this post. I do have some questions too:

    * What’s your sprint length?
    * How do you integrate evaluation, design and development exactly? Let’s say you sprint in 2 week cycles. This leaves very little time to plan research, recruit users, prepare the design, review the findings, refine the design and develop a feature.


    • LaiYee Ho dice:

      Hi Alex,

      Sprint lengths were typically 1-3 weeks long depending on the scope. And you’re right that this leaves very little time to plan, recruit, prepare, review findings etc. Cramming research into such a short time is never great.

      In order to make time for solid research, we ended up adopting a staggered sprint approach to work on 2 features at a time. Say we had sprint A and sprint B. While sprint A was being built by design/engineers, sprint B would be evaluated by UX research. When sprint A was completed by design/engineers, they would switch off.

      This gave research the full 1-3 weeks of a sprint to complete a full study. And design/engineering would be ready to take action on the results immediately.

      – LaiYee Ho

  2. PN dice:

    Hi ! It is a very interesting article and this process seems great.

    I just have some questions which need some enlightments.

    1-I can see an UX team working on research but it seems that after that it directly go to design and dev. I don’t see a product specification to detail the sprint features. Is it done in parallel or is it not necessary in this case ?

    2-During a sprint, how long does it usually take to do these research and evaluation studies ?

    Thanks a lot =)

    • LaiYee Ho dice:


      1) The product specification happens both in parallel and after foundational research. During foundational research, PMs, designers and engineers tag along in the research studies. A lot of product alignment happens during those debriefs and the specifications start to form. Then after the study is over, there is a more formal product specification step to detail them out more before design and development begins.

      2) Foundational research takes 3-8 weeks. Because of the long lead time we often kick this off while a different sprint is finishing.

      Evaluation research is quicker, 1-3 weeks depending on the scope of the features. ~1 week or even a few days if it’s quick usability, but longer if something more in depth or contextual is necessary for validation.

      – LaiYee Ho