...
Decision | Date | Parties | Rationale | Options Considered | ||||||
Project Operations | ||||||||||
Team name: | Nov 27, 2023 | Scrum team - decision makers | Democratic voting | Talent Cloud, ROSTER, Disaster Relief Champions, Emergency Response Task Force | ||||||
Product name: |
| Scrum team - decision makers | ||||||||
Documentation storage: | December 1, 2023 | Scrum team - decision makers | GitHub Wiki | |||||||
Version management is done via … |
| Scrum team - decision makers | ||||||||
Vanity URL |
| Product Owner - Dea De Jarisco | ||||||||
Environments: dev, test, prod | December 5, 2023 | Scrum team - decision makers | Given the tight timelines, we only chose to go with 3 environments. Dev for developers to code and break, test for QAs, and prod. | Staging | ||||||
Infrastructure and Tooling | ||||||||||
Open Shift | December 5, 2023 | Scrum team - decision makers | Cost effective. We are okay going with OpenShift for MVP, where we’ll talk to the OpenShift team about failovers and backups in case the BC data centres are affected. There is an accepted risk that emergencies that affect the data centres the private cloud uses could affect the application. | AWS | ||||||
RDS: Postgres | December 1, 2023 | Scrum team - decision makers | Team knowledge and comfort, familiarity with data structure | |||||||
KeyCloak | December 1, 2023 | Scrum team - decision makers | We are using through the common single sign on (CSSO) - IDIR login | |||||||
User Experience | ||||||||||
Reduce the manual work load for TEAMS coordinators by improving the process of handling data and removing the need to use spreadsheets. | November 29, 2023 | Scrum team - decision makers | Considering the nature of an emergency teams system, where timely and accurate information is crucial, addressing the problem of reducing manual work for service coordinators is a higher priority concern. Coordinators struggle to organize and deploy applicants. They rely on a shared Excel sheet for availability, marking trainings and conducting email checks every 3 months. Spreadsheet difficulties force reliance on alternatives like physical boards, resulting in frequent redeployments instead of prioritizing new applicants. MVP: Focus user group will be TEAMS/TEAMS coordinators. |
| ||||||
Dashboard to use acronyms for ministry | Jan 3, 2024 | Scrum team - decision makers | As per the ticket criteria acronyms will be used for the ministry names in order to save space on the Dashboard for better user exp. | Full name of ministry vs acronym | ||||||
EMCR intake form | Jan 10, 2024 | Scrum team - decision makers | Unclear/unknown scope and risks on integration with BCWS. For MVP, we decided to take the least risky path and go with EMCR. The risk of integration for MVP is too high considering that BCWS is using a legendary system for high emergency risk situations. We are building with flexibility for future scope of integration with BCWS. | BCWS | ||||||
Key Features | ||||||||||
Log in page | December 5, 2023 | Scrum team - decision makers | For MVP, we are focusing on authorizing TEAMS/Regional Coordinators to log in successfully using their IDIR credentials. | Multi-user log in - TEAMS Member, Logistics Assistant | ||||||
Data ingestion | December 5, 2023 | Scrum team - decision makers | As a developer, I want to ingest the master roster TEAMS data, so that I can migrate the data to our app and database. | |||||||
Dashboard - view | December 5, 2023 | Scrum team - decision makers | As a TEAMS/Regional coordinator, I want to be navigated to the dashboard screen after logging in, so that I can view the existing TEAMS members. | |||||||
Search & filter features | December 5, 2023 | Scrum team - decision makers | As a TEAMS/Regional coordinator, I want to be able to search and filter TEAMS members by various options so I can easily find members to deploy to the emergency response crisis. | |||||||
TEAMS user profile - view feature | December 5, 2023 | Scrum team - decision makers | As a TEAMS/Regional coordinator, I want to view a user’s profile so I can quickly find their information. | |||||||
TEAMS user profile - edit feature - limited to certain fields | December 5, 2023 | Scrum team - decision makers | As a TEAMS/Regional coordinator, I want to edit a TEAMS user’s info so I can update their availability. | Multi-field edit | ||||||
Region/Work location filters | January 12, 2023 | SME | The coordinator can only select values in the region OR work location filter at a given time, and the other will be auto-populated with the corresponding values. For example, if a user selects HQ then only those work locations belonging to HQ will be auto populated in the work location drop-down and vice-versa. The user can clear the filters if they wish to select another option. | |||||||
Deployment Strategy and Timelines | ||||||||||
MVP - deploy to production on January 22, 2024 | December 5, 2023 | Product Owner - Dea De Jarisco | We need to be prepared for Freshet which is anticipated to happen as early as February 2024; hence, having the platform ready to for TEAMS/Regional Coordinators to use; so that, they can get ready to onboard potential new TEAMS member and deploy current TEAMS member. | |||||||
MVP - deploy to production by mid-March 2024 | December 11, 2023 | PO - Dea De Jarisco | Considering the risks and potential scope expansion within the challenging 6-week timeframe, the Product Owner (PO) engaged in discussions with the executives. Freshet has been officially removed from our roadmap. Our primary focus will now shift to March. | |||||||
...