Difference between revisions of "User story"

From Pearl Language
Jump to navigation Jump to search
(→‎Template: += Story Template)
(→‎Template: += Ready to Build)
Line 44: Line 44:
|buy some ice cream and quench my thirst.
|buy some ice cream and quench my thirst.
|}
|}
===Ready to Build===
Describe the user’s adventure as a narrative, a story, until everyone can {{p|back brief}} the story crystal clear, lucid way. In short, make sure the {{p|user story}} is {{p|ready to build}}.


==Sources==
==Sources==

Revision as of 09:45, 18 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.

Sources

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