Gary Hawkes | Comments
Team of 5 or fewer? TestRail now starts at $22/user. Test case management, defect integrations, reporting, and more.
I've established the principle to "politely" not wait to be invited by product and project people and start influencing them as soon as I can. For example, with product people I track when they create stories. I can either wait for the refinement sessions or I can as the leader review their stories searching for the "why", ambiguities, untestable AC's etc. I'm happy to brainstorm any ideas with you if it helps π
Hearing what you said about influencing developers, I think you're on the right path. Its no different to influencing outside engineering.
The advocation to those outside QA is tough. Its not a thing that gets solved, but it is possible to improve it but speaking their language. If I can help with advocating outside QA I will π
ππππ
Love the way you framed this as cognitive load is problem not always acknowledged as you indicate. But when you list the symptoms for overload, I can see a lot of testers (including me) going "hey, thats me!". Great work π
I love the reference to what a customer thinks is an issue is not always what testers think is an issue. I think thats why its so beneficial to get people into QA/QE from support, dev, product backgrounds as that really powers up the perspectives of what quality is.
I found this so inspiring and so interesting to listen to. Thank you Clare!
Welcome Imposter syndrome!!! π So privileged to be alongside people I consider to be legends of MoT but very proud to be a part π
Definitely! Its given me the MoTivation not only to keep pushing quality engineering improvements outside of my QE Team as we can only achieve so much on our own. We have to bring everyone with us on the journey.
I think thats a very real problem that we have in the community. It's great that we influence and help each other in this wonderful community but the next step is really to influence those outside it if we're going to make extra improvements to quality.
This is a very important article. We often make the mistake that our testing will find if there are resiliency issues if we have a production like environment, but consciously test resiliency. Thanks for this π
Gary Hawkes
Head of Engineering
He/Him
Head of Engineering who came from QE. Admirer of all humans (with a special affinity for testers). I love to bring out the best in people and help them grow. I have a very tactical view of delivery and love working to find the sweet spot so that processes are a balance between effort and value. Music nut.
Open To
Write
Mentor
Podcasting
CV Reviews