Offshore-Onshore
Models
​
The Software development lifecycle is a balancing act between quality, time and cost. The good, fast, cheap triangle where you can only have two of the three options. Good and fast will not be cheap, good and cheap will not be fast, fast and cheap will not be good. As time and quality are usually the least negotiable the focus has become cost effective delivery.
​
This drive has led either to a reduction in the size of the testing teams, with related risks to the quality of testing or, more often the move to offshore testing; acquiring testers at significantly lower costs.
​
That solution has not proved as effective as had been forecast. The issues of offshoring are well known. Offshoring reduces control of projects through a lack of visibility of resources and communication issues. Problems of time difference and lack of knowledge retention as resources move off projects are constant. The high turn-around of staff in the emerging markets as well as regulatory issues around data security are also manifest.
​
Delphi Services has developed a new resourcing model that gives IT Programme Managers the means to reduce costs without compromising quality.
Model 20-50-30™ is designed to address:
-
A reduction in the cost of delivery of your projects by efficiently using resources only when they are required
-
Preserving project and application knowledge so that delivery is not slowed by changes (ramp up/ramp down) to resources
-
Retaining the best of offshore-onshore or a mix of each, whichever meets your needs
-
Greater control. On-site Test Management Consultants manage resource allocation to allow for their retention by Delphi Services after the project completes.
-
Knowledgebase control will give you peace of mind for any future Business/IT change. Resources are dedicated to perform Static Testing, System Documentation and Knowledge Transfer with a focus on handing systems over to the BAU support teams.
​
This results in cost savings against a typical onshore project testing life-cycle. No costs are incurred when resources are not being utilised and you have greater visibility of resources and activities being performed.