Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

How to ensure quality and performance in your release management

Compared to “Low” performers, “Elite” performers recover from incidents 2,604 times faster, with a lead time from commit to deploy that’s 2,555 times faster.

These results come from the 2018 State of DevOps report from DevOps Research & Assessment (DORA). I quoted these figures in a recent webinar to illustrate the vast difference in outcomes that can result from elite vs. poor DevOps practices.

According to DORA, the State of DevOps report “represents five years of work surveying over 30,000 technical professionals worldwide. The results allow us to better understand the practices that lead to higher software delivery performance that can generate powerful business outcomes.”

Rogue Wave enables DevOps teams

At Rogue Wave, it is our mission to help DevOps succeed by improving software quality and security, by simplifying software development and by shortening the time it takes to discover anomalies and react to incidents.

At Rogue Wave, we want to enable DevOps teams to become Elite, per this table from the DORA report:


Manual work

The DORA report has a section on manual work. The report states:

“When we compare high performers to their lower-performing peers, we find that elite and high performers are doing less manual work than their lower-performing peers at statistically significant levels on all dimensions, while medium performers have the highest amount of manual work on all dimensions.”

Here’s a table from the report:


Our Klocwork product can eliminate manual work. With Klocwork, developers find problems at the earliest possible point before the build, which means less manual work and testing later on.

Klocwork simplifies code testing by detecting issues while you’re writing code. It provides a traceback through the code to explain the execution path from where the problem started to where it ends badly.

Klocwork goes beyond savings in manual work. It finds defects in your code that could cost you customers and reputation. It finds them early in the process, so developers don’t have to go back and fix things later.


During the webinar, I provided a demo of QRebel, our product that catches harmful performance regressions during the development and testing stages.

According to the RebelLabs Developer Productivity Report, 75% of performance issues are discovered in production. QRebel can be used to shift performance testing left, enabling teams to catch issues before production.

I showed a complete DevOps workflow, with direct integration to Jira (trouble ticketing) and Jenkins (continuous integration).

The Jira integration ensures that any found regressions are presented to development teams with the necessary information to fix any issues. Via REST APIs, QRebel also integrates with Github, TeamCity, and Bamboo.

QRebel allows DevOps teams to know that by the time my application makes it into final deploy, that performance has been greatly enhanced.

I showed how new builds and versions are automatically picked up and represented on a timeline. This allows developers to pinpoint when a regression occurred.

Interested in QRebel?

If you’re interested in QRebel, visit our website to request pricing or a demonstration.