Goals
- Come up with topics for the weekly Architecture call
Background and strategic fit
- Why are you doing this? How does this relate to your overall product strategy?
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).
Requirements
| Title | Owner | User Story | Date when it will be reviewed | Notes |
|---|
| 1 |
|
|
|
|
|
| 2 |
|
|
|
|
|
| 3 |
|
|
|
|
|
| 4 |
|
|
|
|
|
| 5 |
|
|
|
|
|
| 6 |
|
|
|
|
|
| 7 |
|
|
|
|
|
| 8 |
|
|
|
|
|
| 9 |
|
|
|
|
|
| 10 |
|
|
|
|
|
| 11 |
|
|
|
|
|
| 12 |
|
|
|
|
|
| 13 |
|
|
|
|
|
User interaction and design
- Include any mockups, diagrams or visual designs relating to these requirements.
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|
| (e.g. How we make users more aware of this feature?) | Communicate the decision reached |
Not Doing
- List the features discussed which are out of scope or might be revisited in a later release.