...
Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
# | Title | User Story | Label | Importance | Notes |
---|---|---|---|---|---|
1 | View load amounts for different variables | As a FC and/or intermediate warehouse manager, I want to view the load amounts for the scheduled delivery period so that I can pack the truck with the necessary amounts. I want to view the following:
| SELV, SIIL | Must Have | |
2 | View and manipulate load amounts (advanced) | As a FC, I want to view the total load amount, per product, for the area I am going to visit, and then have an input method that allows me enter my existing amount I have, so that I can then know the missing amount still needed to load up the truck with amount needed for distribution to that area. (NOTE – still open debate – is this under another domain wsuch as stock management?] | Very nice to have | ||
3 | View CCE status along with load amounts (existing RTM feature) | As a FC and/or intermediate warehouse manager, I want to know the CCE status of the facilities to which I am dropping off vaccines so that in the event of non-functional or erractic functioning of CCE, I can follow-up to see if I should even be planning to visit that facility. This way, I am not unnecessarily taking more vaccines than I need on my trip. | SELV | Must have where RTM available |
Diagrams
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
...
- List the features discussed which are out of scope or might be revisited in a later release.
- List the features discussed which are out of scope or might be revisited in a later release.