From the book by David J. Anderson “Kanban — An Alternative Path to Agility”
Capers Jones reports that in 2000, during the dot-com bubble, he evaluated the quality of programs for North American teams. The quality ranged from six errors per function point to less than three errors per 100 function points — 200 to one. The midpoint is approximately one error per 0.6–1.0 functional point. Thus, teams usually spend more than 90% of their efforts on fixing errors. There is also direct evidence of this. In late 2007, Aaron Sanders, one of the first followers of Kanban, wrote on the Kanbandev mailing list that the team he worked with spent 90% of the available productivity on bug fixes.
Striving for inherently high quality will have a serious impact on the performance and throughput of teams that make many errors. You can expect a two to fourfold increase in throughput. If the team is initially lagging behind, then focusing on quality allows you to increase this indicator tenfold.
One way to reduce the error density in the code is to regularly use static code analysis. Analyzers can detect an error at the earliest stage of its occurrence. As a result, fixing bugs found at an early stage is much cheaper. Additionally, the code that is regularly analyzed becomes cleaner and better.
Here is the conclusion — use the PVS-Studio static code analyzer regularly. This way your kanban board will indicate fewer bugs-related problems. This will save space for useful tasks and epic features. I wish you fruitful work!