Objective: Improve stability and Performance - Meaning: Users see fewer errors and the service gets faster in all the core features.
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: Partners are supported and able to contribute towards to enhancements of the common components we support - Meaning: 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%
General
Content
Integrations