The document discusses how user experience (UX) research needs to adapt to agile development processes. It recommends using research methods that have narrow objectives, shorter timelines, and more informal deliverables to provide frequent feedback throughout sprints. Specific methods described include heuristic evaluations, competitive reviews, guerrilla testing, and rapid iterative testing and evaluation (RITE) that allow quick testing and iteration on prototypes to inform the design process.

1. UX Research in an Agile World
Hira Javed
November 23, 2014

2. About Me
Usability Specialist
@hirajaved10
UX Instructor
http://lnkd.in/HGSpHW

3. “Research is formalized curiosity.
It is poking and prying with a purpose.”
- Zora Neale Hurston

4. UX Research is about…
Understanding the user:
• What they do
• How they do it
• Why they do it

5. Why do UX research?

6. To avoid this…

7. and this…

8. and therefore this…

9. “building the right thing and we’re building
the thing right.”
- Natalie Hanson

10. Goals of UX Research
• To add context and insight to the the
design process.
• To measure the effectiveness of design
solutions implemented.

11. Traditional Face of User Research

12. But times they are
a-changin’

13. Forces Affecting User Research

14. Mobile explosion
It’s all about context

15. Industry speed
Pressure to constantly evolve

16. Agile development
Sprints don’t wait

17. UX Culture
People want to be
involved

18. Traditional methods
take time

19. We have to make these faster…

20. Narrow
objectives

21. Shorter Timelines

22. Informal deliverables

23. Brief Documentation

24. Agile UX Research
• TexAgile is about thinking holistically, working
incrementally.
• UX research process needs to align with this
incremental workflow.
• Research should commence in sprint 0 or
earlier.
• Prototypes will need to be tested one sprint
ahead of development.

25. Research Methods

26. Heuristic Evaluation
• Evaluate part of a design against set of
usability best practises.
• Can be done in 30 minutes
• Can be used to provide usability feedback
in each sprint.

27. Quick Competitive Review
• Identify best practices and trends in the
competitive landscape.
• Can be completed in a day (depending on
research objective).
• Can be used to provide feedback during the
discovery phase.

28. Guerilla Testing
• Quick, low cost, usability testing “in the wild”
• Can be conducted anywhere
• 3 - 5 participants
• 5 - 10 minutes each
• Low - high fidelity prototype

29. Can be conducted as soon as the idea is
out of your head

30. ...with any type of prototype
Low-fidelity prototype Med to High-fidelity
prototype

31. How to Plan a Guerilla Test

32. 1. Identify test goal
Determine what is the purpose of doing
the test.
Example goal statement:
“Assess the latest version of the mobile video player.”

33. 2. Identify target participants
Determine participant characteristics.
Example participant screener:
• Users must own a smartphone.
• Users must access mobile video content at least
once a week.

34. 3. Identify test objectives
Determine what you’re trying to learn.
What questions are your trying to
answer?
Example test objectives:
• Can users easily and effectively use the video
player?
• Can users interact with the scrubber?
• Do users understand how to share a video?

35. 4. Create tasks
Create user tasks that will allow you to
assess your objectives.
Example tasks:
• Play a video and view comments
• Share a video

36. 5. Create scenarios
Create realistic scenarios of when users
may do those tasks.
Example scenarios:
• Let’s say a friend told you about a great comment
Rob Ford made at the end of this video clip. Can
you play the clip and go to the comment?
• You loved the clip and want to send it to another
friend. Can you show me how you would do that?

37. 6. Prepare the prototype
Create a prototype that can be tested.
Sketches Wireframes Live
site/app
Interactive prototype

38. RITE Method
• Rapid Iterative Testing & Evaluation (RITE)
• Developed by Microsoft Games Studio and
Microsoft Research.
• Similar to typical usability testing
• Changes to interface are made as soon as
an issue is identified and a solution is clear.

39. RITE Method
• The improved interface is tested with the next user.
• Requires a dedicated researcher, and designer or
developer.
• Used to make design changes in small increments.
• Can be completed in one day or over a few days.
• Key decision makers must observe the test sessions.

40. RITE: Process
9am
V0.1
Edit 11am
V0.2
Edit 1 pm
V0.3
Edit 3 pm
V0.4
Edit
Final
Iteration
User 1 User 2 User 3 User 4

41. C-RITE Method
• Collaborate Rapid Iterative Testing & Evaluation
• Used by Android teams in Google
• 6 research sessions in 2 days.
• Prototype changes between day 1 and 2.
• Stakeholders collaborate in all UX phases.

42. C-RITE Method
Collaborative design workshop for
each day.
• Designers demonstrate problem solving skills.
• Engineers solve technical constraints.
• Researchers guide insight interpretation.
• PM gives business and scheduling input.
• Can be repeated weekly.

43. C-RITE Method
Traditional roles

44. C-RITE Method
Collaboration in C-RITE

45. C-RITE Process

46. Key Take-Aways
• The agile approach of incremental delivery needs
continual design input.
• There’s a fundamental shift in the way we
conduct research in agile projects.
• Narrow scope, faster methods, fewer participants
but frequent testing, and less documentation.

47. User research
won’t hold you back

48. Any Questions?