Hi, -------- Original-Nachricht -------- > Von: Joost Andrae <[email protected]>
> > > > I think a good first step will be to do the communication between the > > I-Teams and the corresponding QA-Teams. > > A QA representative is always part of the iTeam. An iTeam should consist > at least of representatives of QA, documentation, development and user > experience. An iTeam is often used when features are planned and > developed. The great strength of iTeams is, that the team members cover the full development process. Work can be done in collaboration and with common understanding what to do an why (or why not to do something else). I'd be happy to be corrected here - but iTeams focus on new features. There is nothing like iTeams for bugfixing. That means - for bugfixing we have no common understanding why we fix what we fix - and why we don't fix what we do not fix. One of the first steps an iTeam does for a new fetaure is to collect the related issues and requirements. This is (or at least seems to be) missing for bugfixes. Martin Hollmichel once mentioned, that commented issue lists like http://wiki.services.openoffice.org/wiki/User:Lendo/Usability might be very helpfull. I agree here and would see such a focused and commented list as starting point for some focused bug fixing efforts. I'd really love to work on something like this - as long as it is somehow within my experience and developers would join. André -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
