Offshore Process Overview

HMS's offshore arm has worked on engagements partnering with teams from the US, Middle-East, Europe and different countries in the Asia-Pacific region in delivering solutions for different target groups for specific countries. Working with teams from different countries and cultures has helped HMS develop a process that is flexible and can be adapted to the specific needs of the engagement. HMS understands that the same solution may have to be rendered differently when delivering to a different target audience in a different country. This understanding helps in ensuring that the requirements are well understood for the specific audience(s) and in reducing the time and effort required in sharing this understanding.

HMS has developed an offshore model that has matured in the last 3 years, applying the learning from the experiences in various engagements and working with different partners - both service and product companies.

HMS uses processes and tools that address the critical success factors for engagements utilizing the onshore-offshore model.

Largely, two modes of offshore development can be identified - one, in which all of the development is typically handled by a single offshore team and the other, in which development is by distributed teams, usually one onsite and another offshore.

  • Requirements are understood through a series of interviews onsite with the client team. These are documented using various aids (use cases/user flows, textual description) and passed on to the offshore team. The offshore team validates their understanding of the requirements and proceeds with the design, build and test.
  • Usually, HMS participates in the requirements process and has one or more of its resources available at the client place in the requirements gathering. However, where it makes sense based on the specific engagement, we also work with either the client's representative or partner's team in gathering the requirements, supported by members from HMS's offshore team. In these instances, we establish a clear understanding of how the requirements are captured and ensure that the requirements are well understood by the offshore team before proceeding with the subsequent phases of the development.
  • Distributed development - Rightshore Model - A combination of onsite and offshore teams
  • We have worked on different engagements (typically larger ones) where development is distributed, with both onsite and offshore teams. Depending on the needs, schedule, skills and the size of the teams, different components are developed by the different teams. The leads/managers are responsible for:
  • Ensuring that everyone participating understands the specific needs of the engagement
  • Coming up with the schedule and plan for the distributed development
  • Managing the integration of the different work products as they are delivered.