|
|
|
|
|
|
by notmyfuture
1809 days ago
|
|
|
Yeah - in my experience 6-10 people per team is typical, often with one of them being dedicated QA. Having this, plus a separate central QA team is one way to address the pitfalls of embedded QA I was pointing out - they can cover for time away for team QA, or act as bench capacity. |
|
|
That's difficult to hear, repeatedly, from the same person. And I've seen a lot of developers not react well to the underlying discomfort.
When it's an external team, at arm's length, that relationship can get pretty bad.
At least when it's someone on your team, then you have non-QA moments and interactions to help balance out the unfortunate bug truth.
And the end result is faster, more thorough, more productive bidirectional communication between QA and coders.