How do you implement OKRs with Agile methodology?

OKRs (Objectives and Key Results) and Agile are complementary: OKRs provide strategic direction and measurable outcomes; Agile provides the delivery framework. Integration approach: (1) Alignment — company OKRs cascade to team OKRs. Team OKRs inform the Product Goal and sprint goals (Sprint Goals should advance Key Results); (2) Quarterly cadence — OKRs typically align with quarters (13 weeks ≈ 6-7 two-week Sprints). PI Planning in SAFe is a natural OKR-to-team alignment moment; (3) Outcome-focused backlog — Product Backlog items should be framed around customer outcomes (Key Results) rather than feature output. "Users complete checkout in <2 minutes" rather than "add one-click checkout button"; (4) Sprint Review alignment — Sprint Reviews evaluate increment value in terms of OKR progress, not just feature demos; (5) Avoiding conflicts — OKRs set the "what" (outcomes); Agile teams determine "how" (implementations). Don't use OKRs to prescribe features — they should prescribe outcomes. Challenge: OKR grading (40-70% achievement is "healthy") conflicts with the Scrum team's commitment to Sprint Goals. Treat Sprint commitments as execution plans for OKR achievement, not independent commitments.