Embed Size (px)
DESCRIPTION
Scenarios An old approach to user stories. XP2011 Johannes Brodwall , Storyteller Steria Norway. ”Tell me a story about stories ”. (May not be strictly true). Campfire. Through s tories. Community. Understanding. Stories :. Conflict. Heroes. Action. Resolution. User stories. - PowerPoint PPT Presentation
Citation preview
ScenariosAn old approach to user
storiesXP2011
Johannes Brodwall, StorytellerSteria Norway
”Tell me a story about stories”
(May not be strictly true)
Campfire
Through stories
Community
Understanding
Stories:
Conflict
Heroes
Action
Resolution
User stories
(User stories != stories)
Johannes Brodwall, StorytellerSteria Norway
”Tell me a story about your
experience”
Use cases
Excited
Deluge of details
Detail is the opposite of value
User stories
Excited
Deluge of details
Shoebox of ”stories”
Or worse: Jira
Third time’s the charm
”Tell me a story about a system”
The story of desire
1. User craves stuff2. User goes to web shop3. User finds stuff4. User puts stuff in shopping cart5. User enters address6. User pays7. ….8. User gets stuff
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)
The story of disturbance
1. There is a disturbance in the force2. Operator becomes aware3. Power plant has already reported reserves to
System4. Operator finds reserves5. Operator activates reserves6. System sends activation request to Power
Plant7. System reports activation to Accounting for
payment8. Balance is restored
That is: Electricity consumption does not match
production
Potentially bad
Appliance destroyed or without power
In other words: Warm beer!
1. There is a disturbance in the force2. Operator becomes aware3. Power plant has already reported reserves to
System4. Operator finds reserves5. Operator activates reserves6. System sends activation request to Power
Plant7. System reports activation to Accounting for
payment8. Balance is restored
1. There is a disturbance in the force2. Operator becomes aware3. Power plant has already reported reserves to
System4. Operator finds reserves in system5. Operator activates reserves in system6. System sends activation request to Power
Plant7. System reports activation to Accounting for
payment8. Balance is restored
1. There is a disturbance in the force2. Operator becomes aware3. Power plant has already reported reserves to
System4. Operator finds reserves5. Operator activates reserves6. System sends activation request to Power
Plant7. System reports activation to Accounting for
payment8. Balance is restored
1. There is a disturbance in the force2. Operator becomes aware3. Power plant has already reported reserves to
System4. Operator finds reserves5. Operator activates reserves6. System sends activation request to Power
Plant7. System reports activation to Accounting for
payment8. Balance is restored
The impatient story of disturbance
1. There is a disturbance in the force2. Operator becomes aware3. System has already retrieved
reserves from Legacy System4. Operator finds reserves5. Operator activates reserves6. System reports activation to Legacy
System for distributions7. Balance is restored
”Tell me how the story ends”
Understanding
Plan per sprint
(1 step/variation = 1 feature)
Plan per release
(Scenario in current context)
The impatient story of disturbance
Happy users
Cold beer
1. Conflict: Something happens in the world2. 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 [email protected]@jhannesjohannesbrodwall.com
