Timezone's do come into play, but they're not much of a problem either.
From my experience, most people do not know what to do during this first meeting. In most cases, it is their problem.
In my case, I believe in establishing a Tangible Plan (or Overview) that everyone can unified with. It is about getting everyone to commit to the big picture (the goal, its specific and to each other).
The question is getting everyone to work through specifics of the grand goal.
From my experience, not everyone are willing to be teamplayers. During the 1st meeting, it is about seeing who wants to play teamball and who wants to play "Lone Ranger".
Team collaboration is not about software, It is about a process of getting people to collaborate. 100% team management psychology. ... Remember losers promises while winners commit. Each of your success will be about getting people to commit. .... Thank you very much for all responses.
There are tools to replicate so many things- You can use phone calls, and shared whiteboards.. But they are half-way measures- They don't let you work against each other, or argue back and forth easily, making changes to a design..
I've worked with friends in other states before, and at times, we'd struggle for a design problem for several weeks, before I flew down and we hashed it out in one all-night session of pizza and caffeine.
If it's pure code to spec, perhaps you'll be able to get away without out, but even then, working in the same place ensures that you stay friends, and that you can talk over a design while going out for lunch.
If at all possible, I strongly recommend working in the same place.
For more nebulous, complex projects where decisions frequently come down to judgment calls, it doesn't work so well. For instance, startup founders need to work together, literally elbow-to-elbow to give the best chance of success.
