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
  • Overview
  • Calculation
  • Formula
  • Why It Matters
  • How to Use It
  • An Example To Better Understand The Coding Impact Score
  • Conclusion

Was this helpful?

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

Coding Impact Score

PreviousGit Analytics - Metric DefinitionsNextImpact Ratio (team-level)

Last updated 10 months ago

Was this helpful?

Overview

Oobeya measures the Coding Impact Score by evaluating the magnitude of code changes, which helps answer significant questions:

  1. Approximately how much cognitive load did the developer experience when implementing these changes?

  2. What is the overall impact of these changes on the codebase?


Calculation

The Coding Impact Score is calculated based on the following factors:

  1. Files Touched: How many files were affected by the changes? How many new files were added or deleted from the code base in this Git commit?

  2. Complexity/Scope of Changes: How many insertion points (Git hunks) were changed in each file? How many different classes were modified, added, or deleted?

  3. Work Type of Code Changes: What was the work type of each code line change? How many code lines were newly added, edited, or deleted? To learn more about work types, please click .

Formula

Coding Impact Score of A Commit = (Files added x 10) + (Files modified x 6) + (Files deleted x 6) + (Git hunks x 4) + (New code lines x 0.14) + (Edited code lines x 0.28) + (Deleted code lines x 0.28)

Find below the weighted coefficient of parameters in the Coding Impact Score formula:

Change Level
Change Type
Coefficient

File

Adding a new file

10

File

Editing an existing file

6

File

Deleting an existing file

6

Block

Working on a Git hunk (a separate code block)

4

Line

Adding a new line

0.14

Line

Editing an existing line

0.28

Line

Deleting an existing line

0.28

In Oobeya, you can configure the appropriate coefficients in the administration settings.


Why It Matters

Tracking the Coding Impact Score allows Oobeya to identify the approximate cognitive effort of developers during development cycles. This is crucial for recognizing:

  • Team Health and Individual Health Symptoms: The risk of developers with high cognitive load burning out or becoming overloaded.

  • Working Practice / Collaboration Symptoms: The knowledge silos that have formed within the team.


How to Use It

While a higher Coding Impact Score isn't inherently positive or negative, it does shed light on the cognitive load your team members are experiencing. Here's how you can use it effectively:

  1. Balance Workload Within The Team:

    • Monitor high Coding Impact Scores over time to identify developers who might be at risk of overload and burnout.

    • Redistribute tasks to balance the workload, ensuring sustainable productivity.

  2. Recognize Contributions:

    • Use the Coding Impact Score to acknowledge and understand the complexity of the contributions made by each developer in a given period.

    • Highlight and reward significant efforts appropriately.

  3. Improve Processes:

    • Analyze patterns in Impact Scores to identify areas where process improvements can fix the unbalanced workload among the team members.

    • Implement changes to streamline workflows, empower collaboration, and enhance efficiency.


An Example To Better Understand The Coding Impact Score

To better understand the Coding Impact Score, consider the following example:

  • Commit #1: An engineer added 100 new lines of code to a single file.

  • Commit #2: Another engineer touched 6 files at multiple modules, adding 40 lines, modifying 20 lines, and deleting 20 lines of code.

This shows the total lines of code changed are the same (100 lines) for both commit activities.

Despite containing the same lines of code change, Commit #2 is likely more difficult to implement due to:

  1. Modifying previous work (modifying 20 lines + deleting 20 lines at 6 different files)

  2. Edits in multiple different locations (Git hunks/insertion points in code)

  3. Six different files were affected. The engineer should understand all modules affected, and test them and their dependencies.

Impact Scores for the example are calculated as

  • Commit #1: 24x

  • Commit #2: 92.8x

The Result:

They both had one commit and 100 lines of code changed, but the second engineer exerted approximately four times (3.86x) more cognitive effort on her task compared to the first engineer.


Conclusion

The Impact Score is a powerful tool in Oobeya's suite, providing valuable insights into the cognitive load on your engineering team. By using it to balance workloads, recognize contributions, improve processes, and enhance collaboration, you can support the well-being and productivity of your team, ensuring sustainable, efficient, and productive development cycles.

Explore the metric to get deeper insights into your team:

uses the Coding Impact Score metric to identify the '' symptom.

here
Impact Ratio
Impact Ratio (team-level)
Oobeya
Recurring High Cognitive Load