Page Comparison

...

1. Team Objective: Partners support the CHEFS' roadmap and understand how it aligns with theirs.
   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)

      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.

      1. Strategy: after establishing demand, we find out why, to present a message that will matter to partners, and why we are doing it now.

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

      3. 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 this relates to our roadmap (for executive)

2. Team Objective: Partners support our 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 integrationsStrategy

         1. Tactic: POC Tenant strategy (decoupling user management from CHEFS)

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

   2. Key Result: Measure some value out of the POCs

      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.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.can manage users and roles outside of CHEFS,

      2. Strategy: CHEFS would trust a token that is not a CHEFS aud variable in the JWT

      3. Strategy: can distribute data on a tenant basis through the message queue, only the tenant can read the data. (tenant = the registered app, which displays to the users)

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

   1. Key Result: 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. Key Result: Increased adoption and use of CHEFS API & Custom Components

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

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

      1. Strategy: Enhanced API capabilities

Future:

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.

Sprint Pages