Co-shoring

Co-shoring is a new model for implementing IT projects with on-shore and off-shore components. Whereas, many off-shore projects (where the entire project team is off-shore) have failed, Co-shoring creates a model where some of the team is local (on-shore) to the project and the rest of the team is remote (off-shore). When done correctly, it creates a project environment with the perfect balance of customer satisfaction, efficiency, quality and cost.

The local team (on-shore) includes anyone that, by necessity, needs to be client facing. It always includes an on-site project manager that interacts with the client for any scheduling, scope, change, cost, quality, issues, risks and customer satisfaction issues. Other resources many include Business Systems Analysts. For example, during the requirements phase a BSA would need to directly interact with the client in JAD sessions; so, they would need to be local to the client. Another example is the Systems Architect (SA). Depending on the client, the SA may need to interact with the client's architecture team in a face-to-face forum. By having the client facing parts of the team local it promotes the highest levels of customer satisfaction – something that is missing in many off-shore only projects.

The remote (off-shore) team is usually parts of the technical team. This team is effective at taking development packages (requirements and specs) and developing, customizing or configuring applications to meet the desired results.

Several key components to Co-shoring include the utilization of development and project management controls and processes that are specific to remote project development and management; as well as, tools that help manage every facet of collaboration, communication and coordination.

The best Co-shoring is done with a total transparency. Everyone on the team can easily view, work with, guide and manage all the development and project management processes regardless of location.