# How is Performance Measured in Scrum? | LinearB Blog

> Typically scrum team performance is measured by calculating the deliverables and effectiveness of the scrum team. Common metrics include velocity and sprint burndown. But these metrics are really just trying to demonstrate the team’s planning accuracy and whether or not they’ll deliver what they promised. Unfortunately, they’re rarely accurate because they’re based on estimated story […]

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._

[Blog](https://linearb.io/blog)

/

How is Performance Measured in Scrum?

# How is Performance Measured in Scrum?

![Photo of Sarah Shores](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/logo-mark-lg?_a=BAVMn6ID0)

By [Sarah Shores](https://linearb.io/blog/how-is-performance-measured-in-scrum#sarah-shores)

|

May 19, 2022

![scrum_performance_scaled_8dd2a40ed6](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/scrum_performance_scaled_8dd2a40ed6?_a=BAVMn6ID0)

Typically scrum team performance is measured by calculating the deliverables and effectiveness of the scrum team. [Common metrics include velocity ](https://linearb.io/blog/what-is-scrum-velocity-the-good-the-bad-and-the-ugly/)and sprint burndown.

But these metrics are really just trying to demonstrate the team’s planning accuracy and whether or not they’ll deliver what they promised. Unfortunately, they’re rarely accurate because they’re based on estimated story points. 

In fact, our research shows the industry average for planning accuracy is below 50%. That means that you’re estimating your scrum team’s performance capabilities, but you’re wrong more than you’re right. How embarrassing!

Let’s dive into why you should measure planning accuracy with LinearB and also the leading indicators of planning accuracy to investigate what’s driving it down.

## Table of Contents

* [Why Planning Accuracy Matters](#planning-accuracy)
* [4 Metrics to Benchmark Scrum Performance](#benchmark-metrics)
* [Set Scrum Team Performance Goals](#team-goals)
* [Optimize Scrum Team Workflow](#dwo)
* [Improve Scrum Performance](#improve)

## Why Planning Accuracy Matters

[Planning accuracy is the best metric to consider](https://linearb.io/blog/sprint-planning-best-practices) when measuring team performance in scrum because it allows team members to see if they have delivered on their promises or not. Having better planning accuracy leads to improved delivery and more value for the business.

The problem here is that a lot of companies aren’t reaching a sufficient level of it to be effective in achieving their sprint goal.

In fact, many development teams are failing more often than not because of low planning accuracy. The main culprit? Traditional tools for Git and issue tracking aren’t good enough.

Most of these systems fail to provide valuable insight into scrum projects, they don’t have automation capabilities, and they display issues in an unorganized manner. This is where LinearB comes in.

With LinearB, your can correlate data from project management and Git to supply information crucial to understanding what affects if they can deliver on their promises.

[](https://linearb.io/project-delivery-tracker/)Your CEO will love this! You can see your team’s investment profile, project allocation, and planning accuracy by boards, epics, labels or custom fields. [Learn more about Project Delivery Tracker.](https://linearb.io/project-delivery-tracker/)

## 4 Metrics to Benchmark Scrum Performance

Before you can jump into improving scrum performance, you need to know where to start. You need to first benchmark your team against industry standards. We currently have nine [benchmark metrics available from our study](https://linearb.io/resources/software-engineering-benchmarks-report) if you want to learn more.

But here are four metrics that are leading indicators to improve planning accuracy:

### Cycle Time

Long [cycle times](https://linearb.io/blog/cycle-time-measuring-and-improving-team-process/) reduce team efficiency and the ability to ship features predictably, so it’s one of the first metrics you should benchmark. Our research shows that the average cycle time for the dev teams studied was 6 days + 5 hours, but elite scrum teams have a cycle time of less than 48 hours.

Long cycle times reveal bottlenecks within your team’s PR review process. If you find that your cycle time is fair or needs focus, drill down into the four phases of cycle time to determine what needs the most attention.

![cycle time benchmarks](https://assets.linearb.io/uploads/cycle-time-benchmarks-1024x819.png)

### Pickup Time 

Long [pickup time](https://linearb.io/blog/pull-request-pickup-time/) is a common workflow bottleneck. It occurs for two reasons: 

* The team isn’t aware a PR is ready for review
* There aren’t enough developers available to review

In both instances, a longer transition time from coder to reviewer results in higher cognitive load (re-focus time) and reduced efficiency.

Our research shows that 50% of pull requests are idle for 50.4% of their lifespan, meaning that the average PR sits idle for two days! However, elite teams average pickup times less than 7 hours.

### PR Size

PR Size is so important to track and crucial improve your engineering efficiency, planning accuracy, delivery on your promises, and shipping features faster. All of which leads to higher customer satisfaction. It’s the magic bullet.

Large PR size means that your developer has lots of code changes to review. And it also usually signals that there will be several kinds of changes.

The code becomes hard to understand when the requirements aren’t broken down into digestible chunks. It also makes it more challenging to assess overall.

Our research discovered that PRs larger than 500 changes were less likely to be picked up for review but found clear evidence that, when we reduced PRs to less than 200 changes, these small PRs with lower estimated review time get picked up much faster.

Check out our presentation on how pull requests kill your productivity.

### Rework Rate

Rework (also known as code churn) means your team is having to revisit and make changes to code that is less than 21 days old. Typically, rework occurs because the developer struggled to write the code or only got a superficial comment during the code review process.

![work breakdown](https://assets.linearb.io/uploads/work-breakdown-png-1024x410.png)

Rework isn’t necessarily a problem. No matter how skilled your developers are, it’s impossible your team will have zero code rewrites, so a low rate of rework is healthy and expected. 

Our research shows that elite teams keep their rework rate below 8%, but when rework surpasses 20%, that’s a sign you should worry about it. 

Besides being an indicator of possible existing problems, a high rework rate can be a predictor of high-risk code. It’s more likely defects will be introduced into a piece of code if it gets edited a lot than one that nobody touches.

## Set Scrum Team Performance Goals

Using the insights gained from benchmarking your team and investigating bottlenecks, you should have a good idea of where your performance issues stem from. Now your scrum team can set goals, such as keeping PR Size under a certain limit, as one example.

Having this discussion during a [sprint retrospective meeting](https://linearb.io/blog/6-tips-to-improve-your-sprint-retrospective-meeting/) is a good place to start. A popular method to structure the discussion is Start, Stop, Continue. And once the scrum team has decided what they want to start/stop/continue doing, you can then set goals. 

We recommend that teams remember a few best practices while setting goals:

* Only work on 1-2 scrum metrics at a time
* Aim for a single-tier improvement over a quarter
* Start with PR size, as it will have the most significant benefits

[![team code review goals](https://assets.linearb.io/uploads/Group-6412_3x-1024x951.png)](https://linearb.io/demo/)Track progress by sprint, week or month so you can celebrate team improvement regularly. Let your team have cake! [Book a demo of LinearB today.](https://linearb.io/demo/)

## Optimize Scrum Team Workflow

Unfortunately, metrics and goals alone won’t improve dev teams. To truly improve performance and planning accuracy, scrum teams have to change how they operate. 

With our WorkerB bot, developers are notified in Slack or MS Teams when they’re off course from their team goals.

[![lightning pull requests](https://assets.linearb.io/uploads/Lightning-Pull-Request-1024x497.png)](https://linearb.io/get-started/)Avoid superficial LGTM reviews. Use Team Goals + WorkerB to reinforce good habits around review depth. [Get started today!](https://linearb.io/get-started/)

## Improve Scrum Performance

How do you improve performance in scrum? The quick answer is LinearB.

The LinearB approach to [improving scrum team performance starts with metrics](https://linearb.io/blog/scrum-reporting/), but you can’t stop at data-driven insights. You have to automate and optimize the developer workflow. For even more tips on raising your development team’s productivity using LinearB, check out [this post](https://linearb.io/blog/how-to-improve-scrum-team-productivity/).

LinearB can improve the way you measure scrum team performance and then guide you step-by-step into [improving that performance and planning accuracy](https://linearb.io/planning-accuracy/).

Want to improve your engineering processes at every level? [Get started with a LinearB free-forever account today!](https://linearb.io/get-started/)

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

## Your next read

[![Cover image for AI ROI comes from measuring engineering outcomes on day one](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_ROI_comes_from_measuring_engineering_software_security_2400x1256_2c5eae0862?_a=BAVMn6ID0)](https://linearb.io/blog/kraken-nik-sudan-measure-ai-roi-engineering-outcomes)

Eng. Metrics

[AI ROI comes from measuring engineering outcomes on day one](https://linearb.io/blog/kraken-nik-sudan-measure-ai-roi-engineering-outcomes)

Kraken Engineering Operations Lead Nik Sudan details how to establish day-one data infrastructure to accurately measure AI ROI. Discover why raw token adoption...

[![Cover image for AI is rebuilding software delivery from SDLC to ADLC](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_rebuilding_software_delivery_2400x1256_3fd5887e75?_a=BAVMn6ID0)](https://linearb.io/blog/sdlc-to-adlc-agentic-software-delivery-transformation)

Eng. Metrics

[AI is rebuilding software delivery from SDLC to ADLC](https://linearb.io/blog/sdlc-to-adlc-agentic-software-delivery-transformation)

Discover how engineering organizations are transitioning from the traditional SDLC to an Agentic Development Lifecycle (ADLC). Learn why rising token costs...

[![Cover image for 8 million pull requests reveal where engineering productivity breaks down](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_8_million_pull_requests_2400x1256_03724bfbb2?_a=BAVMn6ID0)](https://linearb.io/blog/8-million-prs-engineering-productivity)

Eng. Metrics

[8 million pull requests reveal where engineering productivity breaks down](https://linearb.io/blog/8-million-prs-engineering-productivity)

8.1M pull requests reveal the gap between AI adoption and engineering impact, and why code review is the bottleneck blocking real productivity gains.

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How is Performance Measured in Scrum?",
  "url": "https://linearb.io/blog/how-is-performance-measured-in-scrum",
  "author": {
    "@type": "Person",
    "name": "Sarah Shores"
  },
  "datePublished": "2022-05-19T13:01:21.000Z",
  "dateModified": "2022-05-19T13:01:21.000Z",
  "image": "https://assets.linearb.io/image/upload/v1720000000/scrum_performance_scaled_8dd2a40ed6.jpg",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Typically scrum team performance is measured by calculating the deliverables and effectiveness of the scrum team. Common metrics include velocity and sprint burndown. But these metrics are really just trying to demonstrate the team’s planning accuracy and whether or not they’ll deliver what they promised. Unfortunately, they’re rarely accurate because they’re based on estimated story […]\n"
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/engineering-productivity-gap)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)