Using Objectives and Key Results (OKRs) in Scrum

Objectives and Key Results (OKRs) act as goal-setting framework for defining and tracking objectives and their outcomes. OKRs are often misunderstood and are a powerful practice to create razor sharp organisational focus. Isn’t Scrum about goals and focus as well? There is the Vision, the Product Goal, the Sprint Goal as well as the Sprint Review.
These elements of Scrum can be very well combined with OKRs. Actually, you might want to turn it around, start with OKRs and map your Scrum implementation to them. In this Scrum Pulse webinar Professional Scrum Trainer Ralph Jocham with Agile Actors #learning  gives a quick intro to OKRs, and you then you will learn how Scrum can benefit from using OKRs to create a network of responsibility from the vision down to individual Sprint Goals. This responsibility network offers a transparency most corporations long for.

[larsrichter]

Stopped the video after 15 Min when Ralph presents an OKR "example". This should be an example how NOT to do OKR. There is a metric in the objective, it's not inspiring but just about Revenue. At least, this Objective should be a Key result. Also the Key Results are NOT Key Results, they are ToDo's, which is not outcome-oriented. So, this example is not an Objective with Key Results, it's a Key Result with a short ToDo-List at best. Very disappointing... (Didn't watch the rest of the video, because of that many failures with OKR, maybe the following part was better.)