Agile Goal-Setting: OKRs, Sprints, and Continuous Improvement

What Is Agile Goal-Setting? Definition and Differentiation

Agile goal-setting combines the principles of agile work methods -- iterativeness, transparency, adaptability -- with systematic goal-setting. Instead of defining rigid annual goals and pursuing them unchanged, goals are set, reviewed, and adjusted in short cycles.

The core idea: No plan survives first contact with reality unchanged. Agile goal-setting accepts this fact and builds it into the process, rather than ignoring it.

The Principles of Agile Goal-Setting

• Iterative: Goals are set in short cycles (typically quarters) and evaluated at the end
• Transparent: All goals are visible to the entire organization
• Outcome-oriented: The focus is on results, not activities
• Adaptable: Goals can and should be adjusted when significant changes occur
• Collaborative: Goals are developed through dialogue between leadership and teams

Agile Goal-Setting vs. Traditional Goal-Setting

The best-known framework for agile goal-setting is the OKR method, which systematizes exactly these principles. OKRs are essentially the interface between strategic planning and agile work.

Why OKRs Are the Perfect Framework for Agile Teams

OKRs and agile methods share the same DNA: short cycles, transparency, focus on results, and continuous improvement. That is why they work so well together.

Shared Values

The Agile Manifesto emphasizes individuals and interactions, working software, customer collaboration, and responding to change. The OKR method connects exactly these values with a structured goal-setting process:

• Individuals and interactions: OKRs are developed within the team, not dictated by managers
• Working results: Key Results measure outcomes, not outputs
• Collaboration: Transparent OKRs promote cross-team alignment
• Responding to change: Quarterly cycles enable regular realignment

The Missing Puzzle Piece

Many agile teams have a paradoxical problem: They are excellent at delivering quickly but do not always know whether they are delivering the right things. Scrum and Kanban optimize execution -- but who defines which direction is right?

This is exactly where OKRs fill the gap:

• Scrum/Kanban answer: *How do we work efficiently?*
• OKRs answer: *What should we work on and why?*

Without OKRs, an agile team is like a high-speed train without a schedule: fast, but with no guaranteed destination.

Spotify: The Textbook Example

Spotify's Squad model is a prime example of combining agile work with OKRs. Each Squad (6-12 people, cross-functional) works in agile sprints but sets quarterly OKRs that contribute to the overarching Tribe goals. Squads have full autonomy in execution but are strategically aligned through OKRs.

The result: Autonomy and alignment at the same time -- the best of both worlds.

OKRs and Scrum: How to Connect Both Frameworks

Scrum is the most widely used agile framework, especially in software development. The integration of OKRs and Scrum follows a clear logic: OKRs define the why and where, Scrum defines the how and when.

The Levels of Integration

Deriving Sprint Goals from OKRs

The key to integration: Sprint Goals contribute to Key Results. If a Key Result is *Increase onboarding completion rate from 45% to 80%*, then successive Sprint Goals could be:

• Sprint 1: Implement onboarding analytics and collect baseline data
• Sprint 2: Identify and fix the three main drop-off points in the onboarding flow
• Sprint 3: Implement personalized onboarding for the two largest customer segments
• Sprint 4: Launch automated onboarding email sequence with contextual tips
• Sprint 5: A/B test the new onboarding experience and optimize
• Sprint 6: Measure results and evaluate OKR score

Each sprint delivers a concrete contribution to the Key Result, without the team losing sight of the strategic context.

Practical Tips for Integration

• Sprint Planning: Start each sprint planning with a brief OKR check: Which Key Results are we addressing in this sprint?
• Sprint Review: Show not only the delivered increment but also the progress on related Key Results
• Retrospective: Discuss whether the sprint work truly contributed to the OKRs or whether there is a discrepancy
• Backlog Refinement: Prioritize backlog items based on their contribution to current OKRs

What Does Not Need to Change

Important: Introducing OKRs does not require any changes to your Scrum process. The ceremonies (Daily, Planning, Review, Retro) remain intact. OKRs simply add a strategic layer that helps the team set the right priorities.

OKRs and Kanban: Continuous Improvement with Direction

