Como usar a pesquisa de experiência do usuário para orientar um processo Ágil

Neste estudo de caso, a autora conta como trabalhou com sua equipe para integrar a pesquisa a um processo de desenvolvimento Ágil. O processo Ágil atualizado resultou no desempenho da pesquisa de experiência do usuário de uma parte fundamental no início de um sprint Ágil para ajudar a orientar a equipe sobre quais problemas do usuário ela resolveria. E a pesquisa de experiência do usuário também ajudou no final de um ciclo a validar se os recursos criados durante o sprint resolveriam ou não os problemas do usuário em questão.

O artigo completo está disponível somente em inglês.

Ho, L. (2018). Como usar a pesquisa de experiência do usuário para orientar um processo Ágil. User Experience Magazine, 18(2).
Retrieved from http://uxpamagazine.org/how-to-use-ux-research-to-guide-an-agile-process/?lang=pt

4 Responses

  1. Alex disse:

    Hi,

    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.

    Thanks,
    Alex

    • LaiYee Ho disse:

      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 disse:

    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 disse:

      Hey!

      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

Leave a Reply