user stories

45
Your User Stories Are Bad And You Should Feel Bad John Cleary Lead Web Developer, DocNet @TheRealBifter Wednesday, 1 May 13

Upload: john-cleary

Post on 02-Dec-2014

428 views

Category:

Documents


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: User stories

Your User Stories Are Bad And You Should Feel Bad John ClearyLead Web Developer, DocNet@TheRealBifter

Wednesday, 1 May 13

Page 2: User stories

We all know what User Stories are, right?

Wednesday, 1 May 13

Page 3: User stories

As a {user}I want {some_feature}so that {i_get_value}

1/3 - THE CARD

Wednesday, 1 May 13

Page 4: User stories

The Conversation

with the user

2/3 - THE CONVERSATION

Wednesday, 1 May 13

Page 5: User stories

public function theConfirmation(){ // tests which convey the detail // and tell us when we are done}

3/3 - THE CONFIRMATION

Wednesday, 1 May 13

Page 6: User stories

The Three Little Pigs

Wednesday, 1 May 13

Page 7: User stories

Story:As a Pig I want a house so that I am safe and warm

Wednesday, 1 May 13

Page 8: User stories

STRAW HOUSE

Wednesday, 1 May 13

Page 9: User stories

WOLF ATTACK!

Wednesday, 1 May 13

Page 10: User stories

Story:As a Pig I want a house so that I am safe and warm

Tests:Does the structure withstand strong winds?

Wednesday, 1 May 13

Page 11: User stories

WOODEN HOUSE

Wednesday, 1 May 13

Page 12: User stories

WOLF ATTACK - AGAIN

Wednesday, 1 May 13

Page 13: User stories

Story:As a Pig I want a house so that I am safe and warm

Tests:Does the structure withstand strong winds of up to 60mph

Wednesday, 1 May 13

Page 14: User stories

BRICK HOUSE

Wednesday, 1 May 13

Page 15: User stories

The moral of the story is...

Wednesday, 1 May 13

Page 16: User stories

... that our user stories should be ...

Wednesday, 1 May 13

Page 17: User stories

IndependentNegotiableValuableEstimableSmallTestable

Wednesday, 1 May 13

Page 18: User stories

Should not rely on other stories

USER STORIES...

INDEPENDENT

Wednesday, 1 May 13

Page 19: User stories

Focus on verbal communication

USER STORIES...

NEGOTIABLE

Wednesday, 1 May 13

Page 20: User stories

“What should I do if my users stories don’t fit on

the card”

Wednesday, 1 May 13

Page 21: User stories

“Use smaller cards”

Wednesday, 1 May 13

Page 22: User stories

Should be written from the user’s perspective

USER STORIES...

VALUABLE

Wednesday, 1 May 13

Page 23: User stories

“Implement a centralised logging system” is

probably not a user story

Wednesday, 1 May 13

Page 24: User stories

Must be estimableUSER STORIES...

ESTIMABLE

Wednesday, 1 May 13

Page 25: User stories

Need to fit within the length of the sprint

USER STORIES...

SMALL

Wednesday, 1 May 13

Page 26: User stories

Need acceptance criteria

USER STORIES...

TESTABLE

Wednesday, 1 May 13

Page 27: User stories

So, why do my user stories suck?

Wednesday, 1 May 13

Page 28: User stories

They are too smallYOUR STORIES SUCK BECAUSE

© quarksteilchen “Tiny Origami Swan Try 1“ from flikr

Wednesday, 1 May 13

Page 29: User stories

They rely on other storiesYOUR STORIES SUCK BECAUSE

© bigoteetoe “Bread & Butter” from flikr

Wednesday, 1 May 13

Page 30: User stories

They are just goldplatingYOUR STORIES SUCK BECAUSE

Wednesday, 1 May 13

Page 31: User stories

There is too much detailYOUR STORIES SUCK BECAUSE

© Treefiddy “Grandfather's Watch, B&W“ from flikr

Wednesday, 1 May 13

Page 32: User stories

You did too much planningYOUR STORIES SUCK BECAUSE

Wednesday, 1 May 13

Page 33: User stories

You wrote themYOUR STORIES SUCK BECAUSE

© a2gemma “A Pair Hard At Work“ from flikr

Wednesday, 1 May 13

Page 34: User stories

How do I make my stories less sucky?

Wednesday, 1 May 13

Page 35: User stories

1. Know your users

Wednesday, 1 May 13

Page 36: User stories

2. Get users to write the stories

Wednesday, 1 May 13

Page 37: User stories

3. Use user proxies if the user is not available

Wednesday, 1 May 13

Page 38: User stories

4. Run workshops

Wednesday, 1 May 13

Page 39: User stories

5. Have project goals and sprint goals

Wednesday, 1 May 13

Page 40: User stories

6. If the story is too big then “slice the cake”

Wednesday, 1 May 13

Page 41: User stories

7. Know what estimates are for

Wednesday, 1 May 13

Page 42: User stories

8. Postpone design

Wednesday, 1 May 13

Page 43: User stories

9. Accept that not everything is a story

Wednesday, 1 May 13

Page 44: User stories

10. Review your stories (using INVEST)

Wednesday, 1 May 13

Page 45: User stories

Thank youJohn ClearyLead Web Developer, [email protected]/bad-stories

Wednesday, 1 May 13