While Scrum works in fixed sprints, Kanban relies on a continuous workflow. The integration of OKRs with Kanban has its own characteristics.

The Kanban-OKR Model

Kanban teams have no sprint rhythm that naturally aligns with OKR quarterly cycles. Instead, they use the OKR cycle as an overarching cadence while the daily workflow continues to be managed continuously.

The approach:

• OKRs set the quarterly direction (which outcomes are pursued)
• Kanban board visualizes the ongoing work
• WIP limits ensure focus is maintained
• Weekly OKR check-ins verify whether the workflow contributes to the OKRs

Kanban Metrics as Key Results

Kanban teams typically measure their performance through flow metrics. These are excellent as Key Results:

• Lead Time: Time from request intake to completion
• Throughput: Number of completed tasks per time unit
• Cycle Time: Time from start of work to completion
• Quality Rate: Percentage of results without rework

Example OKR for a Kanban team:

Objective: Deliver to our customers faster and more reliably than ever before

KR1: Reduce lead time for feature requests from 18 to 8 days

KR2: Increase throughput from 12 to 20 completed features per month

KR3: Reduce rework rate from 25% to under 10%

Continuous Improvement (Kaizen) and OKRs

The Kanban principle of continuous improvement (Kaizen) harmonizes perfectly with the OKR approach: Every quarter, performance is evaluated and new, ambitious goals are set. The quarterly retrospective of the OKR method and ongoing Kaizen measures complement each other -- Kaizen optimizes the daily flow, OKRs provide the strategic direction.

The Agile OKR Cycle: A Step-by-Step Guide

Here is a concrete roadmap for how agile teams can integrate the OKR cycle into their existing work process.

Week 0: Preparation (Before the Quarter Starts)

• Receive and understand company OKRs from the leadership team
• Evaluate retrospective results from the past quarter
• Collect data and metrics to serve as baselines for new Key Results

Week 1: OKR Planning

• OKR workshop (2-3 hours): The team collaboratively formulates its quarterly OKRs
• Align OKRs with company goals (vertical alignment)
• Identify dependencies with other teams (horizontal alignment)
• Enter OKRs into the OKR software

Weeks 2-11: Execution and Tracking

• Sprint planning / Kanban: Prioritize work based on OKRs
• Weekly OKR check-ins (15 minutes): Assess progress on each Key Result
• Confidence rating: How confident is the team in reaching each Key Result? (green/yellow/red)
• Mid-quarter review (Week 6): Deeper analysis of progress, adjust if necessary

Week 12: Scoring and Retrospective

• OKR scoring: Rate each Key Result on a scale of 0.0 to 1.0
• Retrospective: What did we learn? What will we do differently?
• Transition: Feed learnings directly into OKR planning for the next quarter

The Check-in Rhythm in Detail

The weekly check-in is the link between OKRs and daily work. Each team member answers three questions:

• How has the progress on my Key Results changed?
• How confident am I in reaching the Key Result by quarter end?
• What obstacles are in the way?

In agile teams, this check-in can serve as an extension of the existing sprint review or as a standalone short meeting. Northly simplifies this process with automatic reminders and an intuitive check-in interface that takes less than 5 minutes.

Agile Goal-Setting in Europe: Challenges and Solutions

Introducing agile goal-setting in the German-speaking region brings specific challenges that differ from the Silicon Valley perspective.

Challenge 1: Planning Culture

German companies are known for their thorough planning culture. The idea of adjusting plans quarterly can be perceived as a lack of thoroughness.

Solution: Emphasize that agile goal-setting does not mean less planning, but more frequent and targeted planning. Four lean quarterly planning sessions replace one elaborate annual plan and lead to better results. Learn more in our comparison Annual Planning vs. OKR.

Challenge 2: Hierarchical Structures

Many companies in Europe have steeper hierarchies than Silicon Valley startups. The bottom-up component of the OKR method can meet with resistance.

Solution: Start with a moderate bottom-up share (e.g., 30% instead of 60%) and increase it gradually as trust grows. The important thing is that leadership sets the strategic framework and teams receive autonomy within that framework.

