3 ms·
> QA being too close (in org chart terms) to production. Can you explain in a bit more detail what this means in practice? I haven't worked with a QA team befo
by dmix 8y ago
> QA being too close (in org chart terms) to production.
Can you explain in a bit more detail what this means in practice? I haven't worked with a QA team before and I'm curious.
Does it just mean the QA checks happen well after the specific work was being done, making it harder to go back and fix things (due to mental context switching, tooling, etc)? Or just too many last-minute fixes?
- karambahh 8y agoMy positive experiences with QA were always when the QA team was strictly separated from the production team. Ideally, no friendship whatsoever. Doing QA is hard. Bouncing issues & QA reports between teams is hard. Bouncing issues between people that know each others too well or have a common manager leads to all sorts of issues. In this specific instance, it could be as simple as the manager trying to balance things between teams and thus letting things slip past the due date or with sub-par quality. My worst experience was when a married couple worked together on a project I was involved with: one on the sw team and the other in QA. Working together is hard, working on "antagonistic" teams is hell