Reawakening Agile with OKRs
summary
Argues OKRs fit between two-week iterations and long-term strategy as a 3-month, test-first management cadence that sets measurable hypotheses (not epics) and uses key results as acceptance criteria; recommends treating OKRs as the primary prioritization engine — even sidelining the Jira backlog — creating a team “API” for autonomy and cooperation; warns against cascading MBOs, target‑gaming, and points to Google’s ~70% stretch target while insisting success is measured by outcomes and learning, not 100% hit rates.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:25The Agile Virus
- 5:48Corporate Agile
- 11:24OKRs
- 13:39Objective
- 14:57Key Results
- 16:22Space for Autonomy
- 18:13Cascading Control
- 19:47Leadership
- 21:29Cooperative Model
- 23:28Ripples
- 24:53Purpose
- 27:07Prioritisation
- 30:05Acknowledge
- 30:19Backlog
- 31:51Backlog Advice
- 33:32Think Strategically
- 35:24Every Sprint Check
- 35:45What is Success
