- ETL: A large project will use an Extract, Transfer and Load (ETL) tool to move data where it can be used by the SPM solution. With proper access, an offshore team can make a significant contribution to this process.
- Configuration Management: An implementation is usually carried in different environments; development, various testing envionments, and production. Moving the latest files from one environment to the next can be very time consuming, and often can’t be performed while a team works in the environment.
- Reference Data: Loading all the reference data including participants, titles, positions, relationships, territories, etc are activities which will not impact the building of plans, until required for testing.
- Quotas, rate tables and lookup tables: Creating and updating these objects can be a very time consuming activity.
- Formulas and rules: Sometimes, several formulas and rules which are almost identical to each other are required. Not all SPM solutions have an easy “clone” feature, making this activity very tedious.
- Processing: Also called pipeline in Callidus TrueComp, with a large number of participants and of transaction (in late testing phases), processing can take up to several hours. It can be very nice for the onshore team to work on the implementation during the day and come back the next morning to find the results ready and analysis of issues that occured.
- Testing: Testing can be a tedious job. As I discussed before, test scripts should exist which will be executed again and again… and again. Some of the first testing phases such as unit testing and system testing can be almost entirely offshored, but later phases such as integration testing and user acceptance testing are often kept onshore to be able to better monitor quality.
Does anyone have other examples of SPM components which can be offshored easily?