honey-badger

Quality Acceleration is brilliant! I love it.

>In this case, I wouldn't say you absolutely need a full quality team, but having some folks whose primary focus is testing and test automation to help skill up your dev teams sounds reasonable.

This is what we have at our current team, as I have described in a comment above, and it has worked very well for us.

A valuable perspective, and brilliantly articulated. The process of software creation and its quality assurance is so intricately intertwined due to the nature of software itself, that it is near impossible to neatly divide labour.

Great perspective. Now if you were to take the place of Management and tell this exact story, how would it sound?

Not necessarily. In all likelihood, the market punishes bad software quality, but with a longer and more complicated feedback loop.

It is easy to see the increased traction due to building new features. It is difficult to understand the slow, grinding attrition that happens due to bad quality.

Your comment is super helpful! A few months back, we went from scenario 2 to scenario 1, and I can attest to it being substantially better.

Does the QA team comprise domain experts? What is your domain?