DO Q4 OKR Alignment:
DO Q4 OKR 6:
Status colour Yellow title Increase Uptake By 20%
People ObjectivesStatus Strategy:colour Strategy:Purple Strategy:Product Objectives
Strategytitle Tactics:Get all contractors fully credentialed for their role (ie. IDIRs, other IDs on non-IDIR-authenticated systems) by no later than Friday 19 February 2024Hold 3-day in-person CHEFS Team Summit in Victoria the week of 29 January 2024 with full attendance by all CHEFS Government & Contractor team membersComplete any required Govt Employee Performance Development Platform activities/tasks that occur during the quarter
Objective: Sustainably & continuously improve the self-service product experience for CHEFS Form Designersrecurring
Strategy: Complete transition of product documentation from current wiki to DevEx BackStage platform.Status colour Green title completed Q4 Key Result: De-commission CHEFS GitHub Wiki documentation by Feb 29 2024
Loose ends:
Short cut from the App (Help) still goes to the github wiki.Status colour Green title completed
github wiki pages are labelled as historical with a pointer to the up to date content. Landing page explains the change. Table of Contents points to the new developer.gov.bc.caStatus colour Green title completed
Strategy: Develop a Conversational Form Design/Forms Wizard (aka FormsGPTStatus colour Yellow title loose ends Forms-GPT) experience
Q4 Key Result: 5 pilot users will create and publish forms using new wizard by March 30 2024
Loose ends:
get 5 users to do the scenario and get feedbackStatus colour Blue title in progress
Strategy: Continuous product improvement via Agile rituals, including NEXUS processes and bi-weekly sprint plans & reviews
Q4 Key Result: Develop a pilot-ready MVP of the following enhancements:
POC of Addition of authentication support for digital credentialStatus colour Green title completed
Enablement of SSO between CHEFS and applications within Standard Keycloak realmStatus colour Green title completed
Q4 Key Result: Achieve QoQ form publication growth of 10% (Average Number of Forms Published Monthly over the past year from 60 to 66)Status colour Green title completed
Objective: Sustainably & continuously improve the form submission product experience for CHEFS Form SubmittersStatus colour Purple title recurring Strategy:
New features:
Addition of authentication support for VC & Service Card identities
Transition to Standard Keycloak Realm
Automated Test Suite
Enhanced Logging
API Gateway Integration
Service Design, Documentation, End-User Support and Product UX Audit
Operational: Sustain/attain published availability SLA metrics
Process Objectives
Secure capital and operating funding for CHEFS via Treasury Board approval processes/artifacts.Hold 1/2-day on-line/in-person quarterly team retrospectiveRefactor team composition from 1 Team to 2 Teams and revise team ritual schedule as requiredContinuous product improvement via Agile rituals, including NEXUS processes and bi-weekly sprint plans & reviews
Q4 Key Result: Achieve QoQ new user growth of 10%Status colour Green title completed
Status | ||||
---|---|---|---|---|
|
Strategy: Implement Automated Test Suite
Q4 Key Result: Automated Testing Implemented for 20% (from x to y) of codebaseStatus colour Green title completed
Strategy: Reduce frequency and duration of client-impacting CHEFS incidents
Q4 Key Result: Establish baseline of time-to-resolution duration per incidentStatus colour Green title completed baseline was 77 days for patching vulnerabilities
Strategy: Enhance CHEFS Development API
Q4 Key Result: Documented plan for improved API security & scalabilityStatus colour Green title completed
Strategy: Enhanced Resilience of Critical CHEFS systems
Q4 Key Result: Complete a review of CHEFS DR Strategy & DR Best PracticesStatus colour Blue title in progress Did a proposed archictecture.
Expand | ||
---|---|---|
| ||
[Yesterday 1:42 PM] Hall, Matthew CITZ:EX Hi Olena, how are you doing? [Yesterday 1:43 PM] Hall, Matthew CITZ:EX I had a question about what our first steps should be for if want to move the CHEFS app from Silver to Gold and implement DR. [Yesterday 1:44 PM] Hall, Matthew CITZ:EX are there some people we should talk to about this? I'm thinking in terms of architecture refactoring decisions, such as should we be switching from petroni HA to CrunchyDB? I'm not quite sure on the scope of the task. [Yesterday 1:56 PM] Mitovska, Olena CITZ:EX Hi Matt, good to hear from you! I suggest that your team reviews the Guide for Gold teams first to understand some of the specifics of operating 2 instances of an app in Gold: https://digital.gov.bc.ca/cloud/services/private/internal-resources/gold/ If you want to get advice about the DB tech, please reach out to Cailey and she will be happy to help. Also, keep in mind that we split the provisioning of projects sets for Gold and Gold DR and now you have to submit 2 provisioning requests if you need a paired project set in both clustes. I suggest you provision a project set in Gold first and when you are ready to build the second instance in Gold DR, submit the second provisioning request. Any technical questions, the Platform Ops team is available in #devops-operations channel. Finally, you may want to talk to other teams that migrated to Gold. Ian Watts on our team moved Rocketchat to Gold last year, and API Gateway team moved their Kong instance to Gold last year too. heart 1 Sign in to Single Sign-On |