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.

Efficiency is dissected into three key components:

Velocity:

Reflects the speed of development.

• Pull Request Cycle Time

• Sprint Completion Percentage

Quality:

Evaluate the code's robustness and reliability.

• Code Review Issues

• Average number of commits during the PR review process

• Percentage of Bugs & Incidents

Throughput:

Measures the rate of delivering valuable output.

• Merge Frequency

• Deployment Frequency

• Coding Days

To categorize Velocity, 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 55%. 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.