UX & Agile - UX Research Amsterdam meetup - 04022016

Download UX & Agile - UX Research Amsterdam meetup - 04022016

Post on 15-Apr-2017

451 views

Category:

Technology

21 download

Embed Size (px)

TRANSCRIPT

<ul><li><p>UX Research </p><p>Agile </p></li><li><p>Anna Witteman Head of UX Lab </p><p>IceMobile</p></li><li><p>Copyright A. Witteman &amp; R. van den Oever, All Rights Reserved.</p><p> Amsterdam based company (&amp; office in Hong Kong, Toronto) </p><p> 120 employees </p><p> over 30 nationalities </p><p> Either a foodie, code king, design nerd, beer brewer or unicorn </p><p>IceMobile Amsterdam</p></li><li><p>Context ChatPulse UX Testing</p><p>Cultural relevant research</p><p>Experience Mapping</p></li><li><p>THE MARSHMALLOW CHALLENGE</p></li><li><p>Orient Plan Build Ta-da!</p><p>Business (wo)men</p><p>Kindergarten students</p><p>0 18 Minutes</p><p>Uh-oh!</p></li><li><p>Agile teams</p><p>Product Backlog</p><p>Sprint Backlog</p><p>Potentially Shippable Product</p><p>2-3 weeks</p><p>24 hours</p><p>Daily Scrum Meeting</p><p>Design</p><p>Development</p><p>Q/A Testing</p></li><li><p>the problem</p></li><li><p>Ta-da!</p><p>Previous Usability Testing</p><p>Iterative Usability Testing</p><p>0 Time</p><p>Uh-oh!</p><p>Involve users</p></li><li><p>Agile teams</p><p>Product Backlog</p><p>Sprint Backlog</p><p>Potentially Shippable Product</p><p>2-3 weeks</p><p>24 hours</p><p>Daily Scrum Meeting</p><p>Design</p><p>Development</p><p>Q/A Testing</p><p>Usability testing</p></li><li><p>findings do not stick</p></li><li><p>mismatch </p></li><li><p>no visible value</p></li><li><p>Transfer information effectiveThe team should learn most of the user test, not the UX researcher </p><p>Fit the user into the processDo testing so that it is not extra work </p><p>Make results visibleValue should be clear and measurable</p><p>We wanted to find a way to:</p></li><li><p>HOW?</p></li><li><p>Which practice proved its value?</p><p>Individuals and interactions </p><p>Working software </p><p>Customer collaboration </p><p>Responding to change</p><p>over </p><p>over </p><p>over </p><p>over</p><p>processes and tools </p><p>comprehensive documentation </p><p>contract negotiation </p><p>following a plan</p><p>Agile Manifesto</p></li><li><p>Source: Nielsen, Jakob, and Landauer, Thomas K.: "A mathematical model of the finding of usability problems," Proceedings of ACM INTERCHI'93 Conference (1993), pp. 206-213.</p><p>Usability Testing is an iterative process!</p></li><li><p>Iteration is the heartbeat of agile &amp; user testing </p><p>use it!</p></li><li><p>Product = Prototype </p><p> Write a scenario </p><p> Create a prototype </p><p> Recruit users </p><p> Pilot test </p><p> Conduct Tests </p><p> Edit videos </p><p> Analyze video </p><p> Write report </p><p> Present results</p><p>User test = Report</p></li><li><p>Our setup is a combination of simple tools </p></li><li><p>Our setup is a combination of simple tools </p></li><li><p>More evaluators = more issues identified</p><p>Source: Herttzum, M., Jacobsen, N. (2001). The evaluators effect: A chilling fact about usability evaluation methods. International Journal of Human-Computer Interaction, vol. 13, pp.421-443. </p></li><li><p>Ratio benefits to costs of # evaluators4 = ideal # evaluators</p><p>Source: Herttzum, M., Jacobsen, N. (2001). The evaluators effect: A chilling fact about usability evaluation methods. International Journal of Human-Computer Interaction, vol. 13, pp.421-443. </p></li><li><p>Chapter title</p></li><li><p>How to keep track of the findings?</p><p># user that did this task</p><p># user that had this problem</p><p>time stamps of this issue </p><p>on video</p><p>description of issue</p></li><li><p>How to keep track of the findings?</p></li><li><p>Pulse: iterative User Involvement</p><p>Prioritize: test important part(s) most extensive </p><p>Frequent: reliable results, also test improvements </p><p>Empathize: learn what matters to users </p><p>Optimize: learn to test </p><p> Allow responding to change </p><p>'I have not failed. I've just found 10000 ways that won't work.</p><p>Sir Thomas Edison</p></li><li><p>Pulse UX TestingTraditional UX testing</p><p>Iterative UX testing: every 2 weeks</p><p>UX testing (near) the end of a project</p><p>Continuous testingSingle test</p><p>Small sessionsBig session</p><p>Performed by the teams: the team members learn most</p><p>Performed by researchers: the researchers learn most</p><p>Changes early in the process; thus less costly</p><p>Changes late in the process; thus very costly</p><p>Rise in first time right of features</p><p>Few first time right of features</p><p>120% end-result in 80% of the time </p><p>Difficult to measure success</p></li><li><p>Transfer information effectivelyThe team learns most of the user test, not the UX researcher </p><p>Fit the user into the processDo testing so that it is not extra work </p><p>Make results visibleValue should be clear and measurable</p><p>What we achieved:</p></li><li><p>Thank you!</p><p>anna@icemobile.com linkedin.com/in/annawitteman </p><p>@Morise</p><p>mailto:anna@icemobile.com?subject=http://linkedin.com/in/annawitteman</p></li><li><p>We are hiring. icemobile.com/jobs</p></li><li><p>IceMobileAmsterdam @icemobile@icemobile</p></li></ul>