I think "offshore" is another such term. It implies for me a kind of political stratification. Here, on this/our/normal shore, we make important, big decisions. Then we send those big decisions to people with less power/salary to implement. I prefer "multi-site". We make some kinds of decisions here, other kinds there. Or we make decisions here at certain times and there at other times. Or whatever. I expect XP can be used very effectively for multi-site development. I assume that the key is, as Josh said, system-level tests (a la FIT). I expect XP would really suck for offshore development, since the basic political gestures of XP and offshore development are precisely opposite.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Vincent Massol said on "Topic: Agile Methodologies in Offshore Development"
There are a lot of difficult challenges in doing this. The main one, is that, obviously, that both teams are remote. It is difficult to speak together, and so we need to find ways to compensate for that. You know, the agile movement, enforces a lot of communication, it wants to do a lot of communication between teams, so that they actually can transfer knowledge constantly between them. And the challenge is to be able to do this when you can�t speak with the other person. So that�s one core challenge. The other one is more for our customers. When they want to get help from offshore companies, they want to do so without losing the knowledge of their information system, or the architecture part and also the development part of it. So, they want to retain that knowledge, and at the same time be able to benefit from the fact that there are other persons that can help them build the software. So, that�s the other challenge. And we�re trying to address these two challenges by doing this in an agile way.
Joined: Jul 11, 2001
"And the challenge is to be able to do this when you can�t speak with the other person." Or perhaps the challenge is to make it possible to speak to each other even when being on different sites?
Originally posted by Lasse Koskela: If I remember correctly (can't be bothered to re-read the interview), they did use one particular tool extensively. Telephone, was it...
Yes, telephone is one of the tools you could use. With the high speed internet connections we do have today I wonder wether you could have even more "togetherness". Think of what could be done with webcams, for example...
Eclipse had some plug-in for pair programming. I think it was developed offshore. With the right look-and-feel looking over a shoulder has a whole new meaning - yeah web cams would work just remembering to turn it off at intervals would be a chore - don't want to be caught playing on the computer by Big Chiefs. Not that anyone would do that, of course. But there must be security implications.... [ January 16, 2004: Message edited by: HS Thomas ]