Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,551,907
Community Members
 
Community Events
184
Community Groups

Mapping OKRs in Jira

Hello Atlassian Community:

 

Would like to start a discussion around how Atlassian and other companies incorporate Objectives & Key Results (OKRs) into their Jira workflow?

Here's a scenario: A team runs the OKR Play and completes writing up their OKRs for the quarter using the Confluence OKRs template:

  1. How can they now map each Objective in Jira?
  2. How can they then map each Key Result of an Objective in Jira? 
  3. How can they then link feature candidates (story tickets) to each Key Result? Feature Candidates are the features or work items we pull from the backlog of 1 or more Jira projects during sprint planning which we THINK will help achieve our key results.

The goal is for these associations to be dynamic so that if, for example, a product manager updates an Objective or Key Result, the feature candidates that link to them reflect these changes. 

Similarly to how epics and the stories that roll up into them can be used as a mechanism to tell the story of how you arrived at the current state of a feature or product, it's important for anyone looking at a Jira story ticket to be able to see which Key Result it is linked to and which Objective it is linked to (i.e.: similar to the way Epic Links work).

I've read many articles which help explain what OKRs are and how to create them, however I haven't found 1 guide as to how to actually setup Jira to use OKRs. 

https://www.atlassian.com/team-playbook/plays/okrs

https://www.atlassian.com/software/confluence/templates/okrs

For example, the first article mentions that OKRs have been deployed at Atlassian itself, but not exactly how Atlassian uses Jira to integrate their OKRs:
https://www.atlassian.com/blog/jira-align/scaled-agile-okrs

 

A step-by-step guide on how to map OKRs in Jira would be super helpful!

1 comment

Weronika Spaleniak Appfire
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Sep 30, 2021

How about a Jira plugin that would help you manage the OKRs in Jira without having to switch to an additional platform?

Then, you won't have the issue with mapping Jira issues to objectives and key results, but you could still easily connect the Jira issues to the OKRs you've created in the plugin.

 

You can see how it works in our OKRs for Jira. We're developing the tool constantly, trying to be as user-friendly as possible and to really help Atlassian users in their OKR journeys. The plugin is also very affordable.

Best,

Weronika Spaleniak

Product Lead @ Digital Toucan

Comment

Log in or Sign up to comment