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 Page History

« Previous Version 17 Next »

Objective 1

Objective: Create visibility of the stability and performance of CHEFS

Meaning (Key Result): Users see fewer errors and the service gets faster in all the core features.

Strategy: Track and report product usage statistics

Meaning: The ability for the team to know how many forms, users, and submissions are being created, and relate that to cost avoidance for product teams.

  • Metric: Number of forms published and used in production for low, medium and high complexity use cases

  • Metric: Number of users for each available access method

  • Metric: Number of submissions

Strategy: Track and report on bug resolution metrics

Meaning: reducing the time a bug exists will increase the amount of time users experience a bug free service.

  • Metric: Average time to resolution

  • Metric: Number of bugs outstanding

Strategy: Track and report on efforts to maintain and improve application uptime

Meaning: The app is always running and not being taken down for any reason, intentional or accidental.

  • Metric: running more than 99.95% of the time. This is achieved by having less than 22 minutes of downtime.

Strategy: Track and report on the efforts to run automated tests that validate that the system is functioning in an acceptable manner

Meaning: Before any new changes are made to the application, all the previously built features are tested to make sure they didn’t break.

  • Metric: Improve the test coverage by 5%. from 64% to 69%

  • Metric: Ensure that all test are passing before deploying a new release

  • Metric: Improve the maintainability score from a C to a B

Objective 2

Objective: Increase effectiveness of communications with users and partners whom we want to receive feedback and product enhancements from.

Meaning (Key Result): There is a clear and deliberate pathway for allowing partners to talk to our teams and collaborate with us on specific bugs or product enhancements.

Strategy: Publish “week notes” on our work with our partners

  • Metric: count of features implemented

  • Metric: count of success stories or testimonials collected

Strategy: Track and report on the documentation of features

  • Metric: percentage of features documented in tech docs or how-to videos from ?% to ?%

  • Metric: percentage of form components documented in context from 0% to 50%

Strategy: Sharing progress on Fider ideas

  • Metric: number of Fider ideas that has been built in.

Strategy: Listen to users through forums, interviews, and other feedback approaches

  • Metric: People giving feedback on our work

Objective 3

Objective: Increase the capacity for CHEFS to support greater numbers while keeping a sustainable pace for the team

Meaning (Key Result): The speed of change for the product aligns with the changing needs of users. This requires us have a baseline understanding of gaps in capabilities users want CHEFS to be able to do. This requires us to measure acceptance of existing features. New features are introduced to provide missing capabilities

Strategy: Improve the experience of finding and selecting CHEFS as a solution

  • Metric: usage analytics from the digital.gov.bc.ca common components pages people finding the CHEFS card and clicking through to the CHEFS

Strategy: Improve the experience of learning how to build forms (using the right components in the right way)

  • Metric: The average time to get a form published

  • Metric: The number of support requests to create and maintain forms

Strategy: Improve the experience of members of the common components community who desire to understand and contribute to the future architectural direction

  • Metric: Number of ongoing intiatives

  • Metric: Number of initiatives that other teams are collaborating on

  • No labels