Difference between revisions of "User story"

From Pearl Language
Jump to navigation Jump to search
(→‎Template: += Ready to Build)
(→‎Template: += Issues)
Line 47: Line 47:
===Ready to Build===
===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}}.
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}}.
===Issues===
''Issues that need to be resolved before the {{p|user story}} can be declared {{p|ready to build}}. Color open issues '''{{color|red|red}}'''. Color them '''{{color|black|black}}''' when resolved.''
For example:
*{{color|red|How many daily withdrawals are allowed?}}
*What is the maximum amount someone can withdraw and on what does it depend?
**€500


==Sources==
==Sources==

Revision as of 10:07, 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.

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

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

Retrieved from "http://pearllanguage.org/index.php?title=User_story&oldid=2071"