Product Roadmap, Sprint Goals and Planning

Setup and Onboarding

• Project/Code base set-up (PR Review)
• Role definitions
• Definition of Done
• Create Mock-ups Chevonne Li (Unlicensed)
• Retrieve screenshots and desired app state from SME
• Follow-up with SME to review flowcharts and refine requirements Qudsia.Khan
• Decision log Qudsia.Khan
• Flowcharts Qudsia.Khan
• Strategic planning Qudsia.Khan
• Risk assessment Qudsia.Khan Noel.Feliciano Chelsea Brown
• Glossary of Terms Qudsia.Khan
• Scope summary document Qudsia.Khan (PO Review)
• Data Import
• Create data model
• Set up Postgres database (local)

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

• Create Mock-ups Chevonne Li (Unlicensed)
• Conduct mock-up testing with SMEs Chevonne Li (Unlicensed) Qudsia.Khan
• Create test plans Qudsia.Khan
• Create user research questionnaire for intake form Qudsia.Khan
• Conduct user research interviews for intake form Qudsia.Khan
• MVP workflow for intake form Qudsia.Khan

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

• Collect and synthesize data from user interviews Chevonne Li (Unlicensed) Qudsia.Khan
• Create Affinity Mapping
• Create research plan for EMCR/BCWS to inform post-MVP build
• Create EMCR Intake Form Mock-ups Chevonne Li (Unlicensed)

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
• 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

PO/Project Tasks

• Vanity URL Katie Menke (waiting on product name decision)
• PIA/STRA Dea De Jarisco
• Product name
• Comms plan with PSA and EMCR

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)

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

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

Dashboard

• Initial look for BCWS Dashboard for approving new applicants

Applicant Approval

• EMCR - Complete pending applicant review feature

Integrated Intake Form

• Create the first draft of the integrated intake form

Service Design

• Research and analysis of the first draft of the integrated intake form with Emily (BCWS) & Caitlyn (EMCR).

Testing

• Set testing process and release process and cycles

Data Fields

• Gather & finalize data fields needed for BCWS to approve new applicants
• Verify fields of approving applicants against BCWS' rules for approval
• Data freeze - most fields are confirmed so that we can start making changes to our schema (April 24)

Dashboard

• Research the BCWS Dashboard for applicant approval
• Conduct usability testing of BCWS Dashboard with BCWS TEAMS Coordinators
• Finalize the design the BCWS Dashboard for applicant approval by May 1st Chevonne Li
• Decision on BCWS Data Migration - Current Members & Recommitted by May 1st (In scope for May 31st MVP)
• Decision on accessing CHIPS data in partnership w. PSA by May 1st (to resume work in June - POST MVP delivery)

Member Profile

• Design the BCWS member profile
• Conduct usability testing of BCWS TEAMS' members profile
• Finalize the design of the BCWS Member profile by May 1st Chevonne Li

Integrated Intake Form

• Create the first draft of the integrated form to test with BCWS Coordinators.
• Complete the final design of the integrated form by May 1st Chevonne Li so that, we can finalize it in CHEFS
• Create research plan for usability testing of the final integrated form with potential applicants + EMCR & BCWS Members by May 1st Umar Ansari
• Create research plan for the usability testing of the final integrated form with BCWS TEAMS Coordinators to be implemented POST-MVP by May 1st Umar Ansari

BCWS API Endpoint

• Create test API and send over to BCWS to ensure it’s working

Dashboard

• Dev work - front-end & back-end coding Noel.Feliciano Chelsea Brown
• TC-538 - Getting issue details... STATUS BCWS Data Migration - Current Members & Recommitted
• Finalize the data in the excel sheet Emily Robertson by May 13th.
• Import real data to database
• Access to dashboard data
• Wipe seed data from database

Member Profile

• Dev work - front-end & back-end coding Chelsea Brown Noel.Feliciano

MVP Integrated Intake Form

• TC-494 - Getting issue details... STATUS Create the final integrated intake form in CHEFS by May 16th Chelsea Brown and Noel.Feliciano

POST-MVP Integrated Intake Form (after May 31st implementation)

• TC-469 - Getting issue details... STATUS Conduct usability testing of the final integrated form (the one we’re going to release for the MVP) with potential applicants + EMCR & BCWS Members scheduled for May 8th to 10th Chevonne Li and Umar Ansari
• TC-505 - Getting issue details... STATUS Complete synthesis of the usability testing with potential applicants + EMCR & BCWS Members by May 12th - 13th Umar Ansari and Chevonne Li. From the learnings in this usability testing, a second draft will be created of the integrated intake form (preferably in CHEFS).
• TC-506 - Getting issue details... STATUS Create the second draft of the integrated intake form by May 13th to be tested with BCWS TEAMS Coordinators, as the “compromise” Chevonne Li (the changes we gather here will be implemented after May 31st).
• TC-507 - Getting issue details... STATUS Conduct usability testing (the “compromise) of the second draft of the integrated form with BCWS TEAMS Coordinators scheduled for May 14th and 15th Umar Ansari Chevonne Li (the changes we gather here will be implemented after May 31st).
• TC-540 - Getting issue details... STATUS Complete synthesis of the usability testing of the second draft of the integrated form with BCWS TEAMS Coordinators by the morning of May 21st Umar Ansari in preparation for meeting w. Dea on the same day.

