Productive throughput and efficiency

What

This section gives critical metrics on code quality, and the overall productivity of the work being committed.

  1. Code churn: Code that is deleted/rewritten within 21 days of merging is called code churn or rework
  2. Productive Throughput and Efficiency: Code that is not churned, that is, code that does not get rewritten/deleted within than 21 days.
  3. Efficiency: Percentage of Code that does not get churned.

Why

  1. Identify problematic areas of code
  2. Identify problematic repositories
  3. Identify lack of expertise or a need to upskill your engineers
  4. Identify potential quality issues and probability of bugs in future edits

Subscribe to Hatica's blog

Get bi-weekly emails with the latest from Hatica's blog

Share this article:
Hatica logoEngineering Analytics to boost developer productivity
SOC2 monitoring powered by Vanta
GDPR monitoring powered by Vanta

Request Demo

Learn how Hatica can help you build effective engineering teams with data-driven insights

© 2019-2021 Hatica. All rights reserved.