| Target release | MVP release (beta 1) |
|---|
| Epic | |
|---|
| Document status |  |
|---|
| Document owner | Derk Snijders |
|---|
| Designer | Derk Snijders |
|---|
| Developers | Lead developer |
|---|
| QA | Lead tester |
|---|
|
Goals
- Provide a first release, the minimal viable product.
- Provide a stable starting point to reflect and plan future incremental development upon.
- Provide a first attempt at delivering a system that can replace the current intranet
- When the MVP is done, the further requirements to replace the current intranet should be identified.
- Have some working, showable results!
Background and strategic fit
This is the first stepping stone in a more long term development process of providing AEGEE (and other NGO's) with a sustainable and usable Online Membersship System. See the project plan for more information.
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 | 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 | | | | |
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.