FY2024 Q4

DO Q4 OKR Alignment:

  • DO Q4 OKR 6: Increase Uptake By 20%

 

  1. recurring Objective: Sustainably & continuously improve the self-service product experience for CHEFS Form Designers

    1. completed Strategy: Complete transition of product documentation from current wiki to DevEx BackStage platform.

      1. Q4 Key Result: De-commission CHEFS GitHub Wiki documentation by Feb 29 2024

        1. Loose ends:

          1. completed Short cut from the App (Help) still goes to the github wiki.

          2. 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.ca

    2. loose ends Strategy: Develop a Conversational Form Design/Forms Wizard (aka Forms-GPT) experience

      1. Q4 Key Result: 5 pilot users will create and publish forms using new wizard by March 30 2024

        1. Loose ends:

          1. in progress get 5 users to do the scenario and get feedback

    3. Strategy: Continuous product improvement via Agile rituals, including NEXUS processes and bi-weekly sprint plans & reviews

      1. Q4 Key Result: Develop a pilot-ready MVP of the following enhancements:

        1. completed POC of Addition of authentication support for digital credential

        2. completed Enablement of SSO between CHEFS and applications within Standard Keycloak realm

      2. 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)

  2. recurring Objective: Sustainably & continuously improve the form submission product experience for CHEFS Form Submitters

    1. Strategy: Continuous product improvement via Agile rituals, including NEXUS processes and bi-weekly sprint plans & reviews

      1. completed Q4 Key Result: Achieve QoQ new user growth of 10%

  3. Done Once Objective: Sustainably & continuously increase the reliability of CHEFS for all users

    1. Strategy: Implement Automated Test Suite

      1. completed Q4 Key Result: Automated Testing Implemented for 20% (from x to y) of codebase

    2. Strategy: Reduce frequency and duration of client-impacting CHEFS incidents

      1. completed Q4 Key Result: Establish baseline of time-to-resolution duration per incident

        1. baseline was 77 days for patching vulnerabilities

    3. Strategy: Enhance CHEFS Development API

      1. completed Q4 Key Result: Documented plan for improved API security & scalability

    4. Strategy: Enhanced Resilience of Critical CHEFS systems

      1. in progress Q4 Key Result: Complete a review of CHEFS DR Strategy & DR Best Practices

        1. Did a proposed archictecture.

[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