QA strategy is an important part of a lot of our projects, but we haven’t been doing a very good job of showing off our work on the strategy end. That is, until today.
We just published a couple of case studies showcasing some interesting work that involved QA strategy elements and I want to highlight them here because there is a lot more to our QA strategy service than just creating a test plan.
QA Strategy for Junior Test Team
The first strategy case study that I want to highlight involves a company that had a test team composed almost entirely of junior testers. Their testers were doing a fine job of finding bugs. But the problem was that they weren’t finding the right bugs often enough.
An Optimus senior consultant visited with the company and determined what tests needed to be run while educating the junior client team to help them understand and better evaluate technical risks.
Meanwhile, the Noida team automated these tests running the first set of tests before handing them off to the client.
In the space of a month, the company’s QA practice went from inadequate to robust. And they did this without having to hire and retain expensive and difficult to find senior talent.
Perhaps the biggest benefit is that the client’s QA team now has an understanding of what to prioritize and why. The improved QA practices gives them a model for them to learn from and let the lessons crystallize.
Continue reading: QA Strategy for Junior Test Team
Incorporating QA in Upstream Engineering
The second strategy case study that I want to highlight involves a company with slightly more mature QA practices, but was looking to better integrate their QA efforts within agile development.
This is a good time to remind you that Optimus has software, BI and mobile-focused practices and our QA practice can draw on experts from the other practices when we need specialist knowledge like experts in agile development for example.
The client was already doing agile QA. Or they were at least trying to do it. QA practitioners were integrated into cross-functional agile teams and they were testing their team’s code as they wrote it making testing in integral part of each sprint.
As an aside, when you outsource agile QA with us, the testing is typically performed in our offshore facilities overnight. It’s not as intimately integrated as with in-house agile QA. But it keeps up with the pace of your agile teams just fine.
The problem was that the client didn’t have some key high-level testing infrastructure in place like proper test environments and appropriate automated tests, and they didn’t want to disrupt their QA practitioners who were still trying to figure out agile.
Our solution involved supplementing their QA staff with some of our consultants. Their staff would devote as much time as possible to the high-level testing infrastructure tasks we proposed without disrupting their agile teams, so that they would understand enough to own the new infrastructure while our staff ensured that the project wouldn’t take too long.
Finally, we wanted to use the project to demonstrate how agile is done and help them with their adoption of agile.
Continue reading: QA Strategy: Incorporating QA in Upstream Engineering
So, yes. We do write test plans and test cases. But QA strategy at Optimus goes way beyond just that and you should definitely contact us if you find yourself struggling on the strategy end.