Discount Usability Testing for Agile Teams

Preview:

DESCRIPTION

A talk from Agile Roots in 2010. You can't get the whole picture or much context from the slides.The last part of the talk was referring to how you'll be remembered and your legacy in a social-media-based world.It would be unfortunate if your last status update was the one that you see in the facebook wall post.Video from the talk will be posted later.

Citation preview

Discount Usability Testing

for agile teams

Ben CareyBy day

experiments

@bencarey

A Story

The simplest thing that could possibly work.

“- Don Norman, DOET

There is a big difference between the expertise required to be a designer & that required to be a user. In their work, designers often become experts with the device they are designing. Users are often experts at the task they are trying to perform on the device.

POV

BENEFIT

Our Users

1. Why?

1.1 It Helps

Having usable software is kinda like having edible food.

Welcome to basecamp.

EFFORT EFFECT

1.2 Find Empathy

EMPATHY

RTFMFTM

I Them Himself stereotypes real people

what is a browser?

1.3 Stop Guessing

Seek real feedback and high-bandwidth information through

observation.

2 Anatomy

2.1 Instruction

A few usersA few tasks

A few observersA few beers

A Story CardA Story Card

A Story CardA Story Card

A Story CardA Story Card

A Story Card

A Story Card

A Story Card

A Story Card

A Story Card

A Story CardA Story Card

Cadence

Testing

Observing

Facilitating

You’re not limited to just testing the software.

2.2 A Demo

2.3 Exercise

Finding what you should test.

5 - 10 things

Discount Testing Exercise

Group Debrief

3 Where Next?

3.1 Iterating

WTF?(happened to iteration)

“- Steve Krug, Rocket Surgery Made Easy

... even though a piece of duct tape covering a hole in your pants migh not be pretty, it’s still better than a hole.

Do the minimum that you can to fix the problems.

Tweaks cost less.Tweaks require less work.Tweaks don’t ruin lives or break up families.Small changes can be made sooner.Small changes are more likely to actually happen.Tweaks are less likely to break a bunch of stuff.Most people don’t like change, redesigns annoy them.Tweaks aren’t as risky.Tweaks don’t require a lot of meetings.

from Rocket Surgery Made Easy

3.1 Buy-In

You don’t need buy-in.

#1 Frame it as an experiment

#2 Minimal cost

0%

25%

50%

75%

100%

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

#3 Disproportional returns

POV

Stop building stuff that sucks.

SAS

A few people to test

A few people to observe

Debrief observations

Benefit

Our Users

Thank You!Ben Careythesherpaproject.com@bencarey

team room: lachlanhardy (flickr)

Attribution

corbin sign: jstephenconn (flickr)

discount testing: jenniferconley (iliveindallas.com)

empathy: b0xman (flickr)

big mac: pixelden (flickr)

basecamp: ilker (flickr)

tied up finger: mkmabus (flickr)

lots of paperwork: unk’s dump truck (flickr)

peek: mkambus (flickr)

paper prototype: cesarastudillo (flickr)

iTunes cards: yum9me (flickr)

pizza & beer: add1sun (flickr)

duct tape: andrwj (flickr)

spare change: essgee (flickr)

beakers: femgeek (flickr)

trust me: mkambus (flickr)

Recommended