1. Scenarios An old approach to user stories XP2011 Johannes Brodwall, Storyteller Steria Norway

2. ”Tell me a story about stories”

3. (May not be strictly true)

4. Campfire

5. Through stories

6. Community

7. Understanding

8. Stories:

9. Conflict

10. Heroes

11. Action

12. Resolution

13. User stories

14. (User stories != stories)

15. Johannes Brodwall, Storyteller Steria Norway

16. ”Tell me a story about your experience”

17. Use cases

19. Excited

20. Deluge of details

21. Detail is the opposite of value

22. User stories

24. Excited

25. Deluge of details

26. Shoebox of ”stories”

27. Or worse: Jira

28. Third time’s the charm

29. ”Tell me a story about a system”

30. The story of desire

31. 1.User craves stuff 2.User goes to web shop 3.User finds stuff 4.User puts stuff in shopping cart 5.User enters address 6.User pays 7.…. 8.User gets stuff

32. 1.Conflict (User craves stuff) 2.Trigger (User goes to web shop) 3.Action (User finds stuff) 4.… 5.… 6.… 7.…. 8.Resolution (User gets stuff)

34. The story of disturbance

35. 1.There is a disturbance in the force 2.Operator becomes aware 3.Power plant has already reported reserves to System 4.Operator finds reserves 5.Operator activates reserves 6.System sends activation request to Power Plant 7.System reports activation to Accounting for payment 8.Balance is restored

36. That is: Electricity consumption does not match production

37. Potentially bad

38. Appliance destroyed or without power

39. In other words: Warm beer!

40. 1.There is a disturbance in the force 2.Operator becomes aware 3.Power plant has already reported reserves to System 4.Operator finds reserves 5.Operator activates reserves 6.System sends activation request to Power Plant 7.System reports activation to Accounting for payment 8.Balance is restored

41. 1.There is a disturbance in the force 2.Operator becomes aware 3.Power plant has already reported reserves to System 4.Operator finds reserves in system 5.Operator activates reserves in system 6.System sends activation request to Power Plant 7.System reports activation to Accounting for payment 8.Balance is restored

42. 1.There is a disturbance in the force 2.Operator becomes aware 3.Power plant has already reported reserves to System 4.Operator finds reserves 5.Operator activates reserves 6.System sends activation request to Power Plant 7.System reports activation to Accounting for payment 8.Balance is restored

43. 1.There is a disturbance in the force 2.Operator becomes aware 3.Power plant has already reported reserves to System 4.Operator finds reserves 5.Operator activates reserves 6.System sends activation request to Power Plant 7.System reports activation to Accounting for payment 8.Balance is restored

44. The impatient story of disturbance

45. 1.There is a disturbance in the force 2.Operator becomes aware 3.System has already retrieved reserves from Legacy System 4.Operator finds reserves 5.Operator activates reserves 6.System reports activation to Legacy System for distributions 7.Balance is restored

46. ”Tell me how the story ends”

47. Understanding

48. Plan per sprint

49. (1 step/variation = 1 feature)

50. Plan per release

51. (Scenario in current context)

52. The impatient story of disturbance

53. Happy users

54. Cold beer

55. 1. Conflict: Something happens in the world 2. Trigger: System is triggered #. Action: User displays info in System - Variation: Something else happens #. User enters info into system #. System gets info from Other system #. System sends info to Other system #. Other system sends info to system #. Other system gets info from system #. … 20. Resolution: Order is restored Understand Plan sprints Plan releases Scenarios for requirements Johannes Brodwall jb@steria.no @jhannes johannesbrodwall.com