6 Comments
User's avatar
Alex Pliutau's avatar

I like to think of Quality as a shared goal/responsibility. The line between Dev and QA is definitely blurring over time.

Mirek Stanek's avatar

I like when it's blurring, but often it goes in the opposite direction if not moderated.

Worst case - here you have 15 tickets waiting to be tested by QA engineer who is off for holidays and only he/she's capable of running and interpreting 1hr long test suite. Half joke, half true.

Michał Poczwardowski's avatar

I think it leads to Product Engineers, more T-shaped team players, and less focus on separate quality-oriented roles.

Great and comprehensive guide through the transformation that is happening. I like to remind: "quality is everyone’s work".

And it is a quality read — Thank you for the summary, Mirek.

Mirek Stanek's avatar

Thanks Michał! Quality is everyone's work - cannot agree more! :)

Zac Beckman's avatar

This is a great article Mirek. While it probably surprises plenty of “modern” engineers this old approach to QA/testing/quality is still very much a thing (just had a discovery call with a prospective customer… siloed, downstream test specialists). You explain the core problems, root causes, and introduce alternative solutions nicely. 👍

Mirek Stanek's avatar

Thanks Zac! Yeah, I agree - "classic approach" is still quite common, even in times of DevOps culture, DORA and others. And changing it was always a big challenge for me or for leaders who I worked with. That's why I wrote this piece - I want to support all of those who are having hard times and face self-doubts when doing such transformation.