# What Are Scrum Metrics? | 3 Examples | LinearB Blog

> Scrum metrics evaluate if development teams are delivering business value, working effectively, and following scrum best practices. Take a look at 3 scrum metrics examples you should be measuring.

_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)._


```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://linearb.io/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://linearb.io/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "What Are Scrum Metrics? | 3 Examples",
      "item": "https://linearb.io/blog/scrum-metrics"
    }
  ]
}
```

[Home](https://linearb.io/)

/

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

/

What Are Scrum Metrics? | 3 Examples

# What Are Scrum Metrics? | 3 Examples

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

By [Briana Johnson](https://linearb.io/blog/scrum-metrics#briana-johnson)

|

August 24, 2022

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

Scrum metrics evaluate if development teams are delivering business value, working effectively, and following scrum best practices. For this reason, scrum metrics are helpful for both established and new teams. 

Go beyond just tracking whether a sprint goal has been achieved or not. Tracking scrum metrics should cultivate awareness in [the team’s performance](https://linearb.io/blog/how-is-performance-measured-in-scrum) and drive action to change and improve over time.

Let’s take a closer look at what scrum metrics are to understand their importance.

## What Are Scrum Metrics?

Scrum metrics are part of a family of agile methodology KPIs. Almost all agile metrics can be applied to scrum teams, but scrum-specific metrics center around software delivery predictability and delivering value to customers with every iteration.

Or as we like to say at LinearB, [scrum metrics measure](https://linearb.io/blog/scrum-reporting) if you’re delivering on your promises and shipping more features faster.

Scrum metrics have three major goals:

* To measure the team’s predictability
* To measure their efficiency
* To measure developer happiness

Scrum team members should use these metrics to benchmark themselves, set target goals, and develop plans for improvement.

## 3 Scrum Metrics Examples

With the above goals in mind, here are 3 examples of scrum metrics to consider:

### 1\. Scrum Velocity

**Scrum velocity is the average number of story points that a group has completed during the past few sprints.** It is often used in sprint planning to forecast how much output a team can provide in future sprints.

![Velocity Chart. How to read this chart. Track the amount of work completed from sprint to sprint. This helps you determine your team's velocity.](https://assets.linearb.io/uploads/Velocitychart-1024x941-1.png)

In a scrum velocity report, the team has to consider several iterations. This is because the accuracy of their forecast will depend on the number of iterations that they determine. Many [scrum masters](https://linearb.io/blog/how-to-improve-scrum-team-productivity#keep-meetings-brief-and-to-the-point) believe that the more iterations they use, the more precise their prediction is going to be.

Additionally, velocity also determines how a team works through its sprint backlog. A declining velocity often means that there is an area that needs to be improved upon.

Unfortunately, [scrum velocity is a risky metric](https://linearb.io/blog/what-is-scrum-velocity-the-good-the-bad-and-the-ugly) for development teams to consider. This is especially true because team velocity looks at the past, which is not an accurate predictor of the future. If you’re actually looking to improve your team’s predictability and deliver on your promises, you should look at a metric unique to LinearB called planning accuracy.

We know that planning accuracy is hard. Learn more about [our six-step recipe for improvement](https://linearb.io/planning-accuracy).

### 2\. Cycle Time

Cycle time is a key metric for evaluating engineering efficiency. **Cycle time is the time it takes a team to complete a task from the first commit until the code goes into production.**

This metric is made of 4 key components;

* Coding Time
* Pickup Time
* Review Time
* Deploy Time

Cycle time evaluates how quickly a team can deliver features to its users. Teams looking to improve their engineering productivity should focus on decreasing their cycle time without compromising the quality of their outputs (i.e. without increasing change failure rate). 

Our Engineering Benchmarks feature shows leaders which phase of cycle time is causing the biggest setbacks to their software development process. Then teams can set custom goals based on the areas that need improvement to overcome the challenges.

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

These custom Team Goals connect directly to our WorkerB bot to tackle the bottlenecks and time lags that exist within your workflow. WorkerB ensures developer workflow optimization by [automating many non-coding tasks](https://linearb.io/workflow-optimization) of software developers. This feature is intended to let coders do what they do best: coding.

### 3\. WIP

**WIP (work in progress) is the number of tasks started but not yet finished.** Scrum teams often measure WIP and implement WIP Limits to improve developer workflow. 

Many scrum teams use a Cumulative Flow Diagram from their project management tool to visualize WIP.

![Cumulative Flow Diagram](https://assets.linearb.io/uploads/cumulative-flow-diagram-metrics-1024x616.jpeg)Source: [How to Read the Cumulative Flow Diagram \[Infographic\]](https://getnave.com/blog/how-to-read-the-cumulative-flow-diagram-infographic/)

The horizontal x-axis in a Cumulative Flow Diagram indicates time, and the vertical y-axis indicates issues. Each colored area of the chart equates to a workflow status. In the simple version above, the bottom color shows what’s done, the middle area shows WIP, and the top area shows work left to do.

The biggest thing missing from a Cumulative Flow Diagram though is actual Git activity. Very rarely is planned work the only work done during a sprint. Unplanned work, such as technical debt or scope creep, is often encountered in the midst of working on a planned issue and must be addressed immediately to complete the task at hand. 

In a [recent study](https://linearb.io/blog/data-integrity-inversion), we discovered that it’s quite common for developers to start working on these branches without creating or updating corresponding tickets. But our Pulse dashboard correlates data from your issue tracker and Git provider to show you what’s done, WIP, to do, and even unlinked branches (i.e. shadow work). 

![Unlinked Branches and OneClick Ticket](https://assets.linearb.io/uploads/unlinked-branches.png)

## Improving Your Scrum Metrics

Scrum metrics play a critical role in ensuring the success of a sprint. Scrum teams need to review them often, ideally during each [sprint retrospective](https://linearb.io/blog/6-tips-to-improve-your-sprint-retrospective-meeting), to understand what’s improving and what isn’t. 

Ultimately metrics alone don’t improve dev teams. They give you direction on what needs to be improved, but then you have to set goals and implement best practices in order for your scrum metrics to start improving. 

At LinearB, we provide all the metrics you need to measure predictability, efficiency, and scrum team health in one tool. But we also connect those metrics to industry benchmarks and customized Team Goals. Your custom Team Goals can then be connected to our developer bot, WorkerB, which provides real-time feedback to your devs in Slack or MS Teams to keep them aligned to the established best practices.

Improving scrum metrics at every level of your engineering organization starts with LinearB.

## Improve developer productivity with LinearB

Find us on

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

## Your next read

[![Cover image for Your software factory needs a context layer](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/unnamed_4_b35455ae7a?_a=BAVMn6ID0)](https://linearb.io/blog/software-factory-2026-ai-benchmarks-code-review-roi)

Eng. Metrics

[Your software factory needs a context layer](https://linearb.io/blog/software-factory-2026-ai-benchmarks-code-review-roi)

Data from 2.7 million pull requests across 253 engineering organizations shows a widening gap between developers using AI deeply and everyone else. An adoption...

[![Cover image for AI agents are killing the pull request and reinventing CI/CD](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Post_Name_2400x1256_5_496cdfde2d?_a=BAVMn6ID0)](https://linearb.io/blog/circleci-rob-zuber-ai-agents-pull-request-cicd-sdlc)

Eng. Metrics

[AI agents are killing the pull request and reinventing CI/CD](https://linearb.io/blog/circleci-rob-zuber-ai-agents-pull-request-cicd-sdlc)

CircleCI CTO Rob Zuber explains why AI adoption is killing the pull request and forcing engineering teams to completely reimagine the software development...

[![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...

## 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": "What Are Scrum Metrics? | 3 Examples",
  "url": "https://linearb.io/blog/scrum-metrics",
  "author": {
    "@type": "Person",
    "name": "Briana Johnson"
  },
  "datePublished": "2022-08-24T20:21:00.000Z",
  "dateModified": "2022-08-24T20:21:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1720000000/scrum_metrics_e10071c904.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Scrum metrics evaluate if development teams are delivering business value, working effectively, and following scrum best practices. Take a look at 3 scrum metrics examples you should be measuring.\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)
- [Watch now](https://linearb.io/resources/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 Library](https://linearb.io/library)
- [Engineering metrics](https://linearb.io/library/engineering-metrics)
- [Platform engineering](https://linearb.io/library/platform-engineering)
- [Engineering glossary](https://linearb.io/library/engineering-glossary)
- [Developer productivity](https://linearb.io/library/developer-productivity)
- [AI in software development](https://linearb.io/library/ai-in-software-development)
- [Engineering management](https://linearb.io/library/engineering-management)
- [Developer experience](https://linearb.io/library/developer-experience)
- [DevOps](https://linearb.io/library/devops)
- [Engineering operations and the context layer](https://linearb.io/library/engineering-operations)
- [Engineering efficiency](https://linearb.io/library/engineering-efficiency)
- [Software delivery](https://linearb.io/library/software-delivery)
- [Research and data](https://linearb.io/library/engineering-benchmarks-and-research)
- [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)