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
  • What TCQI Measures
  • Core Concepts
  • Configurable Coefficients
  • Step-by-Step Calculation
  • 1. Calculate Issue Risk Scores
  • 2. Calculate Project-Level Category Risk Scores
  • 3. Final Total Code Quality Index (TCQI) Formula
  • Why Use TCQI?
  • Where to Configure
  • Summary

Was this helpful?

  1. QUALITY ANALYTICS

Total Code Quality Index (TCQI)

The Total Code Quality Index (TCQI) is a composite metric in Oobeya that quantifies code quality by analyzing SonarQube issue data through multiple lenses: severity, category impact (security, reliability, maintainability), remediation effort, and codebase volume. It provides engineering leaders with a clear, standardized, and customizable way to monitor and improve software quality.


What TCQI Measures

The TCQI goes beyond raw issue counts. It evaluates:

  • How risky issues are, based on severity and fix effort.

  • What impact they have across key quality dimensions.

  • How clean the codebase is by factoring in total code volume.

  • How the project compares to an ideal maximum through normalization.

This results in a set of actionable, easy-to-compare indices:

  • Total Code Quality Index (TCQI)

  • Security Index

  • Reliability Index

  • Maintainability Index


Core Concepts

TCQI is built on three core inputs from SonarQube:

Dimension
Description

Severity

Indicates how critical an issue is (Blocker, High, Medium, etc.).

Quality Categories

Reflects the issue’s domain: Security, Reliability, Maintainability. An issue may belong to more than one category.

Remediation Effort

The estimated time required to fix the issue (e.g., 10 minutes, 8 hours, etc.).

These inputs are transformed into scores using configurable coefficients defined by your organization.


Configurable Coefficients

All coefficients can be customized in Admin Settings > Code Quality > Code Quality Index.

🔸 Severity Coefficients

Severity
Coefficient

High

0.6

Medium

0.3

Low

0.1

🔸 Quality Category Coefficients

Category
Coefficient

Security

0.55

Reliability

0.35

Maintainability

0.1


Step-by-Step Calculation

1. Calculate Issue Risk Scores

Each issue is scored independently per quality category it belongs to:

Issue_Risk_Score = Severity_Coefficient × Category_Coefficient × Remediation_Effort

Because issues may belong to multiple categories, the same issue may contribute to multiple risk scores (e.g., both Security and Reliability).


2. Calculate Project-Level Category Risk Scores

For each category:

Project Category Risk Score = Sum(Issue Risk for that category)

Project Security Risk Score = Sum(Security_Issue_Risk_Score)
Project Reliability Risk Score = Sum(Reliability_Issue_Risk_Score)
Project Maintainability Risk Score = Sum(Maintainability_Issue_Risk_Score)

3. Final Total Code Quality Index (TCQI) Formula

Total_Risk_Score = Sum(Issue_Risk_Score)

TCQI = 5 × (1− (Total_Risk_Score / (Lines_of_Code + Total_Risk_Score)​)

Why Use TCQI?

  • Standardized and Scalable: Works across small and large codebases alike.

  • Actionable: Highlights critical areas in security, reliability, or maintainability.

  • Customizable: Adapt coefficients to align with your company’s engineering standards.

  • Measurable Over Time: Track quality regressions or improvements release by release.


Where to Configure

To tailor the TCQI model to your organization:

Go to: Admin Settings > Code Quality > Code Quality Index

There, you can:

  • Define severity weights

  • Set quality category priorities


Summary

Oobeya’s Total Code Quality Index provides a balanced, flexible, and insightful view of your engineering organization’s code health. It connects static code analysis to strategic engineering decisions—helping you drive long-term quality improvements.

PreviousUpdate the Agile Board AnalyticsNextAzure DevOps Guides

Last updated 9 days ago

Was this helpful?