You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
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.
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:
A step-by-step guide on how to map OKRs in Jira would be super helpful!