Why and how to combine OKR & Scrum?

In all these years I’ve worked for/with?Scrum?Teams, one common problem I’ve observed was that most of the teams didn’t have access to the big picture. There was a huge gap between vision and strategy and the work the teams delivered. Almost nobody had a transparency if and how they’ve contributed to the success of the company.

Can OKR help to close this gap?

Most Scrum Teams are unfortunately turned into “Feature Factories” who deliver a feature and start developing the next one. They don’t pause to reflect and analyze if the feature really solved a problem or made the life of their customers or users easier. The question about the outcome of their output remains unanswered.

If the team and organization want to escape from the feature factory, and remain aligned but still autonomous instead, outcome-oriented OKRs could help.

How do OKR and Scrum work together?

I’m personally very happy about the new addition of “Product Goal” in the Scrum Guide 2020. Product Goal helps the teams to make their probably rather abstract product vision more tangible. If a team wants to make the product goal tangible and measurable then I’d recommend to do so in form of OKR.?

A product goal written in the form of an OKR, derived from company / product strategy, can help the team to focus on the most important thing for now. After the delivery the team can analyse the outcome by observing the progress made in Key Results (as described in the?Scrum Guide?“progress towards goals”). The key is, of course, to write measurable outcomes. Depending on the information they gather on the way, the team can re-define their approach and activities they do in?sprints.

An example might help to understand it better.?

Strategic Focus:?Seamless checkout process

Objective:?Customers love our new “accountless” checkout process.

1. Key Result 1:?30% of customers login via 3rd?party (G, FB, A)
2. Key Result 2:?40% of customers w/o account return within 4 weeks.
3. Key Result 3:?Conversion rate of Touchpoint X is increased by 10%.

• Backlog Items for KR 1:?Enable Google Login, Enable Apple Login.
• Backlog Items for KR 2:?Observe returning customers behaviour, Make an attractive offer/reason to return.
• Backlog Items for KR 3:?Prototype and conduct customer interviews, Redesign touchpoint X,?AB test it.

How to combine OKR and Scrum events?

OKR?Definition

Every 3-4 months (depending on the pace of the team/organisation) the team and involved people can write OKR-Set(s) (1x Objective and 2-3 Key Results per Objective), that manifests the direction and focus for the next period of time.?

In case there are more than one team working on the same product, it is not necessary to write an OKR-Set per Team. Each team can contribute by focusing on different Key Results. Though, it depends strongly on how the teams are organised and how the OKR set is written.

Product Backlog:?Based on the OKR-Set, the team can identify which experiments, activities, features, initiatives, etc. would help to move towards their product goal. This will also make the decision making progress much more easier.

OKR Check-in

After each sprint in the sprint review the team can discuss if and how their activities moved the needle in Key Results. If there isn’t any, what could be the reason? Should the team maybe re-think their approach? Maybe experiment on other aspects? OKR Check-Ins are for these kinds of conversations take place in the OKR Check-Ins.

OKR Reflection

At the end of the OKR Cycle, (e.g. 6x 2 weeks sprints = 12 weeks), it is now time to review the big picture? All the involved people can evaluate their progress made in Key Results. Which outcomes have been reached? What about the Objective? Have we accomplished the Objective itself indeed? If not, why not? Have we chosen the right Key Results at all? Have the circumstances changed? Is the goal still relevant today? What do we learn of it? What should we do differently in the next iteration??

Also have a retrospective regarding the OKR process. What works well? What not? Generate ideas to improve the collaboration along the way.?

With all these learnings the team can now start the next OKR Cycle by writing a new set of OKRs.

OKR fosters sense of ownership

The scrum teams I’ve worked with found the combination of OKR & Scrum very helpful as they had much more clarity and transparency about their focus and sprint goals. Also reviewing their outcomes after the sprints gave them a sense of contributing to something bigger and started thinking with the end in mind.?

Thinking in outcomes is not easy but crucial to make OKRs work. Most probably you won’t write the perfect outcome-oriented measurable goals at the beginning. But that is ok, give it time.

Also keep in mind: It is not about the perfection, it is about the progress and learning along the way.

Do you face challenges when working with OKR & Scrum? Do you find interesting what you read? Like, share and comment.

Sign up for my public and/or in-house workshops. Link in the first comment.

Cansel S?rgens guides organisations of all sizes from different industries as Strategy | OKR Coach and Trainer. She shares her 15+ years experience in Agile Organisation Development as speaker, author, and founder of OKR Lean Coffee, OKR Open Space, and Reshaping the Future of OKRs.

#fixmyokr #okr #okrs #okrandscrum #outcomeokr #holisticokr #changewithokr #productokr