How do you advocate for quality beyond developers?

The struggle of breaking the stereotype that testing brings quality is one of the biggest challenges I have faced. Another challenge for me is convincing the team in priortizing test execution over test cases. Documentation are good but minimum documentation can help in saving time for better test strategy, test design, etc.

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 😁

Hiya! What a great topic of conversation. An idea I would put forward is to talk about business risk - I've found if you frame the problem in the right way then it can help advocate for whatever you're after - that might be more time, exploring a quality criteria or something else entirely. Also good things to do are communities of practice, knowledge share sessions and more to spread the good word of what's going on. ALso fun things like "quality newsletter" to share what's been going on.

(totally get your comment, louise, of being spread too thin at times with being a lead. I've found being pragmatic and choosing the items to focus on works well. Not looking for perfection but progress day by day on the right things)

Here is a good reference article from the MoTaverse: https://www.ministryoftesting.com/articles/the-quality-and-testing-information-model