Our hearts beat for people<br />UX research in agile contexts<br />Johanna Kollmann- @johannakoll<br />Agile UX & Research...
Research is the first thing to get compromised.<br />Photo byKristina Alexanderson http://www.flickr.com/photos/kalexander...
(Some) research methods<br />Quantitative<br />Qualitative<br />Contextual inquiry<br />Mental models<br />Interviews<br /...
Magic bullets?<br />Photo byEd Schipul http://www.flickr.com/photos/eschipul/4160817135/<br />
Working ahead & ‘sprint zero’<br />‘Case Study of Customer Input For a Successful Product’, Lynn Miller (2005)<br />
Make it a habit<br />‘5 Users every Friday’(case study by Tom Illmensee and Alyson Muff)<br /><ul><li>UX research as the b...
 Solution: get research into the natural rhythm of the Scrum teams</li></li></ul><li>A busy week!<br />Plan<br />(Tuesday/...
‘5 Users every Friday’ (case study by Tom Illmensee and Alyson Muff)<br /><ul><li> Collaborate on the research goals with ...
 Simple template
 Generative AND evaluative
 Recruiting participants way in advance
 Low-cost ‘lab’: a meeting room with observers sitting around the table
 Grabbing people in the wild
 Low-fi reporting</li></li></ul><li>
How it works at TheLadders.com<br /><ul><li>Every other week (2 weeks sprints)
 Use whatever is ready
 Limited to maximum of 3 participants
Upcoming SlideShare
Loading in...5
×

Our hearts beat for people: UX research in agile contexts.

2,938
-1

Published on

An overview of techniques and approaches to ensure UX research happens in agile contexts.

Published in: Design, Technology, Sports
1 Comment
14 Likes
Statistics
Notes
No Downloads
Views
Total Views
2,938
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
38
Comments
1
Likes
14
Embeds 0
No embeds

No notes for slide
  • 2 tracks, staggered sprint approach: The design team works ahead a development time-box or two. In a given timebox they might be: - researching work to be done 2 time-boxes from now (T + 2) -validating design prototypes to be built 1 time-box from now (T + 1) - being available to collaborate with development to support work done in the current development timebox (T) - working with customers to validate working software built in the previous time-box (T – 1)Mention sprint 0. On projects, that’s where in-depth research can happen. Depends on scale and context Interim sprint zeros.
  • Bottleneck problem: Planning and recruiting for usability tests could take a week or more. Running protocols with up to 8 users could take us up to 12 hours. Data analysis could take another week. The report takes a week to write – and a week to read. About 4 weeks – tough when sprints are only 3.
  • Planning starts on Tuesday. Here we’re deciding what our questions are and how we’ll try to find answers. We finish the test plan and prep on Wednesday and Thursday. This might include some wireframes, design comps, or setting up a semi‐functional prototype. We wrote task scenarios designed to help users experience the interface realistically. We handled test logistics, too: recruiting participants and getting our lab prepped.We ran usability tests on Friday – starting first thing in the morning. By late afternoon we had started analyzing data and dashed off a quick results summary for the team before leaving for the weekend.Monday we finished the analysis and got ready for a review session with the team.Tuesday we reviewed research‐based recommendations and started planning for the next round of tests.
  • Reporting: structure!
  • = Mid-way through the sprint
  • Grow them out of proto-personas
  • = Mid-way through the sprint
  • Recruiting: mention user panels
  • !
  • Our hearts beat for people: UX research in agile contexts.

    1. 1. Our hearts beat for people<br />UX research in agile contexts<br />Johanna Kollmann- @johannakoll<br />Agile UX & ResearchThingMeeupt, 24 August 2011<br />Photo by NASA Marshall Space Flight Center http://www.flickr.com/photos/28634332@N05/4864418222/ <br />
    2. 2. Research is the first thing to get compromised.<br />Photo byKristina Alexanderson http://www.flickr.com/photos/kalexanderson/5421517469/<br />
    3. 3. (Some) research methods<br />Quantitative<br />Qualitative<br />Contextual inquiry<br />Mental models<br />Interviews<br />Diary studies<br />Surveys<br />Interviews<br />Generative<br />Usability testing<br />Moderated card sort<br />Wizard of Oz<br />Automated card sort<br />Surveys<br />Automated studies<br />Analytics<br />A/B Testing<br />Multi-variant testing<br />Evaluative<br />Adapted from figures by Janice Fraser, Nate Bolt, Christian Rohrer<br />
    4. 4. Magic bullets?<br />Photo byEd Schipul http://www.flickr.com/photos/eschipul/4160817135/<br />
    5. 5. Working ahead & ‘sprint zero’<br />‘Case Study of Customer Input For a Successful Product’, Lynn Miller (2005)<br />
    6. 6. Make it a habit<br />‘5 Users every Friday’(case study by Tom Illmensee and Alyson Muff)<br /><ul><li>UX research as the bottleneck
    7. 7. Solution: get research into the natural rhythm of the Scrum teams</li></li></ul><li>A busy week!<br />Plan<br />(Tuesday/Wednesday)<br />Recommend<br />(Monday/Tuesday)<br />Prepare<br />(Wednesday/Thursday)<br />Analysis<br />(Friday/Monday)<br />Test<br />(Friday!)<br />
    8. 8. ‘5 Users every Friday’ (case study by Tom Illmensee and Alyson Muff)<br /><ul><li> Collaborate on the research goals with the team
    9. 9. Simple template
    10. 10. Generative AND evaluative
    11. 11. Recruiting participants way in advance
    12. 12. Low-cost ‘lab’: a meeting room with observers sitting around the table
    13. 13. Grabbing people in the wild
    14. 14. Low-fi reporting</li></li></ul><li>
    15. 15. How it works at TheLadders.com<br /><ul><li>Every other week (2 weeks sprints)
    16. 16. Use whatever is ready
    17. 17. Limited to maximum of 3 participants
    18. 18. Validate and iterate</li></li></ul><li>How many people do you need to see bumping their head?<br />Photo bySteve Clark http://www.flickr.com/photos/askclark/3698813123/<br />
    19. 19. So what about personas?<br />Persona and Empathy Map: Design Jam London 3. <br />Team: Alison, Tarun, Jill, Venu and Mariana<br /> http://djlon0304.tumblr.com/page/2<br />
    20. 20. Story mapping as research activity<br />Photo by Anders Ramsay, http://bit.ly/hlHgZd<br /><ul><li>‘Pair interviewing’
    21. 21. Outcome: feature cards
    22. 22. Details on Anders Ramsay’s blog:http://bit.ly/hlHgZd</li></li></ul><li>Top tips 2007 - 2011<br /><ul><li> Prototype! Prototype! Prototype!
    23. 23. State your hypothesis – what do you want to find out or validate?
    24. 24. Combine generative + iterative
    25. 25. Triangulate and consider remote methods
    26. 26. Recruiting is a b*tch
    27. 27. Involve the team
    28. 28. Do it RITE
    29. 29. Practice, learn and iterate</li></li></ul><li>Steve Blank, The Four Steps to the Epiphany<br />
    30. 30. A selection of resources<br /><ul><li> ‘Case Study of Customer Input For a Successful Product’, Lynn Miller (2005)
    31. 31. ‘5 Users every Friday’, Tom Illmensee and Alyson Muff, Agile 2009 Proceedings
    32. 32. ‘Paired Interviews – applying pair programming thinking to user research’, Anders Ramsay,http://bit.ly/hlHgZd
    33. 33. ‘Beyond Staggered Sprints: Integrating User Experience and Agile’, Jeff Gothelf, http://slidesha.re/9Pq3qb
    34. 34. ‘Designing the user experience in an agile context’, Johanna Kollmann, http://bit.ly/p3NmWI</li></li></ul><li>Thank you<br />All the practitioners who share their learnings.<br />The Balanced Team. Desiree Sy. Jeff Patton. Anders Ramsay. Jeff Gothelf & Will Evans. Tom Ilmensee. <br />Jeff Van Campen for organising this event with me, and Fortune Cookie for hosting and sponsoring.<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×