User stories: Difference between revisions
From Modelado Foundation
imported>Cnewburn (Created page with "= User Stories = The purpose of this page is to gather requirements, in the form of user stories, for HHAT. A user story captures the essence of the requirement without over...") |
imported>Cnewburn |
||
Line 1: | Line 1: | ||
The purpose of this page is to gather requirements, in the form of user stories, for HHAT. | The purpose of this page is to gather requirements, in the form of user stories, for HHAT. | ||
Revision as of 15:21, December 16, 2016
The purpose of this page is to gather requirements, in the form of user stories, for HHAT.
A user story captures the essence of the requirement without over-constraining the implementation. It's tied to a role and a benefit. User stories take the following form:
As a <role>, I want <function>, so that <benefit>, subject to the following acceptance criteria <list>.
Please take this approach
- Start each user story with a new subsection, using two equals signs and a space on either side of a title
- Follow the template shown below
User story name 1
As a <role>, I want <function>, so that <benefit>, subject to the following acceptance criteria
* item 1 * item 2 * item 3 * item 4
<Your Name> <Project(s) that this would benefit> <Link to other related collateral>
User story name 2
As a <role>, I want <function>, so that <benefit>, subject to the following acceptance criteria
* item 1 * item 2 * item 3 * item 4
<Your Name> <Project(s) that this would benefit> <Link to other related collateral>