UX 연구를 이용하여 애자일 프로세스를 주도하는 방법

이 사례 연구에서 저자는 팀과 함께 연구 결과를 애자일 개발 프로세스에 통합하기 위해 어떤 조치를 하였는지를 말합니다. 업데이트된 애자일 프로세스는 UX 연구가 애자일 특성이 반영된 스프린트 방식의 기초적 역할을 함을 보여 주었고 사용자들의 문제에 대한 해결점을 찾게 해주었습니다. UX 연구는 또한 스프린트 방식에 내재된 특징들이 의도한 사용자들의 문제를 해결해주었는지의 여부도 확인해 주었습니다.

전체 기사는 영어로만 제공됩니다.

Ho, L. (2018). UX 연구를 이용하여 애자일 프로세스를 주도하는 방법. User Experience Magazine, 18(2).
Retrieved from http://uxpamagazine.org/how-to-use-ux-research-to-guide-an-agile-process/?lang=KO

4 Responses

  1. Alex 댓글:

    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 댓글:

      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 댓글:

    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 댓글:

      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