If QA and developers come from different tracks (eg, devs from CS, QA from problem domain [[ eg. BSc/CS vs BComm/Acct]] ), then QA looks at the things that "weren't in the story requirements" but matter for the product.

If it's a collective "we learned from this", that's good.

If it's seriously and organizationally adversarial, that's bad.