> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/definitions/dora-metrics/deployment-frequency.md).

# Deployment frequency

## Summary

Deployment frequency is one of the DORA metrics. It's the average number of deployments per week, over a given timeframe. It measures a team’s capability to move fast in practical terms: how long it takes to change something in production.

In Swarmia, we take the average of this number in a given time period and show the average number of deployments per day as the deployment frequency.

## Example

Between Monday and Friday, there were 25 deployments. That gives us a deployment frequency of 25, and an average deployment frequency of 5 deployments per day.

## Why it matters

Deployments are what makes work visible to the users, or in other words, what makes it possible for your work to deliver a business impact.

According to the authors of Accelerate, elite teams are able to deploy new code on-demand or multiple times per day, and the release frequency of high-performing teams is between once a day and once a week.

## Benchmarks

* **Great:** Continuously ( ≥ 10 deployments per week)
* **Good:** Daily ( ≥ 5 deployments per week)
* **Needs attention:** Less than daily ( < 5 deployments per week)

## How to use it

Monitoring your deployment frequency and tracking increases or decreases can help indicate certain issues in your system or process. For example, a low deployment frequency can indicate working with large batches or signal other problems, such as poor deployment infrastructure or lack of reliable automated tests.

## Where to find it

You can find deployment frequency (as well as the other DORA metrics) under Infrastructure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.swarmia.com/definitions/dora-metrics/deployment-frequency.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.