Making OKRs and Scrum work together: an Agile Management guide
summary
Data engineering teams at Adevinta run Scrum plus OKRs for ~12 quarters and solve interruptions by splitting capacity into a fast lane (tasks <1 week) and a tech lane (multi‑week tech debt), rotating people quarterly; key results map to epics on the board and the strategic lane owns the highest‑priority KR end‑to‑end. A simple quarterly tracker spreadsheet holds objectives, sprint‑by‑sprint progress and a confidence band (red 0–20, yellow 21–69, green 70–110). This reduces context‑switching, raises finish rates (target ~60–70% OKR attainment) and requires ceremony changes.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:05Overview
- 1:22History
- 1:55What is a Lavinda
- 2:35Global Services
- 3:45The Problem
- 4:15Objectives and Key Results
- 9:45Managing Maintenance Tasks
- 11:00Reducing Sprint Length
- 12:20Fast Lane
- 12:50Tech Lane
- 13:05Lanes
- 14:45Culture
- 15:20Strategic work
- 16:10Recipe
- 19:35Where do things go wrong
- 20:55Keeping the big picture
- 21:45Quarterly tracker
- 23:50Objectives
- 26:15Demos
- 27:30Keep the big picture
- 28:50Summary
- 32:10Questions
related talks
39mReawakening Agile with OKRs
47mReawakening Agile with OKRs
31mWhy OKRs are ideal for agile methodologies
25mOKRs for Product Management
19mLessons in addressing data challenges while using OKRs
46mReawakening Agile with OKRs
43mPractical Strategy: How to relate your OKRs to your technical real-estate
46mOKRs beyond Business KPIs