# Deployment Frequency

**Deployment Frequency** reflects how frequently your organization successfully releases code to production.

This can be calculated in two ways:

* By tracking the number of pull requests (PRs) merged into the `main` or `master` branch.
* Or, by using your JIRA release versions to determine deployment counts.

You can choose the method that best aligns with your workflow.

<div align="left"><figure><img src="/files/Wfcp5QgdPsbgCoj7SIuY" alt="" width="563"><figcaption></figcaption></figure></div>

For any selected team within a given time range, Typo calculates the average number of Pull Requests created by the team's members that were merged into the main/master/production branch per week. The final merge branch to be considered is configurable & can be set as per your processes.

**Click here to learn more about** [**Deployment Frequency configuration** ](/typo-help-docs/configurations/deployment-frequency.md)

<div align="left"><figure><img src="/files/Hx3rulKmkEkxUeEV7SHG" alt="" width="375"><figcaption></figcaption></figure></div>

> Typo deployment Frequency benchmarks allow you to assess your deployment practices against industry standards and competitors, providing a measure of their efficiency and effectiveness. It also helps you to drive continuous improvement and create faster feedback loops.

### **How does measuring Deployment Frequency help in improving the Engineering team's efficiency?**

Measuring Deployment PRs helps improve Engineering teams' efficiency by providing insights into the frequency, timing, and success rate of code deployments. This data enables teams to identify bottlenecks, optimize deployment processes, and ensure timely delivery of features and bug fixes.&#x20;

1. **Identifying Bottlenecks:** Measurement of Deployment PRs helps pinpoint bottlenecks in the deployment process, allowing teams to streamline workflows and reduce time-to-deploy.
2. **Optimizing Processes:** By analyzing Deployment PRs, teams can identify inefficiencies and optimize deployment processes, leading to smoother and faster releases.
3. **Ensuring Timely Delivery:** Tracking Deployment PRs enables teams to monitor the progress of code changes and ensure timely delivery of features and bug fixes to customers.
4. **Supporting Data-Driven Decision Making:** Data from Deployment PRs enables teams to make informed decisions about deployment strategies, resource allocation, and prioritization of tasks, leading to more effective project management.


---

# Agent Instructions: 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:

```
GET https://typo.gitbook.io/typo-help-docs/engineering-metrics/dora/deployment-frequency.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.