|Target release||Release name or number|
|Epic||Link to related JIRA epic or feature|
Sari H. Pitkänen
- E.g. Simplify the user experience, reduce friction etc...
Background and strategic fit
Why are you doing this? How does this relate to your overall product strategy?
- List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).
|1||Short identifier for the story||Describe the user and what they are trying to achieve||Must Have|
- Additional considerations or noteworthy references (links, issues)
| || || || || |
User interaction and design
Include any mockups, diagrams or visual designs relating to these requirements.
Below is a list of questions to be addressed as a result of this requirements document:
|(e.g. How we make users more aware of this feature?)||Communicate the decision reached|
- List the features discussed which are out of scope or might be revisited in a later release.