Insightful stories on how companies make ‘buy or build’ decisions regarding QA services

In today’s article, Nadya Knysh — Managing Director at software testing company a1qa — talks about ‘build or buy’ decisions related to professional software testing.

Nadya Knysh, Managing Director at a1qa

What are the main concerns related to buying a QA team?

Concern #1: It’s not secure

Unfortunately, that’s a major issue for everyone these days. So yes, you have to be very careful when selecting a QA partner. Some companies provide so-called crowd-testing services when your solution is published online, and whoever wants to make some money can go for it and test it.

Concern #2: I cannot control the team

That’s a very popular statement — however, it’s not really valid. There are multiple tools and techniques that will work as your eyes and ears.

Concern #3: They are not sitting next to me

Well, yes and no. Of course, when using a third-party service provider, these people are not in the same physical room, yet they are still there when you need them. Even doctor’s visits are going online now, why shouldn’t that happen to QA engineers?

Real-life stories (not very successful, but very insightful)

In this article, I’d like to share quite complicated cases to help you better understand when an in-house team is not the best option or a third-party vendor is not the best choice.

Story #1

We had been working with a client of ours for just a few months. They already had development resources onboard as well as several business analysts, and they were desperately looking for an internal QA team or at least a QA engineer. It took them three or four months of nonstop interviews, phone screenings, CV reviews, and whatever else. Did they find someone they liked? No.

Moral: Be realistic regarding the quality of the resources you can get from the HR market in your region.

Story #2

Another client of ours started working with us after experiencing a similar situation, though it took them a bit longer to understand that they cannot always get what they want. Their QA budget was very limited, while their expectations of the resources were pretty high. Did they find someone they liked and could afford? Well, yes, but through a third-party vendor (this is us!).

Moral: Be realistic regarding what you can afford with how much you have in your pocket.

Story #3

For a client in New York City, we stepped in to set up the QA process. They already had a team of about six in-house QA engineers, and several more from the third party. We conducted the analysis phase and provided recommendations on how to proceed with the road map and priorities and estimates, and so on. About six months later, I met with the CTO of the company. I asked him how things were going. Did they implement the changes? No.

Moral: To establish good QA practice, you need someone to drive the car. If everyone is taking passenger seats, you won’t make it to Vermont.

Story #4

Another client of ours is an oil and gas company — we had been working with them for quite some time before 2008. In 2008, they had to minimize expenses and freeze most of their software and IT initiatives. That was a bad year for sure! They decided to go with a cheap QA vendor (as well as the development one). Did they manage to make at least one release in the next two years? No.

Moral: Cheap is not always that cheap. P.S. they came back to us in late 2009 and are still our clients.

Story #5

One of the banks here in the US was looking forward to developing a new payment solution, with fully internal software for transaction processing. They decided to hire a third-party company for QA services, and they did. Could they actually start testing? No.

Moral: If your project has very strict security or environment limitations, consider them early.

Story #6

One of our clients was going through a formal tender process. The procurement department had the only criteria — the cheaper, the better. And the cheapest proposal was offered by a company that had no idea what an OSS/BSS solution for telecommunication was. Was this project a success? Not really. Well, yes for us, but you know.

Moral: Check the credentials of your vendor if you want a long-term partner.

In a nutshell, there are several factors that one should consider:

1. Are your QA needs long term? You don’t want to play a hire-fire game every three months.

A final note

And yes, check your vendor — you’d never marry someone without dating (unless you are drunk and in Vegas). If you are looking for a long and fruitful relationship with a partner, you want to know how long they’ve been in business, what they can and cannot do, and what other clients are saying about them.

Software Testing & Quality Assurance Company. #QA #testing #mobile #security #performance #consulting #automation #telecom #ecommerce #banking #Agile #DevOps