10 Great Examples of DevOps OKRs

Category: DevOps OKR.

DevOps is a combination of “development” and “operations” which incorporates both agile practices and tools to increase an organization’s ability to deliver applications and services faster than traditional software development processes to be more responsive to the ever-changing consumer needs.

DevOps strives to streamline an organization’s technical execution ability to develop and improve software features, quickly and efficiently. Devops paves the way for the digital transformation of industries. Devops drives business outcomes as it transforms the way business delivers software with a constant emphasis on delivering user value.

The overall pace of software development has increased with DevOps and teams are now automating integration and testing, and deploying software in the cloud with quick timelines and continuous delivery. With DevOps, there’s more to monitor now, from integration, provisioning, to deployment, and so teams can align DevOps monitoring strategies to OKRs to effectively monitor different aspects of the project.

OKRs, or Objectives and Key Results, is a goal-setting framework that can help highlight priority items in your department and organization and offer focus and alignment for teams and companies. OKRs implemented to track the success of Devops initiatives, communicates the objectives in a consequential way to your organization.

Using OKRs to help drive progress in your DevOps department can make a huge impact in focus and productivity.

In this article, we’ll take a look at some of the examples of OKRs for DevOps that capture the priorities of the department as well as the key KPIs and metrics that should be kept in mind when creating quarterly targets and outlining initiatives. Read these examples, and use them as a launch point to identify your own business’s priorities and create OKRs to drive progress in your DevOps department.

#1: Product Development

Produce clean, efficient code based on specifications, with efficient API calls with less response time and unit test covered in all the code structures

Objective

David Griffin

Improve API response time and unit test coverage

26%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Decrease API response time from 700 ms to 400 ms

Annual-2021 Response time
700 400 646

18%

Increase unit test coverage from 80% to 100%

Annual-2021 Unit test coverage
80% 100% 86%

30%

Increase the testable code coverage from 75% to 95%

Annual-2021 Testable code coverage
75% 95% 81%

30%

#2: Continuous testing

Preventing defect leakage thereby identifying bugs early in the testing phase improves the quality of the testing process to improve quality and so on.

Objective

David Griffin

Improve testing process to reduce defect leakage

16%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Increase functional test coverage from 85% to 99% per project

Annual-2021 Functional test coverage
85% 99% 87%

14%

Increase automated testing scripts from 65% to 90% post release

Annual-2021 Automated testing scripts
65% 90% 69%

16%

Decrease average mean time to identify a defect early in the testing phase from 60 mins to 30 mins

Annual-2021 Mean Time to Identify defects
60 min(s) 30 min(s) 55%

17%

#3: Release management

Improve the release management process, by decreasing downtime of a release cycle, reduce the number of incidents caused after a release and reduce the manual steps involved in deployment.

Objective

David Griffin

Improve release management process

27%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Decrease the downtime during each release cycle from 30 mins to 5 mins

Annual-2021 Downtime during release cycle
30 min(s) 5 min(s) 27 min(s)

12%

Reduce the number of incidents caused by a release from 2 to 0 per release

Annual-2021 Number of incidents caused by a release
2 0 1

50%

Decrease the number of manual steps for deployment from 10 to 5 as a step towards automation

Annual-2021 Number of manual steps
10 5 9

20%

#4: Release Management

Release Management aims to ensure that the integrity of the live environment is protected and that the correct components are released as per the schedule.

Objective

David Griffin

Increase the number of releases to production environment

28%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Decrease outages caused by a release from 10% to 2% this quarter

Annual-2021 Outages caused by a release
10% 2% 7%

38%

Increase the successful changes in a release from 80% to 99%

Annual-2021 Successful changes in a release
80% 99% 84%

21%

Decrease the Mean time to detect failure from 3 hours to 30 mins

Annual-2021 Meant time to detect failure
3 hour(s) 30 min(s) 140 min(s)

27%

#5: Release Management

Plan for OKRs that would strengthen the release management process by increasing the number of isolated releases, decrease the number of emergency patches and number of rollbacks during the progress.

Objective

David Griffin

Strengthen the release management process

36%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Increase number of isolated releases from 2 to 4 per quarter

Annual-2021 Number of isolated releases
2 4 3

50%

Decrease number of emergency patches from 6 to 2 per quarter

Annual-2021 Number of emergency patches
6 2 5

25%

Decrease number of rollbacks from 3 to 0 per quarter

Annual-2021 Number of rollbacks
3 0 2

