-
Notifications
You must be signed in to change notification settings - Fork 0
BackLog
Pineapple0111 edited this page Mar 13, 2020
·
39 revisions
Points Total: 145
Points Completed: 0
Requests
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 01.01.01 | Rider request ride | 5 | HIGH | TODO | P1 |
| US 01.02.01 | Rider view own request | 5 | HIGH | TODO | P1 |
| US 01.03.01 | Rider get notice of request being accepted | 7 | HIGH | ||
| US 01.04.01 | Rider can cancel request | 5 | HIGH | COMPLETE | P1 |
| US 01.05.01 | Rider can contact driver who accepted their request | 5 | MEDIUM | COMPLETE | P2 |
| US 01.06.01 | Rider can get price estimate and can add tip if desired | 3 | MEDIUM | ||
| US 01.07.01 | Rider can confirm the completion of request and pay | 10 | HIGH | ||
| US 01.08.01 | Rider can cancel ride before pickup | 5 | HIGH | TODO | P1 |
| US 01.10.01 | Rider can see info of the driver that accepted their request | 5 | MEDIUM | ||
| US 01.11.01 | Rider can rate driver (binary rating) | 5 | MEDIUM |
Status
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 02.01.01 | User can see the status of their request | 6 | HIGH | TODO | P1 |
User Profile
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 03.01.01 | User have profile with unique-username and contact info | 5 | HIGH | COMPLETE | P2 |
| US 03.02.01 | User can edit contact info | 5 | LOW | COMPLETE | P2 |
| US 03.03.01 | User can retrieve contact info of anything whom they've interacted with before | 6 | LOW | COMPLETE | P2 |
Searching
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 04.01.01 | Driver can see a list of request sorted based on geolocation | 8 | HIGH |
Accepting
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 05.01.01 | Driver can accept request and accept payment upon completion of the ride | 6 | HIGH | ||
| US 05.02.01 | Driver can view the last request that he accepted | 4 | HIGH | ||
| US 05.03.01 | Driver can see if their offer was accepted by the server | 6 | HIGH |
Offline behavior
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 06.01.01 | Driver can see ride history offline | 3 | LOW | ||
| US 06.02.01 | Rider can see current request offline | 3 | LOW |
Location
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 07.01.01 | Rider can specify request start point and destination on interactive map | 10 | HIGH | COMPLETE | P1 |
| US 07.02.01 | Driver can view request start point and destination on interactive map | 8 | HIGH |
Payment
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 08.01.01 | Rider can generate QRbuck | 10 | HIGH | COMPLETE | P3 |
| US 08.02.01 | Driver can scan QRbuck | 10 | HIGH | COMPLETE | P3 |
TODO: better description, more detailed!
create card in github project using the user story number, then assignment team member into each story ---- and the assignment should be roughly equal amongst the members
CMPUT301W20T17