You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket focuses on gathering requirements and defining user stories for the minimum viable product (MVP) aimed at regional staff users. The MVP will deliver key features based on insights into regional submission statuses, submission completeness, and actionable items for regional staff to take. This ticket will involve collaboration with OFA to prioritize features that should be included in the MVP.
Additionally, we aim to ensure that the MVP is designed with regional staff workflows in mind, considering the permission changes and sensitive data updates delivered in #3249. The requirements and user stories defined here will serve as the foundation for the design concepts that will be explored in the next ticket.
Tasks
Hold a requirements gathering session with key stakeholders (including OFA, product team, and regional staff representatives) to determine the core features needed in the MVP.
Develop user stories that reflect how regional staff will interact with the MVP, including actions related to submission status tracking, identifying missing submissions, and addressing issues.
Create an initial set of user personas to understand the needs of regional staff and their workflows.
Organize a prioritization workshop with OFA to evaluate and rank the features based on their importance for the MVP.
Draft an MVP feature list with associated user stories and acceptance criteria for each feature.
Document the outcomes of the prioritization exercise and any decisions on which features should be included in the MVP.
Acceptance Criteria
A set of user stories for regional staff interaction with the MVP has been defined.
The MVP feature list has been created, prioritized, and aligned with stakeholders.
Documentation has been updated to reflect the finalized MVP features and user stories.
The prioritization workshop with OFA has been conducted, with clear outcomes on MVP scope.
All features deemed critical for the MVP are included, and the user stories align with regional staff needs.
Background
This ticket focuses on gathering requirements and defining user stories for the minimum viable product (MVP) aimed at regional staff users. The MVP will deliver key features based on insights into regional submission statuses, submission completeness, and actionable items for regional staff to take. This ticket will involve collaboration with OFA to prioritize features that should be included in the MVP.
Additionally, we aim to ensure that the MVP is designed with regional staff workflows in mind, considering the permission changes and sensitive data updates delivered in #3249. The requirements and user stories defined here will serve as the foundation for the design concepts that will be explored in the next ticket.
Tasks
Acceptance Criteria
Supporting Documentation
Gitbook: Requirements and Prioritization: Contains questions for requirements gathering session and feature list with personas
The text was updated successfully, but these errors were encountered: