Life before and after PVS-Studio

Life before and after PVS-Studio

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!

Download PVS-Studio.

要查看或添加评论,请登录

Andrey Karpov的更多文章

  • PVS-Studio: static code analyzer

    PVS-Studio: static code analyzer

    PVS-Studio is a static code analyzer designed to detect errors and potential vulnerabilities in the C, C++, C#, and…

    1 条评论
  • AI bots on Reddit and sharing some thoughts

    AI bots on Reddit and sharing some thoughts

    Today I stumbled across a thread on Reddit about bots hitting r/programming and leaving senseless comments and…

  • The collection of terrible tips for C++ developers

    The collection of terrible tips for C++ developers

    It could be tedious to constantly explain "how to do proper coding". So, I wrote a small book called "60 terrible tips…

    1 条评论
  • Singly and doubly linked lists in C and C++: general description and 4 implementations

    Singly and doubly linked lists in C and C++: general description and 4 implementations

    Again and again (on Stack Overflow and other websites) developers get questions about the implementation of…

    2 条评论
  • Events calendar for developers

    Events calendar for developers

    You may have encountered the problem when you are struggling to find out information about upcoming conferences you…

  • 0,1,2, Freddy came for Blender

    0,1,2, Freddy came for Blender

    This article could have been named "How PVS-Studio prevents rash code changes, example N7". However, naming articles…

    2 条评论
  • Who's up for talking about projects, researches or something else?

    Who's up for talking about projects, researches or something else?

    The PVS-Studio team publishes many articles devoted to the analysis of open-source projects, code quality, and…

  • 50 terrible coding tips for a C++ developer

    50 terrible coding tips for a C++ developer

    Whichever C++ article you read, it provides serious information, requires thoughtful reading — preferably with a cup of…

    7 条评论
  • How warnings simplify your code

    How warnings simplify your code

    When an analyzer or compiler issues a warning, sometimes it's hard to identify whether it's a false positive or a real…

  • PVS-Studio to help with schoolwork-like tasks in C and C++

    PVS-Studio to help with schoolwork-like tasks in C and C++

    Today I'll talk some more about questions posted on Stack Overflow — in particular, about another discussion started by…

社区洞察

其他会员也浏览了