Mechtilde wrote:
Joost Andrae schrieb:
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.
Should developers be 'bothered' with QA? - I sure hope so - they are the
major contributors to a quality product.
Surely there are steps that the developers use specifically for QA
purposes - (in general)
They might hold code reviews - do they? if they say they do, does a QA
rep verify?
They might produce unit tests for new or changed sections of code - do
they? Does a QA rep verify?
Do developers have any responsibility to update Specification documents
should any 'minor' changes occur to functionality during actual
implementation? Do they? Does QA verify this?
OK - Should they be 'bothered' with the intake process for bug reports?
Not if it can be helped
- although there will, IME, always be some issues that will/can not be
confirmed until the developer actually gets involved.
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
