Why Finding Software Bugs is not Always bad

I started in this industry in the Finance sector and then moved to the Delivery area, where the code is built. In this new area, I wonder daily if everything I hear down the hall makes sense and it encourages me to read and learn a bit more about what the people with whom I work with do every day.

Communication and interaction are vital to solve problems faster and to develop teamwork. Flexible environments like Intraway’s, help to keep employees motivated. Know more!

At Intraway, I hear lots of people talking about quality. Given that, I started to read several blogs and articles on the subject, to understand if what I heard was something familiar in the industry or just a problem of our company.

Even though we can have some KLIs & KPIs to help us measure the quality of our products, even if we always reach our goals, I realized that the most accurate way to measure the quality of our products is with the feedback of our customers.

Now, let’s dig a bit more about some of the KLIs and KPIs that help us avoid getting to our customers with some issues. Measuring bugs is one of the indisputable indicators.

A fundamental concept to keep in mind is that it’s ok to have bugs! Software without bugs doesn’t exist. But besides that, we need to understand there are different stages in which we can find them. The most beneficial, less expensive option is to find them while we test the code, in the QA processes with unit tests for example.

When we are working on a project, we need to take into account that we will be dealing with three necessary parameters that measure our success in project management, the scope of the project, the time needed in order to deliver it, and the resources/budget required to achieve it.

We need to find a balance among the 3 of them to keep our company profitable and our customers happy.

Trying to develop the perfect product/project will lead us to an eternal testing process, trying to find the highest volume of bugs possible, but that will make us extend the scheduled delivery date of the project and increase its costs.

We need to find a balance between what we want to build, how long it will take us to make it, and at which cost, in order to get the higher quality possible and satisfy our customers.

If the customer’s testers find bugs that have a significant impact on the performance of the product, though the financial cost to solve them would be the same, that scenario will make our product seem as not sturdy. There will be an implicit cost here, higher than spending more time testing at a prior stage.

So, again, don’t think that finding bugs is terrible. Let’s encourage our teams to make all the appropriate testing and correct bugs at early stages.

The satisfaction of our clients will be the best reference for our quality. Not giving them a bug-free software (as we all know it’s impossible), but to provide them with the functionality they need, by the time they require it is vital in our industry.

Communication and interaction are vital to solve problems faster and to develop teamwork. Flexible environments like Intraway’s, help to keep employees motivated. Know more!

Menu