Vaccine Product Requirements Template
Goals/Scope
- Include a statement describing what this functionality seeks to achieve and provides criteria guidance of how success would be measured or tested. What are we doing what we are going? What important background information is needed for the stories and may describe the pre-conditions or triggers?
Background
Are there any country specific features that should be noted? Who are the personas? Who are the users that will be interacting with this functionality? What are their challenges, responsibilities, and level of connectivity? These personas are intended to be representative archetypes of the key stakeholders who will participate in theses workflows/scenarios.
Assumptions
- What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this features from a tablet).
User Stories
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 | Short identifier for the story | Describe the user and what they are trying to achieve As a ______ I want/need to ________ so that I _______. - High level acceptance criteria | Relevant labels to distinguish source. From which system, or which country? | Must Have, Nice to Have | |
| 2 |
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.
Dependencies
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
| Description | Link |
|---|---|
| Name of story or release | Link to JIRA |
Open Questions
Initial communication between stakeholders and the development team to help understand scope and estimates.
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | (e.g. How we make users more aware of this feature?) | Communicate the decision reached | Open, In Progress, Closed, and date of closure |
Out of Scope
- 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.
OpenLMIS: the global initiative for powerful LMIS software