> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/engineering-metrics/pull-request-metrics/efficiency-score.md).

# Efficiency Score

In our quest for engineering excellence, we've devised a metric, **‘Efficiency Score,’** to indicate team efficiency through a carefully crafted algorithm. This algorithm considers various team-level metrics, such as Cycle Time, Deployment Frequency, Failure Rate, Coding Days, and more. The result is an efficiency score that gives a snapshot of a team's performance.

<div align="left"><figure><img src="/files/FBhfbIMhMBYy54w7mQyF" alt=""><figcaption></figcaption></figure></div>

### Efficiency is dissected into three key components:

### Flow&#x20;

Reflects the speed of development.

* Pull Request Cycle Time
* Sprint Completion Percentage

<div align="left"><figure><img src="/files/aoPktu7V06Yq3Q05Od8T" alt=""><figcaption></figcaption></figure></div>

### **Quality:**&#x20;

Evaluate the code's robustness and reliability.

* Code Review Issues
* Average number of commits during the PR review process
* Percentage of Bugs & Incidents

<div align="left"><figure><img src="/files/fzkP5LldrD4ujkZIOFYK" alt=""><figcaption></figcaption></figure></div>

### **Throughput:**&#x20;

Measures the rate of delivering valuable output.

* Merge Frequency
* Deployment Frequency
* Coding Days

<div align="left"><figure><img src="/files/TWmiwlhUB6vgEECUOQ4K" alt=""><figcaption></figcaption></figure></div>

To categorize Flow, Quality, and Throughput as High, Medium, or Low, we assess each metric against specific benchmarks. For instance, a PR Cycle Time exceeding 180 hours & Sprint Completion Percentage of <30% falls into the "Needs Attention" category, indicating Low Velocity.

Once each metric's impact is evaluated and each component classified, our algorithm generates a rank, assigning a percentage value. A score of 100% represents outstanding performance across all metrics.

For instance: If Velocity is High, Quality is Medium & Throughput is Medium, the Efficiency score will be in the range of 60-80% - the exact value dependent on the metric scores as calculated by our ranking algorithm.

### **How to Leverage the Efficiency Score?**

Suppose a team's Efficiency score is 5.5. Clicking on the details reveals the breakdown of Velocity, Quality, and Throughput classifications. Identify the low-performing components, delve into the contributing metrics, and establish improvement goals. This iterative process enhances the team's Efficiency score over time.