Standard : Ratio of Planned vs Responsive Work

Description

Ratio of Planned vs Responsive Work measures the balance between work that was anticipated and committed during planning versus work that was added in response to unplanned needs, feedback, or emerging issues. It reflects a team’s adaptability while preserving focus.

This metric helps teams monitor how much of their time is spent delivering against strategy versus reacting to change. A healthy ratio ensures that teams remain agile without sacrificing predictability or long-term outcomes.

How to Use

What to Measure

  • Planned Work: Items committed during sprint planning or formal iteration scope (e.g. backlog items with planning tags).
  • Responsive Work: Items introduced mid-sprint, during a flow cycle, or outside the original scope (e.g. urgent fixes, feedback-driven changes, escalations).

Track this per sprint, week, or delivery cycle.

Formula

Ratio = Planned Work / (Planned Work + Responsive Work)

Alternatively, express as:

  • % Planned Work = (Planned / Total) × 100
  • % Responsive Work = (Responsive / Total) × 100

Example:

  • 8 planned, 2 responsive → 80% planned, 20% responsive

Instrumentation Tips

  • Tag or flag work as “Planned” or “Responsive” in your delivery tools.
  • Use board lanes, custom fields, or time-based filters to distinguish between them.
  • Review data during retrospectives or sprint reviews.

Benchmarks

Healthy ratios depend on team type:

Team Type Target Planned : Responsive Ratio
Feature team 80:20 or 70:30
Ops-support team 50:50 or more flexible
Mixed teams 60:40 or trend-based

Track trends, not just one-off snapshots — consistently high reactive work may indicate systemic issues.

Why It Matters

  • Balances responsiveness with strategic delivery
    Helps teams adapt without losing focus on committed goals.

  • Reveals system health
    High reactive work may signal upstream issues, poor planning, or weak discovery.

  • Improves planning discipline
    Encourages realistic capacity allocation and buffer management.

  • Informs staffing and process design
    Understanding the ratio supports discussions about team remit and organisational design.

Best Practices

  • Reserve capacity for known responsive work patterns (e.g. 10–20% buffer).
  • Collaborate with stakeholders to reduce avoidable reactive work.
  • Use retrospectives to explore causes of unplanned work spikes.
  • Make responsive work visible, discussed, and prioritised deliberately.
  • Adjust planning models as teams and work profiles evolve.

Common Pitfalls

  • Ignoring responsive work in planning, creating the illusion of stability.
  • Underestimating the cost of context switching or unplanned interruptions.
  • Failing to differentiate between legitimate responsiveness and avoidable reactivity.
  • Penalising teams for responsive work when it reveals system-level dysfunction.

Signals of Success

  • A stable, healthy ratio that reflects team purpose and delivery context.
  • Teams adjust plans smoothly when priorities change.
  • Stakeholders understand and support trade-offs when new work emerges.
  • Responsive work leads to valuable outcomes rather than thrash or noise.
  • [[Sprint Volatility Index]]
  • [[Work Replanning Rate]]
  • [[Time to Pivot (Decision to Implementation)]]
  • [[Schedule Adherence for Timeboxed Deliverables]]

Aligned Industry Research

  • Kanban Method (David J. Anderson)
    Encourages managing both planned and unplanned work as part of real system flow.

  • Scrum Guide
    Supports Sprint Backlog as a living artefact that can accommodate emergent work, balanced against the Sprint Goal.

  • Agile Estimating and Planning (Mike Cohn)
    Recommends capacity buffering and visibility for unplanned work to support adaptive planning.