Hi Mechtilde,
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.
Christian (cloph) wrote some good points in his mail. I will citate. Developers should not be bothered with QA. The developers should .. be interested in QA. It should be clear what QA-members can ... do to verify the changes. In the cws and in future to prevent regressions. </citate>
+1
One goal should be to do these things also in the other teams. this will be a great step for the collabaration.
To work together with the application related QA teams is a first step to be involved into working on child workspaces. On the other hand people who contribute by confirming unconfirmed issues is another important thing because this disburdens developers to spend more time on reproducing such issues. I believe you already helped the DBA project in such a way :)
Joost --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
