- Build in Asia
- Design/Review in Europe
- Test in South-America
- Every day.
- Every 24hrs.
Well, I am starting to believe that this is a great way to speed up the process but a small devil in me asks this stupid question:
What if at some point you need to talk with the people from the previous time zone?
Suppose you’ve found something that you don’t understand in their specification or in their code. Or it seems to be wrong. You want to discuss the issue with your offshore colleagues but their working day is over and they went home. Now you have to wait until tomorrow.
I think that the time difference is a huge problem in international communication. Following the sun seems to be a good idea but it is not a panacea. You have to develop a strong process to ensure efficient overseas communication and without disturbing the personal life of your staff.
There is one more great article Bas wrote on offshore software development and I find it very useful. I highly recommend to you 25 Rock Solid Tips to Supervise Offshore Development. Read it and follow those tips – they are really helpful.
If you like the posts in this blog or you are interested in the discussed topics, please, subscribe to the RSS feed to guarantee yourself that you won’t miss an interesting post. You can do it in an RSS reader or by Email.