Pulse UX Testing: Bring the user into the user story. A.Witteman&R.vandenOever

  • View
    264

  • Download
    0

  • Category

    Design

Preview:

DESCRIPTION

Testing with users improves the quality of your product. But why is it that everyone knows the importance of frequent user testing, yet hardly anyone ever does it? Is it because User Testing often is time consuming, complex and expensive? It probably doesn’t fit in your development process and thus feels like extra work. To feel reassured, and to give some sort fake sense of security, you tell yourself to test with users once you have something working, or at the very end of the process. This is strange, because everybody knows that changing your product late in the process will increase costs exponentially. What if we tell you that we created a way so that User Testing saves time, improves the quality and doesn’t cost a lot of money? Team driven, pragmatic and no extra resources needed. During our talk we will show you how, with only 2 hours every sprint, we have focussed on creating better products faster. We would love to share our learnings and simple DIY tools that let you start user testing with your current team(s) tomorrow!

Citation preview

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Bringing the user into the user storyPulse Testing by Anna Witteman & Robin van den OeverMobile App Europe - Sep 2014

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Today

What we will talk about

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Bringing the user into the user story

helped us deliver better products

faster.

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

2002 2007 2014

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Requirements

• Requirement 1

• Requirement 2

• Requirement 3

• Requirement N

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

‘As a user I want to

..................................

so that I can

................................’

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• deliver a better product, faster

• strengthen your team

• with hardly extra costs

Giving the user a place in the process, will

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Introduction

Who we are and where we are from?

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Hello :)

Robin van den OeverProject manager/Agile coach

robin@icemobile.com

Anna WittemanHead of UXLab

anna@icemobile.com

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• Amsterdam based company

• 100 employees

• over 25 nationalities

• Either a foodie, code king, design nerd, beer brewer or unicorn

IceMobile Amsterdam

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

the full mobile agency

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

App icons

the mobile agency for food retail

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

ProductsSpecialized in Food Retail Focus on (end) Users

One-offsAll round Focus on clients

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Problem

Why don’t we test frequently with users?

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

“It doesn’tfit in our sprint.”

“The resultsare hard to measure.”

“It feels like extra

work.”

“We were just up

to speed.”

“It is too soon to testwith users.”

“We don’t have time to make a prototype.”

“Knowing the user is not

part of my job.”

“How do I knowwhat I will get

out of it?”

“Where do we get

users from?”

“How do we know which test results we should use?”

“We do not have resources to do

user tests.”

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Interest:

Plan: How and when are we doing user testing?

Is it really a plan or more an improvisation?

Means:

Interest: What is the motivation for user testing?

Improve the product or prove you are right?

Plan:

Vision: Does decision-makers really have a good UX as a priority?

Or is more a buzz word?

Interest:

Vision

Interest

Plan

Means

Skills

What do we need to be able to start user testing?

Users? Prototype? Software? etc.

Skills: Can we conduct a user test?

Do we know how?

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Transfer information effectiveThe team should learn most of the user test, not the UX researcher

Fit the user into the processDo testing so that it is not ‘extra work’

Make results visibleValue should be clear and measurable

We wanted to find a way to:

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Our solution

How to create a place where great UX will happen.

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Which practice proved its value?

Individuals and interactions

Working software

Customer collaboration

Responding to change

over

over

over

over

processes and tools

comprehensive documentation

contract negotiation

following a plan

Agile Manifesto

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Setup

Process

Proof

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Setup

Process

Proof

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Applying the agile principles to user testing

• Give team members responsibility

• Reduce paperwork to the minimum

• Giving the team little overhead

• Reuse documentation written from an user perspective

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• Write a scenario

• Create a prototype

• Recruit users

• Pilot test

• Conduct Tests

• Edit videos

• Analyze video

• Write report

• Present results

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Product = Prototype

• Write a scenario

• Create a prototype

• Recruit users

• Pilot test

• Conduct Tests

• Edit videos

• Analyze video

• Write report

• Present results

User test = Report

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Our setup

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

More evaluators = more issues identified

Source: Herttzum, M., Jacobsen, N. (2001). The evaluator’s effect: A chilling fact about usability evaluation methods. International Journal of Human-Computer Interaction, vol. 13, pp.421-443.

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Ratio benefits to costs of # evaluators4 = ideal # evaluators

Source: Herttzum, M., Jacobsen, N. (2001). The evaluator’s effect: A chilling fact about usability evaluation methods. International Journal of Human-Computer Interaction, vol. 13, pp.421-443.

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Conclusion

• Optimized the user test:

• Give the team responsibility

• No paperwork and no overhead

• Maintain a mutual goal

• Make the team smarter over time

• Team gets motivated

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Setup

Process

Proof

Setup

Process

Proof

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• Divided total work in small iterations

• Recurring rituals

• Easy to change course if required

• Give room to improve the process

Applying the agile principles to user testing

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Our agile way of working

Product Backlog

Sprint Backlog

PotentiallyShippableProduct

2-3 weeks

24 hours

Daily stand upDesign

Development

Testing

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

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.

How many users should do a usability test?

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Iterative Testing

•Prioritize: test important part(s) most extensive

•Frequent: reliable results, also test improvements

•Empathize: learn what matters to users

•Optimize: learn to test

Allow responding to change

'I have not failed. I've just found 10000

ways that won't work.’

Sir Thomas Edison

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

iteration is the heartbeatof agile & usertesting

use it!

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Our renewed agile way of working

Product Backlog

Sprint Backlog

PotentiallyShippableProduct

2-3 weeks

24 hours

Daily Scrum Meeting

Design

Development

Testing

User Testing

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• User test in every sprint

• User test with 4 users

• Scenario about sprint (& previous sprints)

• No need to react immediately to findings

Pulse Testing: bring the user into the Sprint

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Setup

Process

Proof

Setup

Process

Proof

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• Always show progress visually

• Describe requirements from a user perspective (as a user... so that..)

• Discuss all work created with each other being responsible as a group

Applying the agile principles to user testing

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• Issues

• Insights

• Wish list

• Fixed issues (adjusted issues)

Make all results tangible

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

How to keep track of the findings?

# user that did this task

# user that had this problem

time stamps of this issue

on video

description of issue

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

How to keep track of the findings?

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Follow up and integrate in existing process:

1.The most important issues will become user stories itself

2.These user stories are put in the product backlog

3.Most important issues will surface over time

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Start tracking your Sprint contents

• Because you want to understand the impact of user testing

• Identify types of user stories in sprint:

• New Features

• Bugs

• Rework resulting from user testing

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Example sprint contents

0

15

30

45

60

1 2 3 4 C 5 6 7 8 C

New Features Bugs Rework resulting from UT

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Back to you.

What it comes down to.

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

• Look at common practices within your company

• Eliminate waste

• Merge iterations

• Visualize progress

Learnings

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Every project has its own challenges...

the most important thing is to start, you will make it work for you!

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

How are we and where are we from?Thank you!Questions? Feedback? Share experience with user testing?

Please contact us: anna@icemobile.com & robin@icemobile.com

We love to stay in contact!

http://instagram.com/icemobile

https://www.facebook.com/IceMobileAmsterdam

https://twitter.com/IceMobile

http://icemobile.com/blog

https://linkedin.com/company/icemobile

Follow us and like us on:

The mobile agency for food retail

Copyright © A. Witteman & R. van den Oever, All Rights Reserved.

Recommended