Difference between revisions of "User story"
Jump to navigation
Jump to search
(→Sources: += HBR » Juan Pablo Vazquez Sampere » Generating Data on What Customers Really Want) |
(→Sources: += Mountain Goat Software » Mike Cohn » 4 Reasons to Include Developers in Story Writing) |
||
| Line 40: | Line 40: | ||
|title=Generating Data on What Customers Really Want | |title=Generating Data on What Customers Really Want | ||
}} 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}}. | }} 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 | |||
|url=http://www.mountaingoatsoftware.com/blog/4-reasons-to-include-developers-in-story-writing#When:14:00:50Z | |||
|site=Mountain Goat Software | |||
|person=Mike Cohn | |||
|title=4 Reasons to Include Developers in Story Writing | |||
}} | |||
Revision as of 04:53, 8 May 2014
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