Challenge 3: Works Council and Co-determination

In many German companies, the works council must be involved when introducing new goal-setting processes, especially if they could be used for performance evaluation.

Solution: OKRs are not a performance evaluation tool. Communicate this clearly and early to the works council. OKRs serve strategy execution and team alignment, not individual performance measurement. The deliberate decoupling from compensation is a strong argument here.

Challenge 4: Mid-Market Specifics

The Mittelstand has its own requirements: tighter resources for change management, established structures, often an owner-managed environment.

Solution: Start particularly small. Two pilot teams, one quarter, no additional software in the first round. Only when the value becomes visible should you invest in scaling and tooling.

Challenge 5: Perfectionism

The tendency to want to formulate OKRs perfectly before using them delays the start and raises the bar.

Solution: Accept that the first OKRs will not be perfect. The OKR method is a learning process -- quality improves with each quarter. Tools like Northly help with AI-powered feedback to accelerate the learning curve.

Practical Example: An Agile Product Team with OKRs

A concrete example shows how an agile product team combines OKRs and sprints in practice.

The Team

A cross-functional product team at a SaaS company in Zurich: 1 Product Owner, 4 developers, 1 UX designer, 1 QA engineer. The team works in 2-week sprints following Scrum.

The Quarterly OKRs

Objective: Improve the self-service experience so that customers can successfully get started without support help

KR1: Increase self-service onboarding rate from 35% to 65%

KR2: Reduce support tickets in the first 14 days from 4.2 to 1.5 per user

KR3: Shorten time-to-first-value from 6 days to 2 days

Sprint-by-Sprint Execution

Sprints 1-2 (Weeks 1-4): Discovery and baseline - Implement analytics for the onboarding funnel - Conduct 10 user interviews: Where do customers struggle? - Heatmap analysis of the existing onboarding flow

Sprints 3-4 (Weeks 5-8): First iterations - Fix the three biggest drop-off points in the flow - Build an interactive tutorial for the main use case - Introduce contextual help tooltips

Sprints 5-6 (Weeks 9-12): Optimization and measurement - A/B test the new onboarding flow - Personalization for the two most important customer segments - Final measurement of all Key Results and OKR scoring

The Weekly Rhythm

• Monday: Sprint planning (with OKR check)
• Tuesday-Thursday: Daily standups
• Friday morning: OKR check-in (15 min) -- assess Key Result progress
• Friday afternoon (biweekly): Sprint review and retro

The Result

After 12 weeks, the team achieved the following scores:

• KR1: Self-service rate at 58% (Score: 0.7 -- sweet spot)
• KR2: Support tickets at 2.1 (Score: 0.6 -- good progress)
• KR3: Time-to-first-value at 2.5 days (Score: 0.8 -- nearly achieved)

The overall score of 0.7 shows: The team set ambitious goals and achieved substantial progress. The learnings flow directly into the Q2 OKRs.

Conclusion: Agile Goal-Setting as a Competitive Advantage

Agile goal-setting with OKRs is not a trend but a strategic necessity in a world that changes faster than any annual plan. The combination of OKRs and agile work methods creates a system that simultaneously provides strategic clarity and operational flexibility.

The key takeaways:

• OKRs and agile methods complement each other perfectly: OKRs provide direction, agile methods provide execution
• Sprint goals contribute to Key Results: The strategic and operational levels are directly linked
• Quarterly cycles create learning loops: Four iterations per year instead of one
• Kanban and OKRs work just as well as Scrum and OKRs -- the integration approach differs slightly
• The Europe has specific challenges that can be solved with the right approach

The most successful agile teams in Europe use OKRs not as additional bureaucracy, but as a strategic compass that steers their agile work in the right direction.

Further Resources

• The OKR Method: The Complete Guide
• OKR Check-in Guide for the weekly rhythm
• OKR Templates for various departments
• Avoiding OKR Mistakes -- the most common pitfalls

Northly was built for agile teams: Lean OKR creation, automatic alignment checks, intuitive check-ins, and an AI Coach that continuously improves your OKR quality. Start for free and experience how agile goal-setting gives your team more focus and direction.