Oobeya Docs
  • GETTING STARTED
    • Welcome to Oobeya!
    • Get Started with Oobeya
    • Playground: Live Demo
    • Oobeya Quick Onboarding Guide
  • TEAM INSIGHTS & SYMPTOMS
    • Symptoms Catalog
      • S1- Recurring high rework rate
      • S2- Recurring high cognitive load
      • S3- High weekend activity
      • S4 - High Code Review Time
      • S6- High technical debt on Sonar
      • S7- High vulnerabilities on Sonar
      • S8- High code quality bugs on Sonar
      • S9 - Unreviewed Pull Requests
      • S10 - Lightning Pull Requests
      • S11 - Oversize Pull Requests
      • S12- High Lead Time For Changes (DORA)
      • S13- Low Deployment Frequency (DORA)
      • S14- High Change Failure Rate (DORA)
  • SECURITY
    • 🔐Security at Oobeya
    • Oobeya Managed SaaS
  • INSTALLATION
    • 🐳Oobeya Docker Installation Tutorial & Requirements
    • 🐳Oobeya Version Upgrade For the docker-compose Installations
    • 🐳HTTPS Configuration For Docker Installations
  • PRODUCT DOCS
    • ⭐Oobeya Release Notes
      • 🎁Oobeya 2024 Q1 - Release Notes
      • 🎁Oobeya 2023 Q4 - Release Notes
      • 🎁Oobeya 2023 Q3 - Release Notes
      • 🎁Oobeya 2023 Q2 - Release Notes
      • 🎁Oobeya 2023 Q1 - Release Notes
      • 🎁Oobeya Nov & Dec '22 Updates
      • 🎁Oobeya September 2022 Updates
      • 🎁Oobeya August 2022 Updates
      • 🎁Oobeya July 2022 Updates
      • 🎁Oobeya June 2022 Updates
      • 🎁Oobeya Apr & May 2022 Updates
      • 🎁Oobeya March 2022 Updates
      • 🎁Oobeya Feb 2022 Updates
      • 🎁Oobeya Jan 2022 Updates
      • OOBEYA-2.0.8 - Release Notes
      • OOBEYA-2.0.4 - Release Notes
      • OOBEYA-2.0.0
      • OOBEYA-1.4.6
      • QAD-1.0 - 1.4
    • ▶️Product Tour
    • ❇️Metrics List
    • ☀️Developer Experience Metrics
  • INTEGRATIONS
    • Integration Catalog
      • SCM & CI/CD Integrations
        • Azure DevOps Integration
        • Bitbucket Cloud Integration
        • Bitbucket Server Integration
        • GitHub Integration
        • Step-by-Step Integration Instructions for the Oobeya GitHub Application
        • GitLab Integration
        • Jenkins & Cloudbees Integration
        • Octopus Deploy Integration
        • TeamCity Integration
      • Quality & Security Integrations
        • SonarQube Integration
        • SonarQube Cloud Integration
        • Veracode Integration
      • Project Management Integrations
        • Jira Cloud Integration
        • Jira Server Integration
      • APM / Monitoring Integrations
        • AppDynamics Integration
        • Azure Application Insights Integration
        • Dynatrace Integration
        • Elastic APM Integration
        • New Relic Integration
        • Sentry Integration
    • Installing An Addon
    • Adding A New Data Source
    • Updating and Deleting Data Sources
  • ADMINISTRATION
    • User Management, Single Sign-On, Auth Settings
      • Microsoft Entra (Azure AD) Integration
      • LDAP / Active Directory Integration
      • Importing a New User From LDAP / Active Directory
      • Bulk User Import in Oobeya Using CSV
      • Adding a New User
      • Deactivating a User
      • Understanding Roles in Oobeya
    • License Management
      • Updating The License Key
  • DEVELOPMENT ANALYTICS - GITWISER
    • Git Analytics - Metric Definitions
      • Coding Impact Score
      • Impact Ratio (team-level)
    • Setting Up Development Analytics And DORA Metrics
    • Git Analytics Exclusions
    • Setting Automated Reanalyze For Gitwiser
    • Deployment Analytics (DORA Metrics)
    • Merging Contributor Accounts
  • DORA Metrics
    • DORA Metrics Introduction
      • Lead Time For Changes (LTC)
      • Deployment Frequency (DF)
      • Change Failure Rate (CFR)
      • Mean Time To Restore Service (MTTR)
    • Failure Detection (For Change Failure Rate & MTTR)
    • How To Calculate DORA Metrics for GitHub
    • Updating Team Scorecard configuration to display DORA Metrics
    • How To Start Deployment Analytics (DORA Metrics) For An Existing Gitwiser Analysis
  • Project Analytics - AgileSpace
    • Agile Analytics - Metric Definitions
    • Agile Board Analytics Intro
    • Starting an Agile Board Analytics
    • Board Overview
    • Sprint Reports
    • Update the Agile Board Analytics
  • QUALITY ANALYTICS
    • Total Code Quality Index (TCQI)
  • Guides
    • Azure DevOps Guides
      • How To Calculate DORA Metrics for Azure DevOps
      • Best practices for integrating Oobeya with Azure DevOps Scrum Boards
  • PROFILES
    • Introduction
    • Adding A Profile
    • Developer Scorecard
    • Adding A Related Account Information To Oobeya Profile
  • Team Health
    • Adding A Team
    • Team Scorecard
    • Project Analytics (Scrum Teams) Widget
  • Test Quality Report Widget
  • CUSTOM DASHBOARDS
    • Adding A New Dashboard
    • Adding A New Widget
    • Updating And Deleting Widgets
    • Adding Jira Sprint Progress Widget
    • Adding Jira Board Metrics Widget (Metrics With JQL)
  • SUPPORT
    • Support Request Workflow
    • Customer Success & Support Guide
