Questions Not Stories (Agile Cambridge 2012)

63
Questions not Stories Agile Cambridge 2012 Adrian Howard (@adrianh) quietstars.com

description

Workshop on user stories vs hypothesis & experiments from the Lean Startup community, presented on September 27 at Agile Cambridge 2012.

Transcript of Questions Not Stories (Agile Cambridge 2012)

Page 1: Questions Not Stories (Agile Cambridge 2012)

Questions not Stories

Agile Cambridge 2012

Adrian Howard (@adrianh) quietstars.com

Page 2: Questions Not Stories (Agile Cambridge 2012)

Please ask questions

Page 3: Questions Not Stories (Agile Cambridge 2012)

Disclaimer 1: Eh?

Page 4: Questions Not Stories (Agile Cambridge 2012)

Disclaimer 2:I could be confused

and stupid

Page 5: Questions Not Stories (Agile Cambridge 2012)

Who am I?

Page 6: Questions Not Stories (Agile Cambridge 2012)

Swear Jar

Page 7: Questions Not Stories (Agile Cambridge 2012)

(obligatory cute animal slide)

Page 8: Questions Not Stories (Agile Cambridge 2012)

Who are you?

Page 9: Questions Not Stories (Agile Cambridge 2012)

Disclaimer 3:Be careful if you’re

new to agile

Page 10: Questions Not Stories (Agile Cambridge 2012)

Chatham House Rule applies please

Page 11: Questions Not Stories (Agile Cambridge 2012)

"When a meeting, or part thereof, is held under the Chatham House Rule,

participants are free to use the information received, but neither the

identity nor the affiliation of the speaker(s), nor that of any other

participant, may be revealed"

Page 12: Questions Not Stories (Agile Cambridge 2012)

Exploring user stories

Page 13: Questions Not Stories (Agile Cambridge 2012)

Exercise

• 5m

• Everybody write a user story

• Real (if you can) or made up

• “As a <user>, I want <goal> so that <reason>” template if you want to, but not compulsory

Page 14: Questions Not Stories (Agile Cambridge 2012)

Exercise

• 5m

• Each person explain their user story to the group

• Card. Conversation. Confirmation.

Page 15: Questions Not Stories (Agile Cambridge 2012)

Exercise

• 5m

• Each table write on post-it notes

• User story likes/dislikes, good/bad points, purposes, etc.

Page 16: Questions Not Stories (Agile Cambridge 2012)

Relax

Page 17: Questions Not Stories (Agile Cambridge 2012)

Stories are statements

Page 18: Questions Not Stories (Agile Cambridge 2012)

Stories describe the product

Page 19: Questions Not Stories (Agile Cambridge 2012)

Product owner says

“doing X will return business value”

Page 20: Questions Not Stories (Agile Cambridge 2012)

Breakdown stories by splitting & thinning

Page 21: Questions Not Stories (Agile Cambridge 2012)

Stories = known knowns.

Page 22: Questions Not Stories (Agile Cambridge 2012)

What aboutknown unknowns?

Page 23: Questions Not Stories (Agile Cambridge 2012)

The Lean Startup

“A true experiment follows the scientific method. It begins with a clear hypothesis that makes predictions about what is supposed to happen. It then tests those predictions empirically”

Page 24: Questions Not Stories (Agile Cambridge 2012)

The Lean Startup

• Come up with hypothesis

• Design experiment

• Run experiment

• Validate/Invalidate hypothesis

• Repeat

Page 25: Questions Not Stories (Agile Cambridge 2012)

The Lean Startup

Page 26: Questions Not Stories (Agile Cambridge 2012)

Moving from Stories to Hypotheses

Page 27: Questions Not Stories (Agile Cambridge 2012)

As a potential user, I want register using

twitter so that I don’t have to fill out a

registration form.

Page 28: Questions Not Stories (Agile Cambridge 2012)

Step 1

Page 29: Questions Not Stories (Agile Cambridge 2012)

As a potential user, I want register using

twitter so that I don’t have to fill a

registration form ?

Page 30: Questions Not Stories (Agile Cambridge 2012)

As a potential user, I want register using

twitter so that I don’t have to fill a

