Engineering OKRs template

OKRs example to improve engineering release cycles

Move fast, but don't break things

ObjectiveObj.
Significantly increase the speed of our development cycle
#
Reduce build times from 25 to under 5 mins
#
Reduce cycle time from 28 days to 6 days
Automate all deployment steps
Implement CD pipeline for the staging environment
#
Improve developer NPS from 20 to 60

About this Engineering OKRs example

This template can be tracked in Tability, a modern platform for OKRs.
Get started for free today →

You can go faster while maintaining a high quality of releases.

This OKRs focuses on improving the continuous delivery pipeline to get faster builds and simpler releases.

The less devs have to wait once they push their code, the easier it'll be for them to validate their implementation and move on to the next bit of work.

Move fast, but don't break things.

How to use these templates

You can find this template in Tability, a platform that helps teams get their goals out of spreadsheets.

Tability | Keep a pulse on your master plan

With Tability you can:

  • Get weekly check-ins reminders to track progress.
  • Monitor trends on your Key Results.
  • Connect outcomes to outputs by listing initiatives.
  • Get automated dashboards and reports.
  • See how your OKRs align at a glance.

Learn more at tability.io.

Creator
TabilitySten Pittet
Last updated
5 days ago
Copied
68 times