> And here we disagree. Thou shalt have 1 team. Unless
> if you mean something else.
Why?
On our current project we have other teams that support the file
moves and the client database that our product uses, These other
people are in the same room but they're not part of our project
team. We're planning cross team feedback sesssions so that we
can improve how this works, but having a specific group of people
handling all the FTP and NDM stuff seems to be working.
If we had a team that owned all the GUIs, I think we could have great
success with it, especially since the GUIs for all the products share
so much code.
----------
Phlip had asked my why I think GUI testing is harder. My answer to
that is because it's very platform dependant and it runs on way too
many platforms. The model usually doesn't care about screen size,
resolution, readability, appearence, etc. It's supposed to give the
same answer regardless of the system that runs it. But GUIs often
have to adapt their behavior to the system and in the case of
branded GUIs, they have to adapt to the customer as well.
Web based GUIs have it worse. The functionality may not work on some
particular version of a web browser, or it may be manually disabled by
the user. It's hard to insure functionality when so many things can
go wrong..
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/
