Difference between revisions of "User story"
Jump to navigation
Jump to search
(→Template: += Issues) |
m (+= abouts) |
||
| Line 56: | Line 56: | ||
==Sources== | ==Sources== | ||
{{WebSourceListItem | {{WebSourceListItem | ||
|url=http://dannorth.net/whats-in-a-story/ | |url=http://dannorth.net/whats-in-a-story/ | ||
| Line 93: | Line 90: | ||
|person=Seth Godin | |person=Seth Godin | ||
|title=The magic of a spec | |title=The magic of a spec | ||
|about=about the level of spec required | |||
}} | }} | ||
{{WebSourceListItem | {{WebSourceListItem | ||
| Line 99: | Line 97: | ||
|person=Juan Pablo Vazquez Sampere | |person=Juan Pablo Vazquez Sampere | ||
|title=Generating Data on What Customers Really Want | |title=Generating Data on What Customers Really Want | ||
|about=about capturing {{p|a day in the life}} which in turn can be used to generate a whole bunch of {{p|user stories}} to fill a {{p|story map}} | |||
}} | }} | ||
{{WebSourceListItem | {{WebSourceListItem | ||
Revision as of 09:52, 19 July 2014
…{{{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. |
Ready to Build
Describe the user’s adventure as a narrative, a story, until everyone can back brief the story crystal clear, lucid way. In short, make sure the user story is ready to build.
Issues
Issues that need to be resolved before the user story can be declared ready to build. Color open issues red. Color them black when resolved. For example:
- How many daily withdrawals are allowed?
- What is the maximum amount someone can withdraw and on what does it depend?
- €500
Sources
- 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, about the level of spec required.
- HBR » Juan Pablo Vazquez Sampere » Generating Data on What Customers Really Want, 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.
- Mountain Goat Software » Mike Cohn » 4 Reasons to Include Developers in Story Writing