Lessons Learned about Starting a Development Group in India, Part 1


all of his time reading books on programming in C++ and reading code. He had never written any code.

I called the project lead in India who told me that he had hired three experienced people and one trainee. The person I had in the US was one of the experienced people. At that point, I became extremely concerned.

I shifted gears with the person in the States and assigned him some QA work to do, which he excelled at. Then I cancelled the second person's trip-he was the trainee. By the time the three months were up, all of the people remaining in India had left the company, including the team leader. The person returning to India was reassigned to the electrical engineering group. Eventually the prototype system in India was scrapped after it was discovered that it didn't work at all, and none of our staff could figure out how to fix it.

In the next installment, find out what lessons Peter's company learned from this experience and how it affected the company's second attempt at outsourcing to an offshore team.

In part two, Peter will explain what he did differently the second time.

Click Here to Read Lessons Learned About Starting a Development Group in India– Part 2  and Part 3 .

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!