> ## Documentation Index
> Fetch the complete documentation index at: https://www.scrums.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Observability

> The metrics and KPIs used to measure engineering delivery performance on the Scrums.com platform.

## Overview

SEOP captures delivery performance data continuously and surfaces it in your Analytics dashboard. This section explains the key metrics tracked, what they mean, and how to use them to improve delivery outcomes.

## DORA Metrics

DORA (DevOps Research and Assessment) metrics are the industry standard for measuring engineering delivery performance. SEOP tracks all four:

| Metric                       | What It Measures                                        | Elite Benchmark        |
| ---------------------------- | ------------------------------------------------------- | ---------------------- |
| Deployment Frequency         | How often code is deployed to production                | Multiple times per day |
| Lead Time for Changes        | Time from code commit to production                     | Less than 1 hour       |
| Change Failure Rate          | % of deployments causing failures or requiring rollback | 0–15%                  |
| Mean Time to Recovery (MTTR) | How long to recover from a production failure           | Less than 1 hour       |

DORA data is available on Recommended and Enterprise plans where pipeline integration is in place.

## Sprint Metrics

| Metric                 | Description                                             |
| ---------------------- | ------------------------------------------------------- |
| Velocity               | Story points completed per sprint                       |
| Sprint Completion Rate | % of committed items completed by sprint end            |
| Backlog Health         | Ratio of items estimated vs. unestimated in the backlog |
| Defect Rate            | Bugs found per sprint as a proportion of output         |
| Rework Rate            | % of items returned due to quality issues               |

## Team Metrics

| Metric                    | Description                                        |
| ------------------------- | -------------------------------------------------- |
| PR Cycle Time             | Time from PR opened to merged                      |
| Code Review Participation | % of PRs reviewed by peers                         |
| Code Quality Score        | SonarCloud quality gate status across the codebase |
| Utilisation               | Hours worked vs. hours contracted per engineer     |

## Using Metrics Effectively

Metrics are most valuable when tracked over time. Scrums.com recommends:

* Reviewing sprint metrics weekly as part of your team sync
* Using DORA metrics as a quarterly performance baseline
* Setting target benchmarks with your Enablement Partner during QBRs
* Sharing reports with technical leadership to align delivery investment with business goals