Page Comparison

DO Q1 FY2025 OKR Alignment:

...

1. Team Objective: Increase clarity of CHEFS Product Roadmap so that there is certainty for CHEFS Partner teams that CHEFS is aligned with and supportive of their product/project vision & roadmap.

   1. Key Result: Increase the frequency of communication of our change management processes, handling of Support Requests, and planning activities. (To do, doing, and done - at a higher level specific to the product roadmap)

      Measurement:

      1. Strategy: Regular communications of product roadmap updates to Partner Teams & CHEFS users via a deck presented/distributed at key meetings throughout the quarter.

      2. Strategy: Executive updates (1 per quarter per executive audience) conducted by CPO & PO.

   2. Key Result: Architectural Forum participation rates increasing

      Measurement:

      .

      1. Strategy: Grant early access to new CHEFS features to “CHEFS Insiders”.

      2. Strategy: Conduct award ceremony during Forum to recognize a leading partner for their contributions & impact on CHEFS users throughout the quarter. (CHEFS User Impact Awards - “CHUI Awards”).

   3. Key Result: Receive positive feedback from clients that they feel improvements in communications (before and after)

      1. Strategy: Weeknotes of things that others would care about.

         1. Audience 1: Partner Teams and CHEFS users

            1. (Tactic) Deliverable: (example) We have an updated instruction page for the new CHEFS Role that was added (Submission Reviewer, Read-only reviewer role “Submission Approver”, Write permission reviewer role “Submission Reviewer“)

         2. Audience 2: Executive levels that endorse the use of CHEFS for their Ministries

            1. (Tactic) Deliverable: Executive Level messaging, clarifying alignment to the technology strategies of each Ministry

      2. Strategy: Blogging about form design principles

         1. links to how to documents for users of CHEFS (for designers)

         2. links to how is relates to our roadmap (for executive)

2. Team Objective: Achieve consensus on and partner support for a defensible technology architecture direction

   1. Key Result: Ratify a committed roadmap & project plan (including sequencing & dependencies) for critical CHEFS technology architecture components.

      1. Strategy: Decoupling of Components for improving resilience of CHEFS system integrations

      2. Strategy: POC on the message queue / event streaming to replace the hard coding webhook integration chefs is currently doing

   Promote Digital Trust for public form submissions

   1. 1. Strategy: something with the Person Credential, e.g. enable login with a simple zero knowledge proof request of “do you have a person credential?” That tells us it is a real person, who is from BC.

      2. Strategy: POC issuing a CHEFS “remember me for next time credential” to allow “person credential holders” to have the same experience as an authenticated BCeID user.

3. Team Objective: Simplify the user journey for low-complexity form design & management

   1. KR: Collect new user & low-complexity form maintainer effort & satisfaction metrics.

      1. Strategy: Controlled experiment - new users are asked to translate a specific PDF file into a CHEFS form:

         1. with FormsGPT

         2. without FormsGPT

         3. with CHEFS HelpBot (ie. Retrieval Augmented Generation)

         4. without CHEFS HelpBot

      2. Strategy: Ask power users to provide feedback on efficacy of new features.

4. Team Objective: Enhanced high-complexity forms support

   1. KR: Increased adoption and use of CHEFS API & Custom Components

      1. Strategy: Add new custom components (eg. mapping, look for more in FIDER)

   2. KR: Increased take-up of CHEFS for data and reporting use-cases

      1. Strategy: Kick-ass API yo

PREVIOUS:

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

   1. Objective: 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 (DONE)

   2. Objective: Develop a Conversational Form Design/Forms Wizard (aka FormsGPT) experience

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

   3. Objective: 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. Addition of authentication support for digital credential POC (DONE)

         2. Enablement of SSO between CHEFS and applications within Standard Keycloak realm (DONE)

      2. Q4 Key Result: Achieve QoQ form publication growth of 10% (Average Number of Forms Published Monthly over the past year from 60 to 66) (DONE)

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

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

      1. Q4 Key Result: Achieve QoQ new user growth of 10% (DONE)

3. Strategy: Sustainably & continuously increase the reliability of CHEFS for all users
   (Let’s update DO.Better Prioritization - Agile board - Jira (atlassian.net) DO-208

   1. Objective: Implement Automated Test Suite

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

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

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

   3. Objective: Enhance CHEFS Development API

      1. Q4 Key Result: Documented plan for improved API security & scalability (DONE)

   4. Objective: Enhanced Resilience of Critical CHEFS systems

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