User stories

460 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
460
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

User stories

  1. 1. Your User Stories Are BadAnd You Should Feel Bad John ClearyLead Web Developer, DocNet@TheRealBifterWednesday, 1 May 13
  2. 2. We all know what UserStories are, right?Wednesday, 1 May 13
  3. 3. As a {user}I want {some_feature}so that {i_get_value}1/3 - THE CARDWednesday, 1 May 13
  4. 4. The Conversationwith the user2/3 - THE CONVERSATIONWednesday, 1 May 13
  5. 5. public function theConfirmation(){// tests which convey the detail// and tell us when we are done}3/3 - THE CONFIRMATIONWednesday, 1 May 13
  6. 6. The Three Little PigsWednesday, 1 May 13
  7. 7. Story:As a Pig I want a house so thatI am safe and warmWednesday, 1 May 13
  8. 8. STRAW HOUSEWednesday, 1 May 13
  9. 9. WOLF ATTACK!Wednesday, 1 May 13
  10. 10. Story:As a Pig I want a house so thatI am safe and warmTests:Does the structurewithstand strong winds?Wednesday, 1 May 13
  11. 11. WOODEN HOUSEWednesday, 1 May 13
  12. 12. WOLF ATTACK - AGAINWednesday, 1 May 13
  13. 13. Story:As a Pig I want a house so thatI am safe and warmTests:Does the structurewithstand strong winds ofup to 60mphWednesday, 1 May 13
  14. 14. BRICK HOUSEWednesday, 1 May 13
  15. 15. The moral of the storyis...Wednesday, 1 May 13
  16. 16. ... that our user storiesshould be ...Wednesday, 1 May 13
  17. 17. IndependentNegotiableValuableEstimableSmallTestableWednesday, 1 May 13
  18. 18. Should not rely on otherstoriesUSER STORIES...INDEPENDENTWednesday, 1 May 13
  19. 19. Focus on verbalcommunicationUSER STORIES...NEGOTIABLEWednesday, 1 May 13
  20. 20. “What should I do if myusers stories don’t fit onthe card”Wednesday, 1 May 13
  21. 21. “Use smaller cards”Wednesday, 1 May 13
  22. 22. Should be written fromthe user’s perspectiveUSER STORIES...VALUABLEWednesday, 1 May 13
  23. 23. “Implement a centralisedlogging system” isprobably not a user storyWednesday, 1 May 13
  24. 24. Must be estimableUSER STORIES...ESTIMABLEWednesday, 1 May 13
  25. 25. Need to fit within thelength of the sprintUSER STORIES...SMALLWednesday, 1 May 13
  26. 26. Need acceptancecriteriaUSER STORIES...TESTABLEWednesday, 1 May 13
  27. 27. So, why do my userstories suck?Wednesday, 1 May 13
  28. 28. They are too smallYOUR STORIES SUCK BECAUSE© quarksteilchen “Tiny Origami Swan Try 1“ from flikrWednesday, 1 May 13
  29. 29. They rely on other storiesYOUR STORIES SUCK BECAUSE© bigoteetoe “Bread & Butter” from flikrWednesday, 1 May 13
  30. 30. They are just goldplatingYOUR STORIES SUCK BECAUSEWednesday, 1 May 13
  31. 31. There is too much detailYOUR STORIES SUCK BECAUSE© Treefiddy “Grandfathers Watch, B&W“ from flikrWednesday, 1 May 13
  32. 32. You did too much planningYOUR STORIES SUCK BECAUSEWednesday, 1 May 13
  33. 33. You wrote themYOUR STORIES SUCK BECAUSE© a2gemma “A Pair Hard At Work“ from flikrWednesday, 1 May 13
  34. 34. How do I make mystories less sucky?Wednesday, 1 May 13
  35. 35. 1. Know your usersWednesday, 1 May 13
  36. 36. 2. Get users to write thestoriesWednesday, 1 May 13
  37. 37. 3. Use user proxies ifthe user is not availableWednesday, 1 May 13
  38. 38. 4. Run workshopsWednesday, 1 May 13
  39. 39. 5. Have project goalsand sprint goalsWednesday, 1 May 13
  40. 40. 6. If the story is too bigthen “slice the cake”Wednesday, 1 May 13
  41. 41. 7. Know what estimatesare forWednesday, 1 May 13
  42. 42. 8. Postpone designWednesday, 1 May 13
  43. 43. 9. Accept that noteverything is a storyWednesday, 1 May 13
  44. 44. 10. Review your stories(using INVEST)Wednesday, 1 May 13
  45. 45. Thank you John ClearyLead Web Developer, DocNet@TheRealBifterbit.ly/bad-storiesWednesday, 1 May 13

×