Hi, Ken. Your lines are a little longer than standard, so I've
re-wrapped them.
On Sun, 2004-10-24 at 19:44, Ken Boucher wrote:
> There's no reason all the teams can't still be in the same room and
> if they couldn't there's no reason someone couldn't visit for a day
> or a week or an iteration. That might prove very educational to
> everyone.
I've never tried it on a fully agile project, but I have tried it in a
large, multi-team environment where my team was adopting agile
practices. Ron is correct; you get problems at the interface boundaries
unless people are sitting together.
The day-a-week thing sounds nice in theory, but in practice my
experience is pretty awful. If you don't formally schedule those people,
then there's resource contention and stress on the part of the resources
as they try to make everybody happy. If you do schedule them, then
they're never available at the right times and in the right amounts,
substantially reducing agility. There may be some way to fix this so
it's nearly as good as having the person in the room, but the solution
wasn't obvious to us.
Personally, my preference is that if everybody can't sit together, you
slice things vertically rather than horizontally. That is, each team has
all the people you need to get something done, so that you can make
changes at any layer of the code. There of course need to be mechanisms
so the people who focus on a layer can coordinate, but I think there are
ways to do that without the bottlenecking that "layer = team" yields.
William
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
