-
Notifications
You must be signed in to change notification settings - Fork 0
BackLog
jonny21099 edited this page Mar 25, 2020
·
39 revisions
Points Total: 131
Points Completed: 77
Requests
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 01.01.01 | Rider request ride | 5 | HIGH | COMPLETE | P1 |
| US 01.02.01 | Rider view own request | 5 | HIGH | COMPLETE | P1 |
| US 01.03.01 | Rider will receive notification of their request being accepted by a driver | 7 | HIGH | PROGRESS | P1 |
| US 01.04.01 | Rider can cancel their request | 5 | HIGH | COMPLETE | P1 |
| US 01.05.01 | Rider can contact driver who accepted their request by either phone or email | 5 | MEDIUM | COMPLETE | P2 |
| US 01.06.01 | Rider can get price estimate | 3 | MEDIUM | COMPLETE | P1 |
| US 01.06.01 | Rider can add tip if desired | 3 | MEDIUM | PROGRESS | P1 |
| US 01.07.01 | Rider can confirm the completion of request | 10 | HIGH | PROGRESS | P2 |
| US 01.07.01 | Rider can pay | 10 | HIGH | ||
| US 01.08.01 | Rider can cancel ride before pickup | 5 | HIGH | COMPLETE | 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, whether if it was accepted or pending or completed | 6 | HIGH | COMPLETE | P1 |
User Profile
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 03.01.01 | User have profile with unique-username | 5 | HIGH | COMPLETE | P2 |
| US 03.01.01 | User have profile with contact info | 5 | HIGH | COMPLETE | P2 |
| US 03.02.01 | User can edit their contact info | 5 | MEDIUM | COMPLETE | P2 |
| US 03.03.01 | User can retrieve contact info of anything whom they've interacted with before, such as their past driver | 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 from closest to farthest | 5 | HIGH |
Accepting
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 05.01.01 | Driver can accept request | 4 | HIGH | ||
| US 05.01.01 | Driver can accept payment upon completion of the ride | 4 | HIGH | ||
| US 05.02.01 | Driver can view the last request that he accepted | 3 | HIGH | ||
| US 05.03.01 | Driver can see if their offer was accepted by the server | 4 | HIGH |
Offline behavior
| User Story ID | Description | Story Point | Risk Level | Status | Assignment |
|---|---|---|---|---|---|
| US 06.01.01 | Driver can see ride history offline | 1 | 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 | 4 | 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 |
CMPUT301W20T17