I've been thinking a lot about the collocation of agile development teams (or any development team for that matter). Some people argue that collocated team members are essential to successful software development while others argue that it doesn't make any difference. The more I think about it, and the more we operate with geographically dispersed teams, the more I'm starting to believe that collocation matters.
Currently, our team is spread out between Ft. Collins, CO, and Orlando and Jacksonville, FL. While things have not gone terribly wrong having dispersed team members, I have noticed a difference in communications. The difference is that in the Ft. Collins office (and I'm sure in Orlando and Jacksonville), there is a lot of informal communication that occurs amongst collocated team members. You know, the kind of discussions that happen spontaneously. When these happen, a lot of project information gets passed between team members that doesn't get transmitted to other remote team members. There is no malicious intent to not communicate. It's just that the impromptu discussions don't usually inspire anyone to dial in to a teleconference number and all that...precisely because they are impromptu.
On the flip side, the scheduled daily stand ups, planning meetings and reviews all happen when they're supposed to and everyone communicates on those calls. However, I have found that something is lacking on those calls as well. When a team is all together in a room, there is definitely a different dynamic than when there are "voices" on the phone. Body language plays a huge role in communications and tells a lot more than than what people are saying. However, what I find really absent is the sense of team and camaraderie that exists in a collocated team. There are many "physical" exercises that we used to do for planning meetings and retrospectives that have been lost due to collocation. I found those really useful and without them, I think our planning and retrospectives are less effective than they could be. Maybe we just need to adapt those exercises to be more amenable to the space between our team members.
All in all though, I think I would definitely be in the camp of folks who believe that collocation really does matter. It build a better sense of team, increases both verbal and non-verbal communications, and really fosters a more collaborative work environment.
Comments
Collocation
May 19, 2008 by Mike Cottmeyer (not verified), 1 year 6 weeks ago
Comment id: 1545
You have discussed the two extremes: having everyone collocated vs. everyone in totally different physical locations. How about having team members in the same office but separated by office walls or even floors of buildings? Is getting together periodically throughout the day enough?
I prefer the richness of having everyone in the same physical area, but would conceed it can work if team members frequently congregate and are willing to get up to talk. It just adds another barrier.
- Mike
One big room
May 20, 2008 by cspag, 1 year 6 weeks ago
Comment id: 1547
Actually that's a great point. Here in Ft. Collins, we're building a new office. Our team is currently in one big room and we decided in the new space to do the same thing. At a previous company, our team was all in different offices. It cut down a ton on informal communications. Here in our big room, we have a great, open, communications style that doesn't interfere with our work but actually enhances it. When we get into our new space later this month, we'll post some pictures of it. We designed it to be completely open and collaborative. No offices...just little Scrum rooms for planning/stand-ups, an escape pod (for private calls and ejects from the daily grind), a conference room, and a huge open development lab where we all sit...that's it. We'll keep you all updated on how it goes.
One very big room
May 20, 2008 by JurgenAppelo, 1 year 6 weeks ago
Comment id: 1548
I think I agree with Chris on this one. We have our main office in The Netherlands, and a subsidiary office in Ukraine. Communication is always a challenge, and I would advise against cross-border teams. When both offices are working on the same project, we try to split the project up in two tracks with two subteams, one in each location. Communication is needed between the leaders, but a daily cross-country standup wouldn't work that well.
And I happened to blog recently about our *very* big room, in Tear Down Your Cubicle Walls
Collocation
May 21, 2008 by Agile Vlad (not verified), 1 year 6 weeks ago
Comment id: 1549
I am very much interested in this topic of collocation. The reason for my interest is that in a few months I will be involved in an Agile development project where the technician and the business analyst will be located in India while the project manager and product manager (myself) are located in Orlando. I am very worried as to how Agile can be applied when the two key resources (who are not quite that familiar with our products) are 9 hours away. Prior to the kick off we are planning on writting some procedural documents (which I believe is an anti-Agile step) and then on-going we will hold our daily 'meeting' by phone. Being new to Agile in conjunction with the offshore environment I worry that about the output from the project. Any suggestions would be appreciated.
What is being showcased here
June 4, 2008 by Anonymous, 1 year 4 weeks ago
Comment id: 1565
What is being showcased here is the management and coordination of collocated teams that are seaparated geographically.
I find it entirely unsurprising that one finds that informal communication within each collocated team is easier than between teams. Each team becoms a clique because of the barrier of distance that is maintained between collocated teams. A type of rigid order is maintained by managing several georgraphically dispersed collocated teams.
This is not a case for collocation - it points, in fact, to why collocation is a growing impracticality. If one managed a group of geographically dispersed individuals, one might have a case for collocation.
Owen.
Post new comment