Use Scenarios for your product backlog

720 views

Published on

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
720
On SlideShare
0
From Embeds
0
Number of Embeds
38
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Use Scenarios for your product backlog

  1. 1. ScenariosAn old approach to userstories<br />XP2011<br />Johannes Brodwall, Storyteller<br />SteriaNorway<br />
  2. 2. ”Tell me a story aboutstories”<br />
  3. 3. (May not be strictly true)<br />
  4. 4. Campfire<br />
  5. 5. Throughstories<br />
  6. 6. Community<br />
  7. 7. Understanding<br />
  8. 8. Stories:<br />
  9. 9. Conflict<br />
  10. 10. Heroes<br />
  11. 11. Action<br />
  12. 12. Resolution<br />
  13. 13. Userstories<br />
  14. 14. (Userstories != stories)<br />
  15. 15. Johannes Brodwall, Storyteller<br />SteriaNorway<br />
  16. 16. ”Tell me a story aboutyourexperience”<br />
  17. 17. Use cases<br />
  18. 18.
  19. 19. Excited<br />
  20. 20. Delugeofdetails<br />
  21. 21. Detail is theoppositeofvalue<br />
  22. 22. Userstories<br />
  23. 23.
  24. 24. Excited<br />
  25. 25. Delugeofdetails<br />
  26. 26. Shoeboxof ”stories”<br />
  27. 27. Or worse: Jira<br />
  28. 28. Thirdtime’sthecharm<br />
  29. 29. ”Tell me a story about a system”<br />
  30. 30. The story ofdesire<br />
  31. 31. Usercravesstuff<br />Usergoes to web shop<br />Userfindsstuff<br />Userputsstuff in shopping cart<br />Userentersaddress<br />Userpays<br />….<br />Usergetsstuff<br />
  32. 32. Conflict(Usercravesstuff)<br />Trigger (Usergoes to web shop)<br />Action (Userfindsstuff)<br />…<br />…<br />…<br />….<br />Resolution(Usergetsstuff)<br />
  33. 33.
  34. 34. The story ofdisturbance<br />
  35. 35. There is a disturbance in theforce<br />Operator becomesaware<br />Power plant has alreadyreported reserves to System<br />Operator finds reserves<br />Operator activates reserves<br />System sendsactivationrequest to Power Plant<br />System reportsactivation to Accounting for payment<br />Balance is restored<br />
  36. 36. That is: Electricityconsumptiondoes not match production<br />
  37. 37. Potentially bad<br />
  38. 38. Appliancedestroyed or withoutpower<br />
  39. 39. In otherwords: Warmbeer!<br />
  40. 40. There is a disturbance in theforce<br />Operator becomesaware<br />Power plant has alreadyreported reserves to System<br />Operator finds reserves<br />Operator activates reserves<br />System sendsactivationrequest to Power Plant<br />System reportsactivation to Accounting for payment<br />Balance is restored<br />
  41. 41. There is a disturbance in theforce<br />Operator becomesaware<br />Power plant has alreadyreported reserves to System<br />Operator finds reserves in system<br />Operator activates reserves in system<br />System sendsactivationrequest to Power Plant<br />System reportsactivation to Accounting for payment<br />Balance is restored<br />
  42. 42. There is a disturbance in theforce<br />Operator becomesaware<br />Power plant has alreadyreported reserves to System<br />Operator finds reserves<br />Operator activates reserves<br />System sendsactivationrequest to Power Plant<br />System reportsactivation to Accounting for payment<br />Balance is restored<br />
  43. 43. There is a disturbance in theforce<br />Operator becomesaware<br />Power plant has alreadyreported reserves to System<br />Operator finds reserves<br />Operator activates reserves<br />System sendsactivationrequest to Power Plant<br />System reportsactivation to Accounting for payment<br />Balance is restored<br />
  44. 44. The impatient story ofdisturbance<br />
  45. 45. There is a disturbance in theforce<br />Operator becomesaware<br />System has alreadyretrieved reserves from Legacy System<br />Operator finds reserves<br />Operator activates reserves<br />System reportsactivation to Legacy System for distributions<br />Balance is restored<br />
  46. 46. ”Tell mehowthe story ends”<br />
  47. 47. Understanding<br />
  48. 48. Plan per sprint<br />
  49. 49. (1 step/variation = 1 feature)<br />
  50. 50. Plan per release<br />
  51. 51. (Scenario in currentcontext)<br />
  52. 52. The impatient story ofdisturbance<br />
  53. 53. Happyusers<br />
  54. 54. Cold beer<br />
  55. 55. Scenarios for requirements<br /><ul><li>Understand
  56. 56. Plan sprints
  57. 57. Planreleases</li></ul>1. Conflict:Somethinghappens in the world<br />2.Trigger: System is triggered<br />#. Action:User displays info in System<br /> - Variation: Somethingelsehappens<br />#. Userentersinfointo system<br />#. System getsinfo from Other system<br />#. System sendsinfo to Other system<br />#. Other system sendsinfo to system<br />#. Other systemgetsinfo from system<br />#. …<br />20.Resolution:Order is restored<br />Johannes Brodwall<br />jb@steria.no<br />@jhannes<br />johannesbrodwall.com<br />

×