| Target release | Release name or number |
|---|
| Epic | Link to related Jira epic or feature |
|---|
| Document status |  |
|---|
| Document owner | Unknown User (edcable) |
|---|
| Designer | Lead designer |
|---|
| Developers | Lead developer |
|---|
| QA | Lead tester |
|---|
|
Goals
- 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?
Why did we choose the given technology or component?
Assumptions
- List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).
- Aiming to discuss how we're minimizing impact to community and ensuring upstream compatibility.
Requirements
| # | Title | User Story | Importance | Notes |
|---|
| 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)
|
| 2 |
|
|
|
|
Solution Design
Architectural diagrams and designs for proposed solution.
Implementation
- i.e. show details of the specific configuration or library of the components used
- can speak to details of POC vs production-ready implementation.
Out of Scope
- List the features discussed which are out of scope or might be revisited in a later release.
Questions
Below is a list of questions to be addressed as a result of this requirements document:
- Make sure we cover any proposed impacts this might have on community or existing implementations.
| Question | Outcome |
|---|
| (e.g. How we make users more aware of this feature?) | Communicate the decision reached |