POST-MVP Service/Program Design work (after May 31st implementation)

• TC-542 - Getting issue details... STATUS to start on the research plan for a broader engagement to inform Service/Program Design Umar Ansari

Dashboard

• Dev work - front-end & back-end coding. Code freeze by May 20th Noel.Feliciano Chelsea Brown

Member Profile

• Dev work - front-end & back-end coding. Code freeze by May 20th Chelsea Brown Noel.Feliciano

Testing & Bug Fixes (May 20th - 31st)

• Dev work - testing, bug fixes, and re-testing Chelsea Brown Noel.Feliciano

POST-MVP Integrated Intake Form (after May 31st implementation)

• Complete synthesis of the usability testing of the second draft of the integrated form with BCWS TEAMS Coordinators by the morning of May 21st Umar Ansari
• Create a final version of the integrated intake form by May 24th Chevonne Li so that, we can implement it in CHEFS after May 31st.

Dashboard: Recommitment for Member

• Enable members' ability to log-in

Service Design & Research

• Create research engagement or workshop plan to find out: Information we need to provide; so that, supervisors are more knowledgeable about the CORE program

Demo

• Prepare materials for demo to show our progress to our stakeholders

UX/UI Design

• Finish UX Designs for recommitment for the following user groups:
• Members
• Supervisors

QA Testing

• Set testing process and documentation

Dashboard: Recommitment for Member

• Build member profile to be accessed by CORE members

Service Design & Research

• Create a workshop board to find conduct the session on: Information we need to provide; so that, supervisors are more knowledgeable about the CORE program

UX/UI Design

• Finish UX Designs for recommitment for the following user group:
• Supervisors
• Pop-up sections for sections and roles when adding a new section/role preference(s)

QA Testing

• Remote and travel options

Dashboard: Recommitment for Supervisor

• Build employee dashboard to be accessed by Supervisors

Service Design & Research

• Send invites to Coordinators to conduct the workshop
• Conduct the sessions with Coordinators on creating an info package for supervisors about the CORE program

Demo

• Prepare materials for demo to show our progress to our stakeholders

UX/UI Design

• Finish UX Designs for recommitment for Coordinators
• Recommitment Banner User Interface

QA Testing

• Login Flows

These are the various combinations of roles/programs that a user logging in to our system might have.

• Coordinator/Logistics roles and their corresponding program will be set explicitly in Key Cloak.

• For members/supervisors, their roles (and program, for members) are implicitly set.

• A user will have a supervisor role if their IDIR has been included in any member’s data as the supervisor email.

• A user will have a member role is they have signed up for one or both programs

• Users can be created through submitting a form (or editing an existing users email address to match the email address you are logging in with)

• Supervisors can be created through submitting a form with their IDIR as the supervisor email (or editing an existing users supervisor email address to match the email address you are logging in with)

Notification Functionality

• Developed module functionality

Service Design & Research

• Synthesis of the workshop
• Provide results of the workshop to EMCR and BCWS to start thinking about the materials that need to be created to help supervisors understand the program better and their role in it

Content

• UX Designs for user guides
• Create instructional videos for what recommitment is for a member
• Create instructional videos for what recommitment is for a supervisor

Process Management & Operations

• Create onboarding plan and materials to introduce new features to Coordinators
• Schedule sessions for onboarding Coordinators about the new features

QA Testing

• Notification functionality

Dashboard: Recommitment for Member, Coordinators, and Supervisor

• Dev work - front-end & back-end coding.

Scheduler: Member edit capability

• Dev work - front-end & back-end coding.

Demo

• Prep, January 6th
• Presentation, January 8th

Testing & Bug Fixes (continuous)

• Dev work - testing, bug fixes, and re-testing
• Continue to do bug fixes as they come up after release

Dashboard: Recommitment for Member, Coordinators, and Supervisor

• Dev work - front-end & back-end coding. Code freeze by January 8th

Scheduler: Member edit capability

• Dev work - front-end & back-end coding. Code freeze by January 8th

Testing & Bug Fixes (continuous)

• Dev work - testing, bug fixes, and re-testing
• Continue to do bug fixes as they come up after release

Recommitment Initiation Feature

• Figure out flow and designs for re-initiating recommitment after the due date.

Team Planning - Next Delivery

• SPIKE: Estimates to moving away from CHEFS

Recommitment Re-Initiation for Member, Coordinators, and Supervisor

• Dev work - front-end & back-end coding.
• Email Templates
• Notifications
• Update user manuals

Scheduler: Member edit capability

• Estimate work for how to fix the scheduler to ensure that Coordinators know that members' availability have been recently updated

Testing & Bug Fixes (continuous)

• Dev work - testing, bug fixes, and re-testing
• Continue to do bug fixes as they come up after release

Intake Form

• Finalize Designs
• Dev work - front-end & back-end coding

CHIPS Data Integration

• Start working on the employee data first

Scheduler: Member edit capability

• Start working on the designs
• Start dev work

Testing & Bug Fixes (continuous)

• Dev work - testing, bug fixes, and re-testing
• Continue to do bug fixes as they come up after release