FY2024 Q4
DO Q4 OKR Alignment:
DO Q4 OKR 6: Increase Uptake By 20%
Â
recurring Objective: Sustainably & continuously improve the self-service product experience for CHEFS Form Designers
completed Strategy: Complete transition of product documentation from current wiki to DevEx BackStage platform.
Q4 Key Result: De-commission CHEFS GitHub Wiki documentation by Feb 29 2024
Loose ends:
completed Short cut from the App (Help) still goes to the github wiki.
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
loose ends Strategy: Develop a Conversational Form Design/Forms Wizard (aka Forms-GPT) experience
Q4 Key Result: 5 pilot users will create and publish forms using new wizard by March 30 2024
Loose ends:
in progress get 5 users to do the scenario and get feedback
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:
completed POC of Addition of authentication support for digital credential
completed Enablement of SSO between CHEFS and applications within Standard Keycloak realm
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)
recurring Objective: Sustainably & continuously improve the form submission product experience for CHEFS Form Submitters
Strategy: Continuous product improvement via Agile rituals, including NEXUS processes and bi-weekly sprint plans & reviews
completed Q4 Key Result: Achieve QoQ new user growth of 10%
Done Once Objective: Sustainably & continuously increase the reliability of CHEFS for all users
Strategy: Implement Automated Test Suite
completed Q4 Key Result: Automated Testing Implemented for 20% (from x to y) of codebase
Strategy: Reduce frequency and duration of client-impacting CHEFS incidents
completed Q4 Key Result: Establish baseline of time-to-resolution duration per incident
baseline was 77 days for patching vulnerabilities
Strategy: Enhance CHEFS Development API
completed Q4 Key Result: Documented plan for improved API security & scalability
Strategy: Enhanced Resilience of Critical CHEFS systems
in progress Q4 Key Result: Complete a review of CHEFS DR Strategy & DR Best Practices
Did a proposed archictecture.