Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

DO Q1 FY2025 OKR Alignment:

  • DO Q1 FY2025 OKR 6: INCREASE UPTAKE BY 20%

NEW:

  1. Communication and Process for Support Requests and Change Management

    1. Architectural Forum participation rates increasing

    2. (TACTIC) Weeknotes or Blogging of things that others would care about.

      1. Audience 1: Partner Teams and CHEFS users

        1. e.g. 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

      3. Clarifying alignment to the technology strategies of each Ministry

  2. Decoupling of Components for improving resilience of CHEFS system integrations

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

  4. Promote Digital Trust for public form submissions

    1. 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. 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.

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

  • No labels