“Excuse me, there is some lead in my code!”
I write this post as I crack open the lid of a delicious maple yogurt. Wait! Wallaby’s, “Made In Australia”….Phew, no lead here.
Toys, toothpaste, tires, pet food…I’ve really lost count. Although, I am comfortably numb to the news, I still do feed my paranoia by reading the “Made In” labels.
But compromising quality via outsourced development should not really be a news flash…especially for those of us in the IT industry. The last statistic I heard was a whopping 74% failure rate on outsourced IT projects. WOW! There is no quality standard in the world that does not warrant that as a recall.
I’m not on a rant against Outsourcing. Who am I kidding, the basic foundation of developed nations has been Capitalism. I’m roughly saving $40 an hour per developer here…so yes, I’m going to send this puppy out to India or China or wherever. But how can we ensure that our projects fall into the mere 26% side of the fence? I manage an outsourced outfit in India and here are some things I’ve learnt along the way:
1. Code Quality: This is a big misconception. To clear the air on this, there is nothing wrong with the quality of code being written by your outsourced outfit. If you run the same project here, you will have the same range of skills in your developers. There will be some superstars and some mediocre ones.
2. Communication: This is the kicker. The biggest gripe is that outsourced developers do not think outside the box. Well, without access to constant meetings, group discussions and that white board hanging in your office, it is hard for them to really see the big picture. This coupled with, what I like to call, the potatoe-potahto syndrome, you’re looking at the biggest reason why projects fail. The lack of communication feeds into prolonged decision cycles that come back to bite you. For example, it takes you longer to identify your mediocre performers or even worse, it takes you even a longer time to identify your superstars. There isn’t enough Skype, IM, email or virtual conferencing that can replace sitting across a table and having a discussion.
3. Testing Methodology: We’ve been around outsourcing long enough to realize why some of these projects fail. I know the “cost-savings” carrot is tempting but you are paying roughly $40/hr less per developer. Invest some of that into a comprehensive testing methodology. I cannot stress this enough. Do not outsource if you don’t have a test plan that includes a detailed regression suite. Discuss testing up front in your contract, most companies will welcome the idea of running their deliverables against your testing suite to ensure quality (and not lead).
4. Meet your team: Plan to head out to your outsourcing destination a couple of times during the course of your project. Invest some time and effort in this relationship so that you get to know your team. How long have they worked with the company? What projects have they completed? It will allow you to put faces to the voices you hear on your calls. If nothing else, this will also allow you to cross ‘Visit exotic/enchanting land’ off your list.
Lastly, technology is on your side. It is making it easier to tighten your lines of communication with your team. Feel free to drop in a comment with your outsourcing experience. Mmmm…that was some pretty good yogurt.
Sphere: Related Content