The Cost of Bugs

The cost of bugs in an infographic that Typemock created. I've included this infographic and a link below.

As you can see, bugs and defects in software can be extremely costly to an organization — to the level of $60 Billion (US) dollars a year. That's about $113,333 a minute. Fixing bugs earlier is obviously cheaper. Take a look at the infographic. It has a lot of interesting statistics including the stat that agile projects are 300% more likely to succeed thank non-agile projects. Ironically, the statistics don't show how much more likely an agile project is to have a bug...!

The Severity of Bugs: Are We Doomed Infographic



Blog Categories

Blog Archives

Comments

  • it's all hammer and nails to agile project managers

    Posted by richard bucker on 01/07/2013 07:13am

    agile is agile project management which is different from the agile manifesto. The problem is that "people" are vested in what they know and like most fish are lured by shiny things.

    Reply
  • Agile Evangelism

    Posted by vbwyrde on 11/14/2012 06:44am

    There's a trend in our society for people to use so-called infographics to convey information as though it is scientifically accurate. They usually display statistical information along with leading statements such as "Developers suffered another 31 years..." However, in many cases these are spurious arguments, supported with unreliable statistics that were produced via biased methods by organizations with vested interests. It's a layered approach that tries to lend the impression of scientific accuracy and the aura of cutesy marketing glitz to cause the audience to believe that they'll quickly and easily benefit by taking some approach (and the consequent purchase of certain products or services to do so). This one gives me that impression.

    Reply
  • No surprise there - most "programmers" are mediocre or incompetent

    Posted by Larry on 11/14/2012 05:20am

    While nobody knows what the exact $ impact is, one thing I do know for sure is that by any reasonable standard, most programmers are lousy at what they do. Substandard work is the norm in our field, and most programmers would fail a competency test. This is the cause of most bugs, but unfortunately there are no easy solutions. A licensing system to practice software professionally might help mitigate some of the problem (to what extent is anyone's guess), but that won't be happening any time soon. For now, companies should do everything in their power to carefully screen the developers they hire. Most don't and they suffer the financial consequences. Good developers may be hard to find, but once you do, the financial savings are enormous.

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Testing full recoveries of IT environments requires a proven methodology. Establishing and meeting recovery time objectives (RTOs), configuring a cloud recovery system, and tracking your changing environment are all critical components of a successful cloud recovery operation. It's also important to establish and follow a set of cloud disaster recovery (CDR) best practices. Read this technical guide to learn about these best practices, along with how disaster recovery as a service (DRaaS) can help you complete …

  • Whether on the web, in the cloud or internal, your applications are increasingly vulnerable to attack. Knowing that you need to detect threats is one thing, but how can you find the right solution for your business? Learn how to evaluate application security testing (AST) technologies in Gartner's Magic Quadrant for Application Security Testing. Inside you'll discover evaluations of current solutions including Qualys and how to evaluate vendors based on their ability to execute and completeness of vision.

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date