Can the Quality Assistance Model Accelerate Your Software Delivery and Improve Quality?

Discover the impact of the Quality Assistance Model in our latest article, “Better Software, Faster: A Tester’s Report On The Quality Assistance Model.” written by @nat. This article explores how a tech company revolutionised its testing approach, shifting from traditional quality assurance to a model where every team member contributes to software quality and testing.

Learn how this change not only accelerated software delivery but also significantly improved product quality without the need for additional testers. Ideal for anyone looking to enhance team efficiency, this article is a valuable resource for understanding how to implement such a model effectively.

Check out the article for insights and practical examples, and share your thoughts with us!

5 Likes

Super interesting. I think I am unknowingly in phase one at the moment and yup, it is hard.

Need to find time to watch that video.

2 Likes

Honestly I have a hard time reading further after reading the part about this model originating with Atlassian–as a heavy user of their products I think I’m far from the only one to take issues with their product quality so I don’t have much respect for their expertise on that topic.

(I’ll try to post a more productive reply in a couple days when I have a window to read the rest of the article, but I do feel like we need to do more vetting of the outcomes of those in our industry advocating for reducing or removing the dedicated tester role. If you’re promoting a model but your quality stinks, maybe we shouldn’t take your model very seriously. Also, this is nothing against the blog author, simply an observation seeing Atlassian mentioned as the origin of a model.)

I finally watched the video (https://youtu.be/yRP29wFqu20?si=faKIE-hbaEyHAf8P). Strangely enough a coworker mentioned this to me as well.

Some thoughts

I think this is Major. Management thinks it’s quick and easy but it’s not.

  • the presenter won’t try this again with a new team. Basically mentioned it worked for one team at that one time.

This is interesting so this presentation really should not be taken as a blueprint.

  • Experiment. Try new things.

Yeah I agree.

Overall quite interesting!!

2 Likes

We are going through a similar transformation in our company. Based on our experience the success of this approach really depends on:

  1. The leadership qualities of a particular QA in the team
  2. The buy-in from the engineering manager and/or senior developers in the team.

In many teams the transformation has been great while in a couple of teams it has been challenging.

3 Likes

I would love to hear about the challenges.

I think having success due to the people (QA and Dev) makes this model tricky to implement across different teams.

1 Like