...
| Page Properties | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals/Scope
- Include a statement describing what this functionality seeks to achieve and provides criteria guidance of how success would be measured or tested. What are we doing what we are going? What important background information is needed for the stories and may describe the pre-conditions or triggers?
Background
Are there any country specific features that should be noted? Who are the personas? Who are the users that will be interacting with this functionality? What are their challenges, responsibilities, and level of connectivity? These personas are intended to be representative archetypes of the key stakeholders who will participate in theses workflows/scenarios.
Assumptions
- What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this features from a tablet).
User Stories
Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
...
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | (e.g. How we make users more aware of this feature?) | Communicate the decision reached | Open, In Progress, Closed, and date of closure |
Out of Scope
- List the features discussed which are out of scope or might be revisited in a later release.
- List the features discussed which are out of scope or might be revisited in a later release.