Our hearts beat for people: UX research in agile contexts.
•Download as PPTX, PDF•
15 likes•1,443 views
An overview of techniques and approaches to ensure UX research happens in agile contexts.
Recommended
Recommended
More Related Content
Similar to Our hearts beat for people: UX research in agile contexts.
Similar to Our hearts beat for people: UX research in agile contexts. (20)
More from johanna kollmann
More from johanna kollmann (20)
Recently uploaded
Recently uploaded (20)
Our hearts beat for people: UX research in agile contexts.
- 1. Our hearts beat for people UX research in agile contexts Johanna Kollmann- @johannakoll Agile UX & ResearchThingMeeupt, 24 August 2011 Photo by NASA Marshall Space Flight Center http://www.flickr.com/photos/28634332@N05/4864418222/
- 2. Research is the first thing to get compromised. Photo byKristina Alexanderson http://www.flickr.com/photos/kalexanderson/5421517469/
- 3. (Some) research methods Quantitative Qualitative Contextual inquiry Mental models Interviews Diary studies Surveys Interviews Generative Usability testing Moderated card sort Wizard of Oz Automated card sort Surveys Automated studies Analytics A/B Testing Multi-variant testing Evaluative Adapted from figures by Janice Fraser, Nate Bolt, Christian Rohrer
- 4. Magic bullets? Photo byEd Schipul http://www.flickr.com/photos/eschipul/4160817135/
- 5. Working ahead & ‘sprint zero’ ‘Case Study of Customer Input For a Successful Product’, Lynn Miller (2005)
- 10. Generative AND evaluative
- 11. Recruiting participants way in advance
- 12. Low-cost ‘lab’: a meeting room with observers sitting around the table
- 13. Grabbing people in the wild
- 16. Use whatever is ready
- 17. Limited to maximum of 3 participants
- 19. So what about personas? Persona and Empathy Map: Design Jam London 3. Team: Alison, Tarun, Jill, Venu and Mariana http://djlon0304.tumblr.com/page/2
- 21. Outcome: feature cards
- 23. State your hypothesis – what do you want to find out or validate?
- 24. Combine generative + iterative
- 25. Triangulate and consider remote methods
- 26. Recruiting is a b*tch
- 27. Involve the team
- 28. Do it RITE
- 31. ‘5 Users every Friday’, Tom Illmensee and Alyson Muff, Agile 2009 Proceedings
- 32. ‘Paired Interviews – applying pair programming thinking to user research’, Anders Ramsay,http://bit.ly/hlHgZd
- 33. ‘Beyond Staggered Sprints: Integrating User Experience and Agile’, Jeff Gothelf, http://slidesha.re/9Pq3qb
Editor's Notes
- 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
- !