Powered by GitBook
On this page
  • Impact Ratio Metric
  • Calculation
  • Why It Matters
  • How to Use It
  • An Example To Better Understand The Impact Ratio
  • Conclusion

Was this helpful?

  1. DEVELOPMENT ANALYTICS - GITWISER
  2. Git Analytics - Metric Definitions

Impact Ratio (team-level)

PreviousCoding Impact ScoreNextSetting Up Development Analytics And DORA Metrics

Last updated 10 months ago

Was this helpful?

Impact Ratio Metric

The Impact Ratio metric in Oobeya measures the relative contribution of an individual developer compared to the team's average impact. This metric helps answer significant questions:

  1. How does an individual developer's cognitive load compare to the team's average?

  2. Are there significant imbalances in contributions within the team?

Before reading this guide, check out the metric.


Calculation

The Impact Ratio is calculated using the following formula:


Impact Ratio = Total Impact Score of a Developer / Avg Team Impact Score 

Factors Considered:

  • Total Impact Score of a Developer: The sum of the Coding Impact Scores of all contributions (commits) for a developer within the given period.

  • Avg Team Impact Score: The average Coding Impact Score of the team, calculated by dividing the total team impact score by the number of active contributors.


Why It Matters

Tracking the Impact Ratio allows Oobeya to identify the relative cognitive load and contribution of individual developers compared to the team average. This is crucial for recognizing:

  • Individual Health Symptoms: The risk of certain developers being overburdened compared to their peers.

  • Work Distribution and Collaboration Symptoms: Potential imbalances in work distribution that could affect team dynamics and efficiency.


How to Use It

While an Impact Ratio higher or lower than 1.0 isn't inherently positive or negative, it provides insights into individual contributions, workload balance, and knowledge silos. Here's how you can use it effectively:

Balance Workload Within The Team:

  • Monitor Ratios: Regularly track the Impact Ratios to identify developers who are significantly above or below the team average.

  • Redistribute Tasks: Adjust task assignments to ensure a more balanced workload, preventing burnout and promoting sustainable productivity.

Improve Processes:

  • Analyze Patterns: Examine patterns in Impact Ratios to identify areas where process improvements can help balance workloads and share the knowledge among team members.

  • Implement Changes: Introduce changes to streamline workflows, enhance collaboration, and boost efficiency, ensuring a more equitable distribution of cognitive load.


An Example To Better Understand The Impact Ratio

Consider the following example:

  • Developer A: Has a total impact score of 120x.

  • Team: Consists of 4 developers with individual impact scores of 40x, 120x, 30x, and 10x.

  • Total Team Impact Score: 40x + 120x + 30x + 10x = 200x

  • Avg Team Impact Score: 200x / 4 = 50x

Calculation:

  • Impact Ratio of Developer A: 120x / 50x = 2.4

Result:

Developer A has an Impact Ratio of 2.4, indicating that their cognitive load and contribution are significantly above the team average. This could be a sign that Developer A is taking on more complex or critical tasks, or it might indicate a need to rebalance workload within the team.


Conclusion

The Impact Ratio is a powerful tool in Oobeya's suite, providing valuable insights into the relative contributions and cognitive load of individual developers. By using it to balance workloads, recognize contributions, break down knowledge silos, and improve processes, you can support the well-being and productivity of your team, ensuring sustainable, efficient, and productive development cycles.

Coding Impact Score
Coding Impact Score & Impact Ratio