How to use OKRs
Kendis Team avatar
Written by Kendis Team
Updated over a week ago

OKRs stands for Objective and Key Results. At a Program Board level in Kendis, it is possible to create an Objective and link it to the features. OKRs are extensions to the Objectives; now you can define an Objective with one or more key results.

Terminology

Let's start by defining the new terminologies that you may see while creating, managing, and tracking your OKRs

Strategic Themes

OKRs main heading. Will be customizable in the future

Objective Group

Objectives (OKR) always belong to an Objective Group. It has a cumulative progress of all the Objectives in the group.

Objective

Define the goal, target, or what needs to be achieved

Key Result

Key Results benchmark and monitor how we get to the Objective. Effective KRs are specific, time-bound, and aggressive yet realistic.

Associations

An Objective may be associated with different collections

Link Backlog Item

Link a work item to the Objective

Create Objective Group

Before you create an Objective, you must create an Objective Group.

  • Click on the +Add link.

  • Provide the Title of the Objective Group, and it may represent a bigger goal, period, or cycle.

  • Save

You may reorder Objective Groups to set the right priority

Create Objectives and Key Results

To create an Objective, click the + icon and type your Objective. Once an objective is created, you may perform additional steps.

  • Link items to Objectives

  • Provide extra details, e.g.,

    • Description, responsible, start and end date

    • Objective Groups: An objective may belong to more than one

To access the modal window, click on the Objective ID number or from the menu option selection "View Details."

Linked Items

Linking items provides an automated way to track the progress. OKRs can link items from different collections, making setting goals and tracking progress flexible.

To link items, choose the "Link Item" menu option or open the Objective modal window and link items from there.

Select your collection and type your target search criteria to find the relevant items and link to the objective.

Create Key Results

A Key Result (KR) can be created under an Objective. You may choose the menu option to create a Key Result or open the Modal window and selct "Linked Items" section to create a Key Result.

To create a Key result, you need

  • Key Result Details

  • Type of Key Result

Key Result Details

A Key result has the following details.

  • Summary or Title: A short description of your Key Result.

  • Status

  • Start Date

  • End Date

  • Responsible

  • Description

Type of Key Results

Key Results benchmark and monitor how we get to the Objective. Effective KRs are specific, time-bound, and aggressive yet realistic.

There are three types of Key results; the default is "By Items."

Key Result Type

Description

By Items

Search and link items to a Key Result. The progress tracking will happen automatically based on the linked items' completion.

By Target

A way to track the progress of a subjective Key Result, e.g., Decrease the deployment cycle by 50%

Unit: %

Target: 50

Progress: This will be set manually by the user

By Objective

A Key result can be linked to another Objective, making it

possible to have "Cascading OKRs."

1) By Items

Select this option when you want to automatically track the progress of the key results based on some work item completion, e.g., a Portfolio-Epic, Feature and others.

While linking, you would go through the same linking experience as linking items to the Objectives.

2) By Target

Select this option when you need to define and track a Key Result where the target and progress are manual. For example, you may have a Key Result to Improve the Integration time by 45%

3) By Objective

This is a useful option for building "Cascading OKRs". An Objective can only be linked to another Objective through a "Key Result".

Create a Key Result of Type Objective and then link this Key result to another Objective. This way, the progress of your Key Result will automatically be calculated based on the linked Objectives.

Example Objective with all three types of Key Results

Type of OKRs

With the Kendis Enterprise Platform, OKRs can be created at multiple levels.

An OKR can be shared across different locations; e.g., an OKR created for one collection can be shown in a second collection.

Type of OKR

Description

Collections OKRs

OKRs for collection. A collection may represent a Portfolio, Agile Release Train, Department, or others.

Batches OKRs

OKRs for a Batch

Global OKRs

An Organization level OKRs

Program Board OKRs

Program Board Objectives with OKR style enabled.

Collection OKRs

A collection may represent a department, portfolio, Agile Release Train, or other entities in your Organization. OKRs in each collection are visible only to users with rights to access that collection. The Objective and Key Results are exactly the same as described above in earlier sections.

Batches OKRs

You may need to track the progress of OKRs for a specific batch. The OKRs created in a Batch are only visible unless associated with the other collections or batches.

Global OKRs

This is a section where you can create Cascading or normal OKRs that are more generic and are not specific to any Collection, Program board, or Batch.

Program Board OKRs

You may be familiar with these OKRs. By default in the Program Board, the OKR style is turned off, but you may enable it. Objectives at the Program board can be linked through Key Results to top-level OKRs from Collections, Batches, or Global. More information about Program level OKRs.

OKRs associations

You may share Objectives across different departments through associations, release trains, and batches. Associations are also labeled as Global Objective Relationships at the Objective modal window.

To make an Objective visible to a different collection or batch, open an Objective and select the target from the Global Objectives Relationships section

Once associated, it will show as a tag on the Objectives listing

Did this answer your question?