Offshore Migration Approach

Protech understands that the right offshore management model is critical for a smooth transition and steady state delivery of applications development and maintenance. Our model recommends that the Protech leadership team (which includes offshore staff that remain onsite for the duration of a project) and subject matter experts be located onshore/onsite to ensure smooth knowledge transfer and effective project communication and controls.

Application development project’s business requirements, macro design and user acceptance testing are performed onsite, while micro design, build and unit testing are done offshore. Application maintenance involves a greater offshore component – with most design activities, build and unit testing performed offshore. Staff from the offshore location comes onshore during the transition of knowledge and work, then most return as leads and liaisons to the offshore team. The objective is to optimize the blend of cost effective resources while providing effective knowledge transfer and business support from Client to Protech team. Our methods carefully guide our staffing models with gated checkpoints requiring client approval that the appropriate objectives have been achieved before transition continues.

Approach
Protech’s success in migrating application development, maintenance and support work offshore results from our Offshore Management Model and our Migration Approach.

Onsite – Offshore Delivery Model

Governance
The management of application development and maintenance work by our client or Protech or a joint team will be based on a project /client requirement of an offshore initiative and processes are jointly developed by Protech and our client. When more applications move offshore, Protech recommends the establishment of an offshore program management structure that includes both client and Protech leadership.

Tools and Methods
When operating in a multi-location model, it is imperative that all members of the team are utilizing the same processes, which necessitates a strong, standard set of tools and methods. The management model and governance structure we propose will be supported by a comprehensive set of Protech methodologies and tools. These tools and methods have been designed to guide global teams through all phases of application development and maintenance and have been refined based on our experiences ensuring rapid project initiation, high project productivity around the clock and seamless integration of client and Protech on shore and offshore project teams. Our development methodologies are standardized, facilitating improved productivity, consistency, quality and streamlined management and communications. Protech’s approach to designing and developing custom applications is multi-phased, each phase building upon predecessors. This incremental and iterative approach allows Protech and our clients to refine both the design and the release strategy before construction begins. It also facilitates the evaluation of the viability of the solution in each phase throughout the engagement. The major phases of the approach are depicted in the figure below, with descriptions of each phase following:


Solution Phases
The Solution Outline and Macro Design phases are typically conducted as separate planning and high-level design projects. The Micro Design, Build Cycle and Deployment phases are then bundled together into a Release, which focuses on the detailed design, construction and deployment of the specific functions included in the application release.

Solution Outline
The Solution Outline phase provides a process, through which the complexity and scope are defined and the overall strategy and approach for the design and development effort is established.

Macro Design
The Macro Design phase prepares the groundwork for the Release phases by developing architecture designed to withstand business changes through the delivery of the solution. Macro Design moves the focus from business to technology strategy, addressing the global, architectural issues affecting all releases. The standards, guidelines and architectural results developed during the Macro Design phase will help minimize long-term development cost by reducing re-work, from release to release.

Build Cycle
Development and testing of the solution Release take place during the Build Cycle. This is an iterative phase with each Build Cycle containing several incremental programming and testing cycles. An assessment of business conditions and validation of the release strategy is performed before the construction of each release, providing an opportunity for adjusting the design and release strategy to help respond to changes in scope. Changes in scope may change the cost and schedule and will be handled using change control.

Deployment
The objective of Deployment is the managed roll-out of the solution Release. The migration of users from other systems and the required data conversions also are managed in this phase. Each release is evaluated and the results fed back into the assessment of the next release. A pilot may be used to verify that each release functions as expected.