grhmellis.substack.com/p/mentoring-...

A 3A session doesn't *have* to be Dev, Test, BA

Anyone with knowledge to drive out assumptions and clarify misunderstandings can participate.

Need designers, invite designers
Need Infra, invite infra
Need UX, invite UX
Need network, invite network

*Shared understanding* == goal, not box-ticking

If you've spent any time as a testing professional you will probably have heard these words:
"I’ve tested before"
grhmellis.substack.com/p/when-i-hea...

To hiring managers.
Change is what a skilled tester will attempt to effect, in attitudes, in communication, in levels of understanding, in mindset...
All under the umbrella of an increase in quality (whatever *quality* means in the context)
Change is not something to be feared

Things I get asked about at interview:

Automate all the things?
If I've used GIT/Bitbucket/Gitlab?
Deployment strategies?
Defect lifecycle?
Languages?
SDLC?

Things I *never get asked:

The role of a tester?
How I approach testing?
How I use models?
Exploratory testing?
Skilled testing?

You know you're on the road to agile testing nirvana when:

Someone observing a stand-up from the outside can't differentiate developers from testers.

You don't require a SM to facilitate.

Assistance is offered before assistance is requested.

Devs engage in testing to get the story to done.

Test automation does not ensure quality software.

Here's what does:
Quality Testers
Quality Developers
Quality BAs
Quality UX
Quality Scrum Masters
Quality Architects
Quality Infra Engineers
Quality Managers
Quality Stakeholders

A blog post.
About good behaviours.
Or not-so-good behaviours.
For QA.
Or Not.

grhmellis.substack.com/p/agile-gotc...