Quality Engineering

Developing quality at pace

Quality Engineering in Banking

People talk about about “Quality at speed”, but people make mistakes at speed. Instead,
I prefer to think of “Quality at pace”
— Anne-Marie Charrett

Disrupters are challenging the brick and mortar banks challenging banks to develop be customer focused and quality software faster and smarter than ever before.  A fintech typically owns all it’s code, deploys weekly, can innovate and experiment on its customer database. A disrupter may only take a small percentage of the Australian market share but 4 more similar banks, that has a big impact on the traditional banking sector.

In response many banks look to the technology leaders like Google or Atlassian as a model to transform their processes. But a big part of change is Agile, and many have only just recently moved to Agile or not at all. They may wish to adopt an Atlassian or Google model and all that may entail, but they’re unable to adapt or contextualize a model coming from a technology product development organisation to their circumstances.

Traditionally organisations may bring in an organisation like Thoughtworks, who come in and solve various problems. But there is no sharing of skill and know how and once that organisation leaves, everything returns as it was.

Testing Times has developed a different model, the Quality Engineering model doesn’t focus purely on testing, but looks at the software development practices and provide alternative approaches to improve the quality of a product and get the people within a bank to a level of capability that they can stand on their own.

The focus hence is not purely on testing. Testing helps shine a light on the state of quality, in itself it does nothing to improve or change Quality. Testing is simply one of the many activities teams are trained on to improve the quality of their product.

Case Study: Macquarie Bank