Difference between revisions of "User story"

Revision as of 08:39, 18 July 2014

…{{{context}}}

✣ ✣ ✣

{{{wish full}}}

Therefore:

{{{therefore full}}}

✣ ✣ ✣

left overs need to extend WebSourceListItem to accommodate ‘epilog’ or ‘about’

@@ Line 1: / Line 1: @@
+{{Oyster
+|goal=be crystal clear on what who wants and why so it can be build
+|stage=Sparkle
+|theme=Agile, Lean, Scrum, Product
+}}
 ==Sources==
+'''left overs''' need to extend WebSourceListItem to accommodate ‘epilog’ or ‘about’
+*, about the level of spec required.
+*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://dannorth.net/whats-in-a-story/
@@ Line 33: / Line 45: @@
 |site=Seth’s Blog
 |person=Seth Godin
-|title=The magic of a spec}}, about the level of spec required.
+|title=The magic of a spec
+}}
 {{WebSourceListItem
 |url=http://blogs.hbr.org/2014/05/generating-data-on-what-customers-really-want/
@@ Line 39: / Line 52: @@
 |person=Juan Pablo Vazquez Sampere
 |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}}.
+}}
 {{WebSourceListItem
 |url=http://www.mountaingoatsoftware.com/blog/4-reasons-to-include-developers-in-story-writing#When:14:00:50Z