OKR

OKR = Objectives, Key Results & Initiatives

Objective(s)

Where do I need to go?

Objetives are statements that inspire and direction

= your big goals

Key Result(s)

How do i know I’m getting there?

Key results measure progress toward an objective

= outcomes to help you measure your success towards the goals

Initiative(s)

Where will I do do get there?

Taks that needs to be done in short-term as part of somebodys daily business

= steps necessary to achieve the key results

Objective #1: Improve the Release Quality

… should help the team to cope with bug deduction and product testing updates in beta + increasing code unit test coverage can help to correlate with the parameters of release updates

Target date: Q4/2025

Visibility: All employees

%

KR #1.1: Reduce the number of bugs

… getting reported after a new release from 20 to 5

KR type: Decrease KPI

KPI: # of Errors

  • 67% 67%

KR #1.2: Increase the average number

… of end users testing product updates in beta from 3 to 6

KR type: Increase KPI

KPI: # of Users

  • 67% 67%

KR #1.3: Increase code unit test coverage

… from 80 % to 90 %

KR type: Increase KPI

KPI: Unit Test Coverage

  • 70% 70%

Objective #2: Enhance Team Collaboration

… should help the team to work more efficient & effective with all team members

Target date: Q3/2025

Visibility: All employees

%

KR #2.1: Implement daily stand-up

… meetings to improve team communication and collaboration

KR type: Increase KPI

KPI: # of agile Scrum teams

  • 50% 50%

KR #2.2: Raise the number of code reviews

… done by members by 50 % within the next three months

KR type: Increase KPI

KPI: # of CRs

  • 60% 60%

KR #2.3: Conduct an event aimed

… at better teamwork and collaboration within the team

KR type: Increase KPI

KPI: # of Team events

  • 40% 40%

Objective #3: Improve our code quality standards

… OKRs to increase code quality

Target date: Q1/2026

Visibility: All employees

%

KR #3.1: All pull requests are reviewed by 2

… 100% of pull requests are reviewed by 2 developers

KR type: Increase KPI

KPI: # of pull requests

  • 45% 45%

”KR

… 75 % of the developers have gone through QA training

KR type: Increase KPI

KPI: # of DEVs

  • 38% 38%

KR #3.3: All repositories are using code

… 100 % of repositories are using code linting and static code analysis

KR type: Increase KPI

KPI: # of repositories

  • 40% 40%

KR #3.4: Reduce QA-related broken builds

… Reduce the percentage of QA-related broken builds by 60%

KR type: Decrease KPI

KPI: # of broken builds

  • 41% 41%