This repository has been archived by the owner on Jan 22, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Product Backlog
Will Fenton edited this page Nov 29, 2019
·
22 revisions
ID | Done | Requirement | Rationale | Size | Risk |
---|---|---|---|---|---|
4 | ✓ | Moods emoticons and colors are consistent across the entire application. | A consistent design language is important to make the app intuitive. | 2 | Low |
6 | ✓ | Users can view mood events in their history and see all its available details. | Recording mood events is pointless if users can't see their past mood events. | 4 | Low |
7 | ✓ | Users can edit the details of mood events in their mood history. | Users may want to go back and add more detail to their past mood events, or change the details. | 4 | Low |
8 | ✓ | Users can delete mood events from their mood history. | Users may have accidentally posted a mood event, or someone took their phone and posted a mood event, and they may want to delete it. | 2 | Low |
10 | ✓ | Users can add an image to a mood event. | An image can provide context to a mood event. | 3 | Medium |
13 | ✓ | Users have unique usernames. | Users need distinct usernames to be distinguishable from one another. | 1 | Low |
16 | ✓ | Users can filter their mood history to show only mood events with a particular emotional state. | Users may want to find specific mood events, and it is easier to find them if you can filter the list. | 2 | Low |
17 | ✓ | Users can request another user to follow their most recent mood event. | Users may want to see their friends mood events. | 3 | Medium |
18 | ✓ | Users can grant other users permission to follow their most recent mood event. | Users may not want another user to see their mood events, so it requires permission. | 4 | Medium |
19 | ✓ | Users can view as a list the most recent mood events of the users they follow. | Mood events of users that a given user follows should be easily accessible from one place. | 4 | Low |
20 | ✓ | The list of mood events of users that a given user follows is sorted in reverse chronological order (most recent first). | Users most likely want to see the most recent mood events from people they follow. | 1 | Low |
24 | ✓ | Users can see a map of mood events (with locations) of other users that they follow. | Users may want to see where their friends mood events happened, without viewing each one individually from the mood history. | 5 | High |
25 | ✓ | Mood events from other users that a user follows on the map show their emotional states. | The mood of a mood event is the most important part, and should be visible without viewing the details of the mood event. | 3 | Low |
ID | Done | Requirement | Rationale | Size | Risk |
---|---|---|---|---|---|
1 | ✓ | There is a mood history to contain user's mood events. | Users should be able to view their past mood events, so mood events need to be stored. | 2 | Low |
2 | ✓ | Users are able to add mood events to their mood history. | Recording mood events is the basic functionality of the application. | 4 | Low |
3 | ✓ | Each mood event should contain a date and time (required), emotional states (required), reason (optional), and social situation (optional). | Date / time and emotional state are the bare minimum, and then users can optionally include more information. | 3 | Low |
5 | ✓ | Mood emoticons and colors are easily distinguishable. | Users should be able to determine the mood at a glance, instead of reading the mood. | 2 | Low |
9 | ✓ | Users can add a reason for a mood event (max 20 characters or 3 words). | Users may want to record the reason for a mood event, so that when they look back they can remember the cause. | 2 | Low |
11 | ✓ | Users can specify the social situation for a mood event. (one of: alone, with one other person, with two to several people, or with a crowd). | In addition to the reason and image, the social situation also gives context to a mood event. | 2 | Low |
12 | ✓ | Users have a user profile. | Users should be able to view their / other user's profile information. | 4 | Medium |
14 | ✓ | Users can view their mood history in a list. | Users should be able to view their mood history. | 4 | Low |
15 | ✓ | Users' mood histories are sorted in reverse chronological order (most recent first). | Users are more likely to want to view their recent mood events. | 1 | Low |
21 | ✓ | Users can optionally attach their current location to a mood event. | User's mood events may be tied to locations (e.g. sad because they're at a funeral home) | 3 | Low |
22 | ✓ | Users can see a map of their mood events (with locations) from their mood history list. | It offers users another way to view their mood history, and analyze patterns in their mood events. | 5 | High |
23 | ✓ | Users' mood events on the map show their emotional states. | The mood of a mood event is the most important part, and should be visible without viewing the details of the mood event. | 3 | Low |
26 | ✓ | User login is authenticated with a password. | User accounts should be secure, without authentication anybody could login to their account and modify their mood history. | 2 | Medium |
27 | ✓ | Users can create an account. | Users need a way to create an account. Tying accounts to phones wouldn't work because users may switch devices and want to keep their history. | 3 | Medium |
28 | ✓ | Users can logout. | Users may want to logout and let their friend use the app on their phone. | 1 | Low |