Tech Debt - Sonar Maintanability

Overview

Overview

Definition (Hover Text)

explains the estimated time required to fix all Maintainability Issues/ code smells

Source Tools

Sonarqube, Sonar Cloud

Graph type

Line

Filters

Sonar Project

Hover Format on KPI

Date Range:<<Days>>

Fields on Overlay

Project

Job Name

Tech Debt

Week

Business Logic

Calculation Formula

It is calculated as effort to fix all Code Smells. The effort is calculated in minutes and converted to days by assuming 1 Day=8 Hours 

Trend

Lower the days, better is the ‘Quality’

Maturity Levels

M1: >100 days 

M2: 50-100 days

M3: 30-50 days,

M4: 10-30 days,

M5: <10 days

Instance level thresholds

 

Configurations

Processor Fields

NA

Mandatory fields

NA

How to Validate KPI

Suggested ways of working

 

Sample JQLs

 

Benefits of KPI

How does the KPI help

The Tech Debt - Sonar Maintainability KPI helps teams identify and address areas of the codebase that require improvement, reducing technical debt and improving code maintainability. This leads to increased development efficiency, reduced bugs, and improved long-term code quality.

C

© 2022 Publicis Sapient. All rights reserved.