User story
…{{{context}}}
✣ ✣ ✣
{{{wish full}}}
Therefore:
{{{therefore full}}}
✣ ✣ ✣
✣ ✣ ✣
Template
Legend
| color | meaning |
|---|---|
| black | To be implemented in the current variant of the user story. |
| red | Issues that must be researched and resolved before you can start with implementation. |
| grey | Items that will not be implemented in the current variant of the user story (out of scope). |
Verb sentences, please
When composing the title of a user story, use verb sentences and active language. The verbs are the actions and activities users can do with your product. The nouns are the objects or parts that make up your product.
For example:
- To send a message.
- To delete a message.
- To close a partnership.
Story Template
Slightly different from the “As a role I want to function so that I value.”
| When I | situation | am in the city |
| I want to | feature (verb sentence) | withdraw cash |
| so that I | value, benefit | buy some ice cream and quench my thirst. |
Sources
left overs need to extend WebSourceListItem to accommodate ‘epilog’ or ‘about’
- , about the level of spec required.
- about capturing a day in the life which in turn can be used to generate a whole bunch of user stories to fill a story map.
- Dan North & Associates » Dan North » What’s in a story?
- The Common Craft Blog » Lee LeFever » Why This Bathroom Sign Is a Great Explanation
- Mountain Goat Software » Mike Cohn » Advantages of User Stories for Requirements
- Boost » User stories: a beginner’s guide
- Stellman-Greene » Andrew Stellman » Requirements 101: User Stories vs. Use Cases
- Seth’s Blog » Seth Godin » The magic of a spec
- HBR » Juan Pablo Vazquez Sampere » Generating Data on What Customers Really Want
- Mountain Goat Software » Mike Cohn » 4 Reasons to Include Developers in Story Writing