registration form ?

Page 31: Questions Not Stories (Agile Cambridge 2012)

Step 2: Ask why?

• Increase # registrations?

• More social media penetration for marketing?

• Allow notification features?

Page 32: Questions Not Stories (Agile Cambridge 2012)

Step 3: What’s our hypothesis?

Page 33: Questions Not Stories (Agile Cambridge 2012)

Allowing users to register with twitter will drop abandoned registrations by 5%

Page 34: Questions Not Stories (Agile Cambridge 2012)

Exercise• 5m

• Pair up

• Pick a story card and apply:

1. Question mark

2. Why (or “whys”) ?

3. Generate hypothesis

Page 35: Questions Not Stories (Agile Cambridge 2012)

Building Experiments

Page 36: Questions Not Stories (Agile Cambridge 2012)

Experiments produce learning

not product

Page 37: Questions Not Stories (Agile Cambridge 2012)

Experiments can get thrown away

Page 38: Questions Not Stories (Agile Cambridge 2012)

Focus on speed of feedback

Page 39: Questions Not Stories (Agile Cambridge 2012)

Allowing users to register with twitter will drop abandoned registrations by 5%

Page 40: Questions Not Stories (Agile Cambridge 2012)

Experiment

• Built fake “register with twitter” link which led to nice error message

• Released to segment of customers on live site

• Measured how many new users tried it

• <1% - hypothesis invalid

Page 41: Questions Not Stories (Agile Cambridge 2012)

Not just A/B testing

Page 42: Questions Not Stories (Agile Cambridge 2012)

Exercise

• 5m

• Pair up

• Pick a hypothesis

• Come up with as many ways to validate the hypothesis as possible

Page 43: Questions Not Stories (Agile Cambridge 2012)

Exercise

• 5m

• Each table write on post-it notes

• Hypothesis/experiment likes/dislikes, good/bad points, purposes, etc.

Page 44: Questions Not Stories (Agile Cambridge 2012)

The Good, the Bad & the Ugly

Page 45: Questions Not Stories (Agile Cambridge 2012)

Alignment on value

Page 46: Questions Not Stories (Agile Cambridge 2012)

Helps build an experiment culture

Page 47: Questions Not Stories (Agile Cambridge 2012)

It’s hypotheses before, during and after development

Page 48: Questions Not Stories (Agile Cambridge 2012)

Metric-First Development

Page 49: Questions Not Stories (Agile Cambridge 2012)

Encourages value-oriented infrastructure

Page 50: Questions Not Stories (Agile Cambridge 2012)

Hypotheses talk about business value directly

Page 51: Questions Not Stories (Agile Cambridge 2012)

Success changes

Page 52: Questions Not Stories (Agile Cambridge 2012)

Splitting/thinning changes

Page 53: Questions Not Stories (Agile Cambridge 2012)

Where’s the user?

Page 54: Questions Not Stories (Agile Cambridge 2012)

Where’s the delight?

Page 55: Questions Not Stories (Agile Cambridge 2012)

Horde of zombie experiments

Page 56: Questions Not Stories (Agile Cambridge 2012)

Where are the running, tested

features?

Page 57: Questions Not Stories (Agile Cambridge 2012)

What happens when I can’t

validate cheaply?

Page 58: Questions Not Stories (Agile Cambridge 2012)

What about non-startup contexts?

Page 59: Questions Not Stories (Agile Cambridge 2012)

Some folk find reality hurts

Page 60: Questions Not Stories (Agile Cambridge 2012)

Further Reading• Lean Startup by Eric Ries

• Running Lean by Ash Maurya

• The Four Steps to the Epiphany by Steve Blank

• The Entrepreneur’s Guide to Customer Development by Brant Cooper & Patrick Vlaskovits

• The Startup Owner's Manual by Steve Blank (not read)

Page 61: Questions Not Stories (Agile Cambridge 2012)

I <heart> feedback

Page 62: Questions Not Stories (Agile Cambridge 2012)

Questions?

Page 63: Questions Not Stories (Agile Cambridge 2012)

Adrian [email protected]

twitter.com/adrianhlanyrd.com/profile/adrianh

quietstars.com