Good business value improvement articles/studies from improving sonarqube scores?

Does anyone have any good articles on business value/justification on improving Sonarqube scores?

E.g. decreasing the sonarqube scores means your project has better code velocity, less bugs, etc.

I couldn’t find anything on Sonarqube’s blog/site that might cover this and it seems like something larger teams/companies might have investigated already…

1 Like


You might find this academic paper on the impacts of technical debt interesting

Technical Debt: An empirical investigation of its harmfulness and on management strategies in industry


That was a really nice read…thanks :slight_smile:

Was hoping companies might have studied it and written up blogs…we’re having a hard time correlating improving Sonarqube stats vs. team happiness/velocity etc…