> ## 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.

# Developer Productivity

> Measure engineering workflows at the team and system level without ranking individual developers.

## Measure the system

Developer productivity describes how effectively your engineering system turns effort into valuable software. Scrums.com measures workflows and outcomes at the team level. It does not create individual leaderboards or developer scores.

## Signals you can use

| Signal       | What it helps you find                         |
| ------------ | ---------------------------------------------- |
| Cycle time   | Queues between first commit and production     |
| Review wait  | Pull requests waiting for attention            |
| Throughput   | Changes completed over time                    |
| Code churn   | Rework after changes merge                     |
| Quality      | Coverage, static-analysis, and security trends |
| Blocked work | Work stalled beyond an agreed threshold        |

These signals complement DORA metrics. DORA describes delivery throughput and stability. Workflow signals help you explain why those outcomes change.

## Review productivity data

1. Connect the tools that hold your work and delivery history.
2. Confirm that teams use consistent workflow states and production markers.
3. Establish a baseline using each team's own history.
4. Identify a queue or constraint you can change.
5. Review the trend after the change.

<Warning>
  Do not use activity volume, lines of code, or isolated commit counts as individual performance measures. These measures ignore work complexity and encourage harmful behavior.
</Warning>

## Related

* [Team observability](/docs/platform/team-observability)
* [Engineering capacity planning](/docs/platform/engineering-capacity-planning)
* [Developer productivity capability](https://www.scrums.com/platform/developer-productivity)