Products

Problems
we solve

We can help your business

Request a Free Demo / trial

Insights

Insights | How to
3 November, 2021

WQR – 3 Software Quality Lessons From the Finance Sector

Software Quality Lessons From the Finance Sector

In previous years I have found the World Quality Report (WQR) lacks relevance for all but the largest companies in the world. This year, however, I found myself agreeing with a lot of it. This year’s WQR points the way for many companies. 

According to this year’s WQR, the financial sector sees higher software quality than other sectors. Potentially this is big money at play, after all, they have more to spend and more to lose if things go wrong. 

Building high-quality software is not just about throwing money at a problem. It’s about setting the right conditions for success and often implementing basic, but effective approaches.

Looking at the WQR, we can take 3 software quality lessons from the financial sector analysis: 

  1. Invest in Skills – Train Your Team
  2. Improve Communication and Collaboration
  3. Shift quality left, and right

3 Software Quality Lessons You Can Learn from the Finance Sector

In the Financial Sector analysis, the WQR highlights the top ‘conditions that contributed to increased efficiency in testing’. These are conditions that anyone can implement:

1. Invest in Skills – Train Your Team

Financial companies have consistently been among the first to use Agile and DevOps, AI (Artificial Intelligence) & ML (Machine Learning) and test automation. Critically, they have maximized their investment by employing and/or training staff to make these approaches successful.

It always amazes me when companies invest their hard-earned budget on elaborate systems, yet don’t spend a penny upskilling their staff. Imagine NASA building a space shuttle, then just expecting a pilot to make it work. It would be a disaster, the shuttle would either be left unused, or it would crash. 

Like the pilot, your staff are skilled in their current roles. Despite this, few if any people can just pick up new tech at the drop of hat. Skills must be learned and developed. With the right training though, your staff can become astronauts. 

Financial sector companies have learned that if you want to see the benefits of new tech, you must invest in those who will use it. 

These days, training isn’t expensive and it fits around working schedules. There are many different education and certification options including digital learning and instructor-led courses, both on-site and remote.

When you invest in technology you must make sure your staff have the right skills.

2. Improve Communication and Collaboration

Over the years, financial companies have developed widely disparate working teams. Whether subcontinental consultancies, regional offices, or sites spread out over cities and broad campuses. 

This experience has helped them foster communication and collaboration. Again, they were early adopters of communication technology and centralised test management tools. 

To make collaboration really work for software testing, you must have centralised quality processes. 

Test management tools like ALM/QC and Octane are essential. They provide a collaborative location where users can:

  • Access an overall view of quality
  • View and action their specific tasks
  • Understand how defects are affecting various integrated components
  • Assign and communicate issues and assets amongst each other

As with training above, test management tools are nowhere near as expensive as they used to be. With SaaS options and different license types, you can get proper, enterprise-grade test management tools for less than you think. 

If you’ve never used a test management tool, you’ve been missing out.

These tools are essential for driving collaboration and bringing the whole quality process together.

3. Shift Quality Left and Right

Testing has moved on since the old days. Testing used to be the final step in your software project, often treated as a box-ticking exercise. These days, testing has evolved into ‘Quality Engineering’ or QE.

With QE you proactively build quality into your software at every stage:

  • How to shift quality left. Drive quality into your development activities. Including rigorous scrutiny of requirements and specifications, and quality-driven development – including early functional automation and performance testing.
  • How to shift quality right. Ensure your solution continues to perform in live. Quality must not stop at the end of the implementation. Monitor your systems after project delivery with tools like Business Process Monitor

The Right Tools and Approaches Don’t Need to be Expensive

The financial sector has learned how to create higher quality software. We can all learn 3 valuable lessons from them.

  1. Invest in Skills – Train Your Team
  2. Improve Communication and Collaboration
  3. Shift quality left, and right

With these lessons, every organisation can increase their software quality, without breaking the bank. 

At Calleo, we provide class-leading quality engineering tools via SaaS or permanent licenses. 

