The World is FlatOutsourcing and offshoring is a mainstream business practice in today's economy. Companies reach to outsourcing and offshoring to find cost savings, find expertise outside of their core business, and provide a follow-the-sun workforce. Blended costs for outsourced companies is lower than a purely domestic team by leveraging lower resource costs in other countries like India, Brazil, and the Philippines. Things are no exception where I work.The StoryI have decided to document the transformation of my department into a global organization that embraces outsourcing and offshoring. I am also hoping that those that went through this process with me who read my blog will provide comments of their own, and keep me honest.In The Beginning...In the middle of 2007, my department decided to globalize our work force and find an outsourcing vendor. Other departments had experience with Satyam, Intellogroup, and Accenture. We decided to start with Satyam, as we heard the most positive reviews of their performance.We put together a brief meeting and walked through our objectives of blending a global team to drive down costs. Over the course of the next 4 months, we focused our interviewing skills at a half dozen candidates for our first outsourced team member. The first candidate seemed to be a good fit for our team, and so we made short order in making an offer and getting a contract signed. But, in the 24 hours between interview and offer, the candidate mysteriously became unavailable. Interview followed interview, and all the candidates seemed to fall short of our expectations. It reached a point where the resumes stopped coming in. With only two months left in the year, we resolved ourselves to try another outsourcing company. After reaching out to Intelligroup, we held a brief meeting with them. The meeting turned into an ad-hoc interview for one of the attendees. He seemed to be strong in .Net technologies, have a solid background in software architecture, knew enough about web technologies, and had project management experience. We made an offer, signed a contract, and on December 3, 2007, we had officially taken the plunge into offshore outsourcing and hired our onshore liaison. Next...My next post will talk about how we expanded the team to include our first offshore resources located in India, how we integrated them into the team, and some of the bumps and bruises we experienced along the way. |
Saturday, January 24, 2009
Outsourcing 101 - Introduction
Posted by
Brian Whaley
at
1/24/2009 09:50:00 PM
Labels: Offshoring, Outsourcing
Subscribe to:
Post Comments (Atom)
























6 comments:
looking for next post
"bumps and bruises"? We've been knocked out into a coma! Let's be honest here. We're never going to recover from the horrendous decision of going with Intelligroup. It was theft in broad daylight, with every BMS personnel responsible for managing them, supporting their cause against BMS interests. I still wonder what the BMS managers had to gain from keeping them around, despite being repeatedly informed that the very same action would have dire consequences. But I guess they all had their own self interests in mind - report to their managers what they want to hear, in the hope of receiving a promotion/raise/bonus in return. Corporate slimeballs!
Rule #1: To be management, you HAVE to be spineless.
The term "cost savings" has been loosely used by every so-called "outsourcing expert" in the industry and has been blindly considered a major benefit to the strategy of outsourcing/offshoring.
Since you have first hand experience, I'd be interested to know how the strategy affected you from a cost savings perspective.
Hope to read more about it in your next post.
It's not possible to determine the cost savings at the team level. There are many facets to the cost of maintaining an IT organization, and the direct cost of the resources is only one. It's possible that the direct cost could increase, while overhead costs decrease. It's also possible that the number of projects could decrease if the outsourcing does either and much better or much worse job - guess which is more likely :) More importantly, I don't think anyone can calculate the real costs of offshoring. Even if it saved the company money, what happens when the company's customer base/sales decreases when Americans lose jobs and can't buy their products? These offshoring decisions are as well thought out as Obama's stimulus plans. Only chaos theory can predict the results. Except that I am sure that the results will not be good overall.
Rule #2 - to be a developer, you have to be able to complain without considering your own part in the problem/solution. :)
Rule #3 - Too many cooks spoil the broth.
You REPLACE the bad ones (in this case all of them) with new resources. You don't bring on new resources and retain all the bad ones too. The goal was to save costs, or was it the opposite?
Post a Comment