Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

This page captures key decisions made in the course of development.

Decision

Date

Parties

Rationale

Options Considered

Project Operations

Team name:
ER Avengers (ERA)

Nov 27, 2023

Scrum team - decision makers

Democratic voting

Talent Cloud, ROSTER, Disaster Relief Champions, Emergency Response Task Force

Product name:

PENDING

Scrum team - decision makers

Documentation storage:
Teams SharePoint, Confluence, GitHub (ReadMe), Mural

December 1, 2023

Scrum team - decision makers

GitHub Wiki

Version management is done via …

PENDING

Scrum team - decision makers

Vanity URL

PENDING

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.

Sanity

Infrastructure and Tooling

Open Shift

December 1, 2023

Scrum team - decision makers

Cost effective

AWS

RDS: Postgres

December 1, 2023

Scrum team - decision makers

Team knowledge and comfort, familiarity with data structure

KeyCloak

PENDING

User Experience

Reduce the manual work load for regional 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 Regional/TEAMS coordinators.

  1. Understand program requirements/process

  2. Communication/Notifications

  3. Rebuild the intake form

  4. Multiple user access with different dashboard views

Key Features

Log in page

December 5, 2023

Scrum team - decision makers

For MVP, we are focusing on authorizing Regional Resource 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 resource coordinator, I want to be navigated to the dashboard screen after logging in, so that I can view the existing TEAMS members.

Filter & sort features

December 5, 2023

Scrum team - decision makers

As a resource coordinator, I want to be able to filter and sort 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 resource 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 resource coordinator, I want to edit a TEAMS user’s info so I can update their availability and interests.

Multi-field edit

Deployment Strategy and Timelines

MVP - deploy to production on January 18, 2023

December 5, 2023

Product Owner - Dea De Jarisco

  • No labels