# Merge Frequency

{% hint style="warning" %}
Note: this metric is **only shown at a team level**, not an individual level.
{% endhint %}

![Merge Frequency graph](https://cdn.prod.website-files.com/610c8a14b4df1ae46b1a13a3/63480105db9cad1bbd9a2f5a_Merge%20Frequency.jpg)

**What it is:** This is an alternative to [DORA's Deployment Frequency](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance). It shows the median number of PRs merged per person on a team, over time.

**Why it matters:** This is an indicator of the value we're providing to customers, because it shows the volume of work being released to production. It can be useful to measure both `Merge Frequency` and `Deployment Frequency`. While it is best practice for each merge to automatically deploy to prod, often this is not the case - maybe your deploy pipeline is not yet fully automated, or it takes a while to deploy so you often want to batch changes. A significant difference between these two measures might indicate opportunities for improvement in your deployment processes.

**How we calculate it:** We count the **number of PRs merged** in each time period, **divided by the number of people on the team**. This normalization is to allow benchmarking of teams against industry standards, regardless of team size. 

Merged PRs are attributed to the person who **opened** the PR, not the person who performed the merge action. We use "merged" to mean "completed," reasoning that the person who opened the PR is most likely to have done the work.

You can filter for only collaborative PRs (ones that had input from someone other than the PR author) using the [Collaborative PRs toggle](/knowledge-base/collaborative-prs-and-all-prs-toggles.md).

{% hint style="success" %}
**What good looks like**

[Google suggests that elite teams should be deploying multiple times a day](https://storage.googleapis.com/gweb-cloudblog-publish/images/Calculating_the_metrics_frOhcbp.max-2800x2800.jpg). If we call that one deployment per day per team, that’s 5 deploys per week in a 5-day work week. Dividing this by a rough approximation of team size (around 5 developers), and taking into account the fact that there's sometimes more than one PR included in a single deploy (for major features, it could be best practice to collect up lots of changes into a release branch), we recommend keeping this metric over 2 PRs merged per person per week.
{% endhint %}


---

# 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://docs.multitudes.com/metrics-and-definitions/process-metrics/value-delivery/merge-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.