Get in touch with us today to see how little these solutions cost, and how much value they add.

Would you like to know more? Get in touch today

Stephen Davis
by Stephen Davis

Stephen Davis is the founder of Calleo Software, a OpenText (formerly Micro Focus) Gold Partner. His passion is to help test professionals improve the efficiency and effectiveness of software testing.

To view Stephen's LinkedIn profile and connect 

Stephen Davis LinkedIn profile

3rd November 2021
Test Automation Hype

Are Test Automation Claims Just Marketing Hype?

Read the marketing collateral from test automation vendors and you’ll encounter bold promises around costs, coverage, and defect reduction. However, for many who have been through multiple automation initiatives, the reality frequently fails to live up to the pitch.

Adding More Testers Makes Quality Worse

When Adding More Testers Makes Quality Worse!

You’re deep into a project, go-live is rapidly approaching, but there is a mountain of testing to get through. Then, a key stakeholder chimes in, “Let’s just pull more people into testing.” It sounds logical: bigger effort, higher quality. But doubling down on resources can easily lead to chaos, confusion, and worse software quality.

Is Open Source Trustworthy

Do You Trust Open-Source Tools for Enterprise Testing?

Open-source testing tools like JMeter and Selenium have obvious appeal—no licensing fees, endless customisation, and a community to lean on. But, if you’re using open-source for mission-critical testing, you need to ask—is it really worth the risk?

Should testers be allowed to block releases?

Should Testers Be Allowed to Block Releases?

Your testers find a critical bug the night before a major release. Should they have the power to stop the launch?

Testers provide essential insights into software quality and risk. Their analysis is critical for decision-makers, so would it make sense to give them the power to veto releases?

Bug seeding

Bebugging: Would You Plant Defects to Test Testers?

Would you intentionally plant defects to test your test team? Bebugging, as it’s known, is a technique where software flaws are purposely introduced to gauge testing effectiveness. Are there times and places where bebugging is a valid way to help improve processes, tighten up testing, or root out a potential weak link?

Unethical Test Tool Marketing

Exposed: Are You Being Conned By Test Tool Marketing?

We have all witnessed an alarming rise in deceptive marketing practices that undermine customer decision-making and market integrity, with tool vendors increasingly comparing their tools to industry leaders using deliberately misleading information.

Flaky Automated Tests

Are Flaky Automated Tests Better Than None at All?

Is flaky automation better than no automation at all? Does it help accelerate projects and reduce timelines, or does it end up causing more problems than it solves? And are the questions moot when, with modern AI-powered tools, there’s no excuse for flaky tests?

Software Testing Concepts

Software QA Mythbusting: 5 Misunderstood Testing Concepts

We’ve all been there—sitting in a meeting, nodding along, confident that everyone shares the same understanding, only to discover later that our ideas were built on shaky ground, based on false assumptions and an incomplete grasp of a complex situation. In the world of software development, nowhere is this more common, or more consequential, than with software testing.

LoadRunner v JMeter

LoadRunner: Cheaper & Easier Than JMeter?

Four years ago, I wrote about how LoadRunner Cloud was debunking the myth that open-source is cheaper. At the time, LoadRunner Cloud’s pay-as-you-go pricing, bundled infrastructure, and rapid setup were already making it a compelling alternative to JMeter and similar tools.

Insights

Search

Related Articles

InsightsTrending

To get other software testing insights, like this, direct to you inbox join the Calleo mailing list.

You can, of course, unsubscribe 

at any time!

By signing up you consent to receiving regular emails from Calleo with updates, tips and ideas on software testing along with the occasional promotion for software testing products. You can, of course, unsubscribe at any time. Click here for the privacy policy.

Sign up to receive the latest, Software Testing Insights, news and to join the Calleo mailing list.

You can, of course, unsubscribe at any time!

By signing up you consent to receiving regular emails from Calleo with updates, tips and ideas on software testing along with the occasional promotion for software testing products. You can, of course, unsubscribe at any time. Click here for the privacy policy.