Testing Services provides a platform for QA professionals to discuss and gain insights in to the business value delivered by testing, the best practices and processes that drive it and the emergence of new technologies that will shape the future of this profession.

« Warehouse Management System (WMS) "System test" automation | Main | 'Fix it' or 'Build it right'? How do we improve quality through collaboration and shared accountability? »

Program managing multi-vendor QA teams - It is an Art!

If you take today's QA organizations, the presence of a multiple vendors/partners is a given. While this may be beneficial to organization from risk mitigation and cost efficiency perspective, it does pose significant challenges from a vendor/partner management perspective. This challenge gets further aggravated given the increasingly complex nature of IT programs and the short turn-around time demanded by business.

In such time-constrained and high stress environments, managing multi-vendor QA teams to achieve the common goal of zero defect leakage to User Acceptance Testing [UAT] and Production becomes harder and harder. In most cases, client QA organizations end up spending significant and valuable management time in resolving inter-person conflicts, rectifying communication deficiency between vendors, innuendos of favoritism, or in explaining to business stakeholders why the productivity of QA is low.

So, given these challenges, should QA Organizations look for a single-vendor strategy? Not at all. Multi-vendor/partner situations are here to stay. What organizations need to find is the best collaborative platform to ensure that they get the maximum from the partner set up that they have created.

From my experience of leading multi-vendor QA teams at several organizations, I have noted down few best practices that I believe can help you in this journey of maximizing value from your partner eco-system. According to me these are simple and common sense guidelines and have worked like a charm wherever I have implemented or adopted them.

Setting up a structure and process for the QA team:

Approach: Having a foundation for how the QA team should work internally and interact with other stakeholders such as Development, Build, Interfacing and Business teams is vital. Think through all likely interaction scenarios and draw simple swim-lane diagrams. Prepare a self-explanatory slide deck and share with the QA team and stakeholders to set expectations upfront. Hold lessons learnt sessions and implement action items from these sessions to foster continuous improvement. Ensure that you engage with client management, as well as leadership teams of all the vendors, to gain buy-in on the common process and structure, highlighting benefits to the program and thereby to each team member.

Benefits: Publishing structure and process for the QA team sets expectations and standard operating procedures such as stage-gate criteria clearly with stakeholders. This helps to send a common message for the QA team, irrespective of vendor affiliation.


Keeping program objective as the primary goal for the QA team:

Approach: Document the Program Test Plan with defined objectives for QA team, such as ensuring all requirements are covered with test cases, execution of all test cases prepared, retest and closure of all critical/ major defects detected during test execution. Also cover all dependencies the QA team has such as test environment, access needs, and test data. Publish and procure approval from stakeholders.

Benefits: Upfront planning, documentation and seeking approval from stakeholders on a Program Test Plan ensures all stakeholders are on the same page, and clear about entry and exit criteria expectations, risks, dependencies and objectives for QA team to be measured on. This ensures that the team members from multiple vendors march towards the common program objectives for the QA team.


Motivating teams through mutual respect:

Approach: Back to basics! Treat each team member with respect as an individual. Respect can go a long way towards motivating team members. Use data based decisions, avoid prejudices and favoritism, and suspend perceptions, while interacting with team members from multiple vendors. Display fairness and sensitivity in all interactions. Build trust with team members.

Benefits: Treating each and every team member with respect and fostering a culture of mutual respect motivates the team, aligns them to the QA team objectives thereby building a cohesive team. A cohesive team helps you to cross train and improve productivity.


In conclusion, the above tenets help prevent chaos and frictions associated with a multi-vendor QA team. If an organization leads from the front practicing these best practices, I am sure they will be well on their way to achieving their objectives of the program and satisfying business stakeholders.


Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Infosys on Twitter