> I'd expect problems on the interface between any two teams, especially if
> it was an active interface, subject to a lot of learning and changing. And
> I'd expect that the GUI / model interface would have a lot of that.
I'd expect initial problems, but if two xp/agile teams couldn't find ways to work
together,
communicate, provide freedback to each other, etc. then I would be asking a lot of
questions.
Perhaps one GUI member could pair with on project member for scoping out the tests or
for most of or perhaps the entire card. Perhaps a project member could serve as a
"model
customer" or "model consultant". Perhaps a GUI member could serve as a "GUI interface
consultant", so the model people know what needs to be passed across the layer.
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.
But I'm sure two agile teams could find their own perfect solutions. If not, I'd
seriously
start looking at why.
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/
