2 added 3 characters in body
source | link

Neither, QA should be part of the Agile delivery teams. I mean that the QA/Testers should sit with the developers and help them deliver tested features during their iterations.

Read some Agile testing books: http://agiletester.ca/, cause it sounds like the developer is practising Agile, but the testing is falling back on more traditional methods, like clustering teams.

BothBut if need to pick one out of two evils it would be a product specific teams, because as a tester you need to learn the product domain specifics risks and such.

Neither, QA should be part of the Agile delivery teams. I mean that the QA/Testers should sit with the developers and help them deliver tested features during their iterations.

Read some Agile testing books: http://agiletester.ca/, cause it sounds like the developer is practising Agile, but the testing is falling back on more traditional methods, like clustering teams.

Both if need to pick out of two evils it would be a product specific teams, because as a tester you need to learn the product domain specifics risks and such.

Neither, QA should be part of the Agile delivery teams. I mean that the QA/Testers should sit with the developers and help them deliver tested features during their iterations.

Read some Agile testing books: http://agiletester.ca/, cause it sounds like the developer is practising Agile, but the testing is falling back on more traditional methods, like clustering teams.

But if need to pick one out of two evils it would be a product specific teams, because as a tester you need to learn the product domain specifics risks and such.

1
source | link

Neither, QA should be part of the Agile delivery teams. I mean that the QA/Testers should sit with the developers and help them deliver tested features during their iterations.

Read some Agile testing books: http://agiletester.ca/, cause it sounds like the developer is practising Agile, but the testing is falling back on more traditional methods, like clustering teams.

Both if need to pick out of two evils it would be a product specific teams, because as a tester you need to learn the product domain specifics risks and such.