OKRs and Agile combined in 3 steps

Objectives & Key Results (OKRs) has been largely spread over the past couple of years. Large organizations have adopted OKRs however, most of them are not making the most out of it. Simply, because guidelines are not respected and events are not set to govern a good implementation.

Keep it simple and focus on what matters.Confucius

Three steps to setup OKRs:

1. Define your team, timeline and related documentation if available

Team	@mention names or link to your team’s space
Timeline	Use /date to quickly add the date range for these OKRs
Related pages	Add links to past OKRs or any other key documents

2. Use the table below to define each objective and the expected key results. Put each objective in its own row, add objective owners, and type /status to add the score.

Objectives	Key results	Owner	Partner with	Expected EoQ key result score	Current status
e.g., Create a delightful and helpful experience in every single user interaction momentOwner: @mention ownerEnd-of-quarter objective score: 0.0-1.0	Decrease iOS “launch to send first message” time from average 20 seconds to 8 seconds.	@mention owner	@mention partners	1.0	Month 1We are 1 month into the quarter and have reduced average time from 20 to 18 seconds (10% reduction). We are confident we can find more ways to achieve our goal of 8 seconds (60% reduction) by the end of the quarter.Month 2…Month 3…

A simple example of a ‘good’ OKR looks like this:

Objective	Launch an MVP product website
Key Result 1	Forty percent of users come back two times in one week
Key Result 2	Recommendation score of eight
Key Result 3	Fifteen percent conversion to Premium plan

3. Combine OKRs with Agile/Scrum to create a value

1. Create the required OKRs as user stories in your backlog by highlighting the objective and the specific key results need to be achieved
2. Plan your user stories within a sprint of 2 or 4 weeks and assign it to the owner (mind dependencies if any)
3. Schedule your Sprint review by end of the Sprint to review the results achieved
4. Do a Sprint retrospective, measure the way results have been delivered, and optimize

Create OKR Backlog as Epics and User Stories Download

Example of a good and simple user story for an OKR

As an XYZ Corporate/Department,
I would like to achieve a product engagement of 80% WAU
in Q1,
So that I can increase my product value and strengthen my
competitive advantage
Acceptance Criteria:

1. Number of downloads….
2. Total number of users ….
3. Launch 5 surveys to understand how customers engage
   with our product
4. ….

See also >https://www.scrum.org/resources/what-is-sprint-planning and https://www.atlassian.com/team-playbook/plays/okrs

Sources: Confluence, Herbig.co, scrum.org, Own.