-
Notifications
You must be signed in to change notification settings - Fork 0
Product Backlog
Justin Monteza edited this page Apr 9, 2021
·
31 revisions
- Low: Nice to have features
- Medium: App quality improvement but not critical
- High: Key feature of the app; must be done right
- Story points have been estimated depending on three factors: work complexity, amount of work, and uncertainty
- Work complexity accounts for how many features in the app are affected, or have to be taken into account when implementing the user story
- Amount of work accounts for the time taken to implement a user story
- Uncertainty accounts for how to clear is it to develop the features required to implement a user story
- The story points range from 1 to 5
- 1: low work complexity; a low amount of work; very little (or no) uncertainty
- 2: low work complexity; a medium amount of work; very little (or no) uncertainty
- 3: medium work complexity; a medium amount of work; slight uncertainty
- 4: high work complexity; a high amount of work; a medium level of uncertainty
- 5: high work complexity; a high amount of work; high uncertainty
| US 01.01.01 | ID: 001 |
|---|---|
| Requirement: | As an owner, I want to publish an experiment with a description, a region, and a minimum number of trials. |
| Rationale: | So that other users could replicate and review my experiment. |
| Risk level: | High |
| Story Points: | 5 |
| Status: | Complete |
| US 01.02.01 | ID: 002 |
|---|---|
| Requirement: | As an owner, I want to unpublish an experiment. |
| Rationale: | Because the experiment is outdated or the experiment methodology is unsatisfactory. |
| Risk level: | Medium (Uncommon but somewhat important) |
| Story Points: | 1 |
| Status: | Complete |
| US 01.03.01 | ID: 003 |
|---|---|
| Requirement: | As an owner, I want to end an experiment. This leaves the results available and public but does not allow new results to be added. |
| Rationale: | Because enough data has been collected or the data limit has been reached. |
| Risk level: | High (too much data might break the app) |
| Story Points: | 1 |
| Status: | Complete |
| US 01.04.01 | ID: 004 |
|---|---|
| Requirement: | As an owner or experimenter, I want to subscribe to an experiment to participate in it |
| Rationale: | Because I found it interesting and I’d like to see the results. I’d also like to replicate this experiment if possible. |
| Risk level: | High |
| Story Points: | 2 |
| Status: | Complete |
| US 01.05.01 | ID: 005 |
|---|---|
| Requirement: | As an experimenter, I want to be able to execute trials for an experiment and upload them to the experiment. |
| Rationale: | Because I subscribed to the experiment and I can conduct the experiment. |
| Risk level: | High |
| Story Points: | 5 |
| Status: | Complete |
| US 01.06.01 | ID: 006 |
|---|---|
| Requirement: | As an owner or experimenter, I want to see histograms of the results of trials. |
| Rationale: | So that I can quickly and easily visualize the experiment result. |
| Risk level: | Medium (This is a pretty good way to visualize the result) |
| Story Points: | 3 |
| Status: | Complete |
| US 01.07.01 | ID: 007 |
|---|---|
| Requirement: | As an owner or experimenter, I want to see plots of the results of trials over time. |
| Rationale: | So that I can see the progress of the experiment and how the result evolves over time. |
| Risk level: | Low (Not very useful but nice to have) |
| Story Points: | 4 |
| Status: | Complete |
| US 01.08.01 | ID: 008 |
|---|---|
| Requirement: | As an owner, I want to ignore certain experimenters' results. |
| Rationale: | It is to prevent trolls, bots, and spammers from contaminating the experiment. |
| Risk level: | Medium (Having a way to moderate experimenters is significant) |
| Story Points: | 1 |
| Status: | Complete |
| US 01.09.01 | ID: 009 |
|---|---|
| Requirement: | As an owner or experimenter, I want to observe statistics (quartiles, median, mean, stdev) about current trials. |
| Rationale: | So that I can draw a statistical conclusion from my experiment. |
| Risk level: | Low (Probably not a lot of people know what those statistics mean. Nice to have for people who knows) |
| Story Points: | 2 |
| Status: | Complete |
| US 02.01.01 | ID: 010 |
|---|---|
| Requirement: | As an experimenter, I want to ask a question about an experiment |
| Rationale: | So that I could ask for more clarification or details. |
| Risk level: | Medium (Fairly important to have a way to communicate but have workarounds) |
| Story Points: | 4 |
| Status: | Complete |
| US 02.02.01 | ID: 011 |
|---|---|
| Requirement: | As an experimenter or owner, I want to ask to reply to questions about an experiment. |
| Rationale: | It is so that I can answer those questions raised by the participants. |
| Risk level: | Medium (Required if decided to implement 02.01.01) |
| Story Points: | 3 |
| Status: | Complete |
| US 02.03.01 | ID: 012 |
|---|---|
| Requirement: | As an experimenter or owner, I want to browse questions and replies about an experiment. |
| Rationale: | It is so that I do not need to ask duplicate questions and to potentially help with other’s questions. |
| Risk level: | Medium (Required if decided to implement 02.01.01) |
| Story Points: | 2 |
| Status: | Complete |
| US 03.01.01 | ID: 013 |
|---|---|
| Requirement: | As an experimenter, I want to be able to generate QR codes that I can print for a specific experiment and trial result (for instance PASS for a binomial trial I subscribed to). |
| Rationale: | So that I can quickly switch to the experiment and record the result without manually opening the app. |
| Risk level: | Low (Not a critical feature, given that the user can already do that via the app) |
| Story Points: | 3 |
| Status: | Complete |
| US 03.02.01 | ID: 014 |
|---|---|
| Requirement: | As an experimenter, I want to be able to scan QR codes to indicate success or failure, or increment counts for trials I subscribed to. |
| Rationale: | Because it is often easier to scan QR code than manually opening the app. |
| Risk level: | Low (Not a critical feature, given that the user can already do that via the app) |
| Story Points: | 5 |
| Status: | Complete |
| US 03.03.01 | ID: 015 |
|---|---|
| Requirement: | As an experimenter, I want to be able to register an arbitrary bar code (such as one of your favorite book) to act on a specific experiment result for a trial. |
| Rationale: | So that I do not need to generate and print my own barcode. |
| Risk level: | Low (Nice to have if decided to implement US 03.01.01) |
| Story Points: | 5 |
| Status: | Complete |
| US 04.01.01 | ID: 016 |
|---|---|
| Requirement: | As an owner or experimenter, I want a profile with a unique username and my contact information. |
| Rationale: | Having my contact information would make me reachable by other contributors where we can discuss our results. |
| Risk level: | High |
| Story Points: | 4 |
| Status: | Complete |
| US 04.02.01 | ID: 017 |
|---|---|
| Requirement: | As an owner or experimenter, I want to edit the contact information in my profile. |
| Rationale: | My information is out of date and needs to be updated. |
| Risk level: | Medium |
| Story Points: | 1 |
| Status: | Complete |
| US 04.03.01 | ID: 018 |
|---|---|
| Requirement: | As an owner or experimenter, I want to retrieve and show the profile of a presented username |
| Rationale: | This will allow me to get in touch with other contributors and ask them how they were able to achieve their results. |
| Risk level: | Medium (It makes sense to read the contact info of other participants.) |
| Story Points: | 3 |
| Status: | Complete |
| US 04.04.01 | ID: 025 |
|---|---|
| Requirement: | As an owner or experimenter, I do not want to log into my application using a username and password. |
| Rationale: | This will make it easier for users to participate in an experiment. |
| Risk level: | High |
| Story Points: | 5 |
| Status: | Complete |
| US 05.01.01 | ID: 019 |
|---|---|
| Requirement: | As an experimenter, I want to specify a keyword, and search for all experiments that are available. |
| Rationale: | So that I can find the experiments I’m interested in more efficiently. |
| Risk level: | High (can’t subscribe to an experiment if you can’t find one) |
| Story Points: | 3 |
| Status: | Complete |
| US 05.02.01 | ID: 020 |
|---|---|
| Requirement: | As an experimenter, I want search results to show each experiment with its description, owner username, and status. |
| Rationale: | So that I don’t need to click into the experiment every time I want to check its details. |
| Risk level: | Medium (It will be nice to know the details of an experiment at a glance) |
| Story Points: | 2 |
| Status: | Complete |
| US 06.01.01 | ID: 021 |
|---|---|
| Requirement: | As an owner, I want to specify if a Geo-location is required or not for trials. |
| Rationale: | Some experiments I create are location-dependent, and knowing where an experimenter carried out the trials is important in understanding the results. |
| Risk level: | Medium |
| Story Points: | 1 |
| Status: | Complete |
| US 06.02.01 | ID: 022 |
|---|---|
| Requirement: | As an experimenter, I want to add Geo-location to experimental trials that need it. |
| Rationale: | This will help other contributors gain a better understanding of how I achieved my results. |
| Risk level: | Medium |
| Story Points: | 4 |
| Status: | Complete |
| US 06.03.01 | ID: 023 |
|---|---|
| Requirement: | As an experimenter, I want to be warned about geo-location trials. |
| Rationale: | I would not like to share my location at all times, and I should be aware if a trial requires me to do so. |
| Risk level: | Medium |
| Story Points: | 1 |
| Status: | Complete |
| US 06.04.01 | ID: 024 |
|---|---|
| Requirement: | As an experimenter, I want to see a map of geo-locations of a geo-location enabled experiment. |
| Rationale: | By doing so, I will be able to easily mark where I carried out my experiment, and also see all the locations where trials have been conducted for other experimenters. |
| Risk level: | Low |
| Story Points: | 5 |
| Status: | Complete |
TOOLS
MEETING NOTES
DELIVERABLES