33%

#6: DevOps Monitoring

Monitor server’s health by analyzing the performance and uptime with respect to the available resources. Make sure that it is properly configured and scanning features are working as intended such as for identifying vulnerabilities in the application.

Objective

David Griffin

Implement monitoring for server health

41%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Reduce daily application exception errors from 50 to 10 by setting up alerts for HTTP server error

Annual-2021 HTTP server error rate
50 10 41%

23%

Optimize page load by setting up DataIn metric to restrict the payload request upto 20kb

Annual-2021 DataIn Metric
10 20 13

2%

Log all (100%) API service details when the Average Response Time from the service exceeds 800ms

Annual-2021 Average Response Time
400 1200 774

50%

#7: Change Management

Change Management Processes include a sequence of steps or activities that move a change from inception to delivery. Change Management Plans are developed to support a project to deliver a change.

Objective

David Griffin

Strengthen the change management process

42%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Increase overall change success rate from 75% to 95%

Q1-2021 Change success rate
75% 95% 80%

25%

Decrease number of failed changes from 3 to 1 per quarter

Q1-2021 Number of failed changes
3 1 2

50%

Decrease number of unauthorized changes from 2 to 0

Q1-2021 Number of unauthorized changes
2 0 1

50%

#8: Configuration Management

Configuration management is an IT management process that tracks individual configuration items of an IT system.

Objective

David Griffin

Increase efficiency with a defined configuration process that provides control and improves visibility with tracking

36%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Increase the number of CMS audits per quarter from 3 to 6 to identify the configuration errors

Annual-2021 Number of audits
3 6 4

33%

Decrease the number of configuration errors from 7 to 3

Annual-2021 Number of configuration errors
7 3 6

25%

Increase the frequency of physical verifications of CMS contents from 1 to 3 per quarter

Q1-2021 Frequency of physical verifications of CMS contents
1 3 2

50%

#9: Deployment

Build OKRs that improve deployment processes with supportive key results that would reduce market time, lead time and increase automated testing scripts.

Objective

David Griffin

Improve deployment process

50%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Decrease the deployment speed from 30 mins to 10 mins

Q1-2021 Deployment speed
30 min(s) 10 min(s) 26 min(s)

20%

Increase the capacity of pipeline to handle simultaneous deployments from 10 to 20

Q1-2021 Change Volume
10 20 13

30%

Reduce the time to market for each release from 3 weeks to 1 week

Q1-2021 Time to market
3 week(s) 1 week 2 week(s)

50%

Decrease the lead time between fixes from 2 weeks to 1 week

Q1-2021 Lead time
2 week(s) 1 week 1.5 week(s)

50%

#10: Deployment

Focus on improving the recovery and reducing the failure rate during deployment of the projects will improve the on time delivery release by decreasing the time taken between product launches and the unscheduled downtime.

Objective

David Griffin

Improve recovery and failure rate

30%

Target Date: Annual-2021

Visibility: All Employees

key-iconKey Results

Increase the Mean Time to Failure from 2 months to 6 months

Q1-2021 Mean Time to Failure (MTTF)
2 month(s) 6 month(s) 3 month(s)

25%

Decrease failed deployment rate from 30% to 15% per release

Annual-2021 Failed deployment rate
30% 15% 26%

27%

Decrease the Mean Time to Repair from 3 hours to 1 hour

Q1-2021 Mean Time to Repair (MTTR)
3 hour(s) 1 hour 2 hour(s)

50%

Decrease code freeze to delivery time from 8 hours to 2 hours

Q1-2021 Code freeze to delivery
8 hour(s) 2 hour(s) 7 hour(s)

17%

Conclusion

While your own business’ and department’s OKRs might look a little different depending on your priorities and initiatives, these Objective and Key Results serve as a good starting point to get you thinking about the goals you have for the upcoming quarter.

When tracking key DevOps metrics, a result that seems progressing well on its own could look completely different when aligned and tracked alongside with OKRs. Careful tracking of these devops OKRs can ensure not only greater efficiency in development and production, but more importantly, its alignment to the company’s objectives, thereby leading to delighted end-user experience. Embrace DevOps OKRs, and you could see vast improvements in application deployment and feedback.

Take a look at other departments’ priorities, as well as the corporate-level goals. What role does DevOps need to play to help these goals succeed?

For more information on how to write great OKRs, and more examples in other departments, don’t forget to check out our blog!

 

 

Related Articles