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 71 Next »

\uD83D\uDCCB Overview

Deliver a Minimum Viable Product (MVP) of the emergency response software app by March 22, 2024 to assist BC government employees, particularly EMCR TEAMS coordinators, in finding and deploying EMCR TEAMS members' talent during emergencies and disasters. The ask is to also deliver an updated intake form for BC employees to apply to EMCR TEAMS for a seamless user experience.

❓ What is TEAMS?

TEAMS is the staffing system which maintains a resource pool of highly qualified employees from various ministries with appropriate skills to work in emergency operations centers.

When emergencies happen, TEAMS volunteers leave their BC Public Service base positions to work in a TEAMS role, with the benefit of not losing their position or pay. TEAMS members play an important role during the coordination of emergencies and disasters in British Columbia.

There are two TEAMS within government, one for EMCR and one for BCWS. The focus of this product is EMCR TEAMS.

\uD83C\uDFA2 Project strategy roadmap and planning

This strategic roadmap lists the Sprint goals and orders them by priority. This strategic plan details the action items and plans for each sprint. The development of the dashboard feature before user profile management, ensuring a logical flow that emphasizes core functionalities and user interactions. Regular sprint reviews and retrospectives will be essential for adapting to changing requirements and ensuring continuous improvement throughout the development process.

What do the colors mean?

Moved over to next sprint

In-progress/carried over to the next sprint

Sprint 1 Goals
Dec 1 - 14, 2023

Sprint 2 Goals
Dec 15 - 22, 2023

Sprint 3 Goals
Jan 4 - 17, 2024

Sprint 4 Goals
Jan 18 - Feb 7, 2024

1

Setup and Onboarding

Login Portal Backend - group it as one

  • Set up KeyCloak
  • Handle authentication/authorization
  • Implement backend validation for user authentication
  • Route the FE to the login page
  • Conduct basic testing for login functionality

DevOps

  • Get app into OpenShift

Mockups/Testing/Documentation

DEvOps

  • Create data model
  • Set up Postgres database (dev)
  • Environment setup (dev)
  • GitHub workflows for PRs
  • Automated testing suite for FE
  • Automated testing suite for BE
  • Implement backend validation for user authentication
  • Get into Openshift
  • Set up TEST env

Dashboard

  • Finalize iteration of dashboard mock-up (search/filter/table)
  • Integration between FE and BE

EMCR Intake Form

Service Design

  • Create MVP service blue print

User Profile Screen

  • Create user profile mock-ups
  • Finalize requirements/AC for filter section (function, work location)

Continue Build of Dashboard

  • Create seed data for testing
  • Complete filters

Build and Test User Profile Screen

  • Conduct thorough testing of the user details screen features
  • Implement user profile screen
  • Display profile section (question)
  • Test that data from dashboard matches profile data

Scheduler SPIKE

  • Work on the Spike ticket for scheduler
  • Design the of the scheduler

EMCR Intake Form

  • Collaborate with CHEFS on intake form build
  • Build RestAPI and endpoint tokens to pull in CHEFS EMCR Forms data
  • Conduct thorough testing of the EMCR intake form mock up with coordinators

Service Design

  • Create MVP service blue print
  • Test MVP service blue print with EMCR coordinators
  • Gather and summarize existing EMCR TEAMS communications (i.e. email templates) to identify improvements to processes

Conduct Testing

  • Conduct comprehensive testing, including unit tests, integration tests, and system tests
  • Address any discovered bugs or issues promptly

2

PO/Project Tasks

PO/Project Tasks

  • Vanity URL Katie Menke (moved to POST MVP)
  • PIA/STRA Dea De Jarisco (submitted)
  • Product name
  • Comms plan with PSA and EMCR (POST MVP)

Sprint 5 Goals
Feb 8 - Feb 21, 2024

Sprint 6 Goals
Feb 22 - March 6, 2024

Sprint 7 Goals
March 7 - March 20, 2024

MVP Release

March 22, 2024

1

Dashboard

  • Update availability on dashboard based on scheduler SPIKE
  • Complete filters
  • Add “new” member UI

User Profile:

  • UI Edit “new” member

Scheduler:

  • UI FE and BE of scheduler

EMCR Intake Form

  • Testing with TEAMS applicants

Service Design

  • Research and analysis of EMCR intake form

Testing

  • Conduct comprehensive testing, including unit tests, integration tests, and system tests
  • Address any discovered bugs or issues promptly

Dashboard

  • Import real data to database
  • Access to dashboard data
  • Wipe seed data from database
  • Add “new” member DEV

Log in:

  • Edit access only for two EMCR IDIRs (confirm IDIRs with Caitlyn)

User Profile:

  • Edit “new” member

Scheduler:

  • Build FE and BE of scheduler

EMCR Intake Form

  • RestAPI and token
  • Final build of EMCR Intake Form

Testing

  • Conduct comprehensive testing, including unit tests, integration tests, and system tests
  • Address any discovered bugs or issues promptly

User Profile:

  • Update fields based on final EMCR Intake Form
  • Wrap up features of User Profile

Code freeze March 12:

  • Wrap up existing feature work by EOD March 12
  • Bug fixes
  • Small UI tweaks

Service Design

  • Research and analysis of single intake form approach (BCWS and EMCR) to inform future state document
  • Draft single intake form (content and design)
  • Process mapping workshop with SHR, logistics, TEAMS coordinators and training.

EMCR Intranet:

  • Update job descriptions
  • Provide update instructions on EMCR TEAMS program

EMCR Onboarding:

  • Update User Manual based on process mapping workshop
  • Onboard EMCR to user manual and application

Celebrate release!

  • Deliver a virtual meeting with EMCR and the team to introduce the MVP link and celebrate!

Service Design:

  • Document post-MVP feature ideas based on research

Documentation:

  • Clean up Figma, Confluence, MS Teams, documentation and JIRA
2

PO/Project Tasks

  • Product name (done but can’t implement until after Post MVP)
  • Comms plan with PSA and EMCR (Post MVP)

PO/Project Tasks

  • Communicate upcoming release and training to EMCR coordinators
  • Identify training champions
  • Confirm post MVP funding and ownership (pending governance decisions)

PO/Project Tasks

  • Onboard coordinators to new EMCR dashboard and intake form
  • Prep for March 22 demo celebration with EMCR and Scrum Team
  • Prep for final MVP demo on March 20 🥳
  • Communicate MVP and post MVP to leadership

\uD83D\uDDE3 Project channels

Channel

Name

Link

Audience

MS TEAMS

ERA

ERA TEAMS Page

Scrum team

\uD83D\uDCDA Resources

  1. Glossary

  2. EMCR Intranet

  3. BCWS Intranet

  4. TEAMS

  5. TEAMS Trainings

  6. Annual Commitment Information

  7. Annual Commitment Form

  • No labels