We work with your management team to study all the processes and identify core/ non-core processes. We assess non-core processes for outsourcing that are closely relevant to your business objectives and can generate best value if outsourced to offshore destinations. At the end of this phase, you get an enterprise outsourcing model for your organization and a strategy to move to new outsourcing model.
This model is best suitable for small businesses or large businesses that are looking to outsource just one of their processes that have already been identified for outsourcing. Working with your leadership team and SME’s, our goal is to analyze the process for it’s off shoring value potential, ROI and organization benefits. At the end of this phase, you get cost-benefit-risk analysis, Value addition matrix, Best suited outsourcing solution for a business process and List of qualified offshore suppliers.
The purpose of the project concept is two fold. First, the project concept is used to focus the project team’s efforts and ensure all subsequent decisions and initiation activities have consistent objectives and direction. Secondly, the project concept is used to communicate those objectives and direction to buyer organization’s executive management who will make the “Go/No-Go” decision.
A Risk management Plan describes the project’s approach to and processes for risk identification and management. The Risk management Plan typically includes: Responsibilities for Risk management, Approach to Risk management, Risk Identification, Risk Analysis, Risk Planning, Risk Implementation, Risk Tracking & Control and Communications.
The Master Project Plan defines the resources, responsibilities, and major processes for designing and implementing an offshore outsourcing project. Some of the processes in Master Project Plan are Requirements definition, Request for Proposal (RFP) preparation, Proposal evaluation, Prime contractor selection, Contract award, Contractor oversight, System acceptance and System implementation.
When planning the project, it is important to consider the project’s approach to testing and acceptance. The intent of the Test Strategy is to establish the framework for testing the system and work products delivered by the Contractor. Testing Strategy identifies the types of testing that contractor is expected to address in their proposals. The Strategy also defines the level of participation for the buyer user teams and the responsibilities for all participants.
