Onsite – Offshore Model of Software Testing Projects (and How to Make It Work for You)

The Onsite-Offshore approach is a commonly applied working strategy for many IT groups in the sector, particularly QA units. In this operation, one or more (based on the scale of the project) of the service provider’s QA members work in the same environment as the client.

The site of the client and the operational place of the service firm can be anywhere geographically – from across the planet or occasionally even within the same region.

Upon utilizing this operational approach, certain expectations arise from the Onsite and Offshore resources. Here are some pointers:

Duties Of An Onsite QA Representative/Coordinator

• Gathering technical insights from the client and dispersing it amongst the team
• Streamlining the transmission of timelines, progression, delays, etc. between the team and the client
• Discussing and handling the Test plan, along with reviewing Test scenarios/Test prepositions with the client unit
• Contributing to the Test data formulation stage
• Issuing Test execution directives
• Performing the preliminary and foundational test on deployed configurations and giving approval for the team to proceed with testing
• Sporadically being involved in the test execution phase
• Leading defect analysis meetings with the appropriate development and support units
• Gathering metrics
• Facilitating UAT (User Acceptance Testing)

Responsibilities Of An Offshore Group

• Developing Test scenarios based on the test plan
• Formulating Test cases after the Test scenarios receive approval
• Creating Test Data
• Carrying out the tests
• Documenting Defects
• Forming Test Reports
• Supplying inputs for Test Metrics aggregation
• Taking part in defect appraisal and other Project-Associated meetings

Pros Of An Onsite-Offshore Software Testing Approach

• When effectively applied, this approach ensures constant progression of the project all day.
• Direct client interaction enhances communication and solidifies business connections. It permits a smooth transition of information about the systems and the client’s needs.
• Cost-effective – Offshore groups cost less compared to forming an entire onsite QA team.

Commonly, issues arising in software projects often comprise:

• Onsite resources argue that Offshore resources lack skills and accessibility when required.
• Offshore units grumble about insufficient inputs.

Proposed fixes for these problems:

• Remember that Onsite and Offshore are equally significant in this scenario – neither supercedes the other. For the model to function effectively, these two sides should cooperate perfectly.
• Ensure there is at least an hour of joint working duration for both parties.
• Regular and efficient communication is necessary.
• Designate tasks for each other and work on fulfilling the list, continually giving feedback on progression.
• Consider differences in time zones. If helpful, do a quick interaction with the Onsite coordinator before starting work (at an appropriate hour) to set clear expectations.

For those whose tasks are strictly situated in one place, we trust this commentary clarifies how this approach works.

For those already functioning under this setup – kindly share your experiences. How do you facilitate effective interactions and synchronizations? Are there any obstacles? Does this approach prove helpful in any regard?

We invite your comments below.

A guest contribution by Swati Seela, a member of the STH team. You also have the opportunity to publish your guest articles on this blog. Find more information here.