Several projects I am working on within my organisation are adopting SAFe in order to build software solutions, so I thought I should perform some SAFe testing!
With my Agile background, I am able to provide a lot of value in helping the teams follow an iterative development lifecycle (predominantly Scrum), but I have little experience of processes outside of the development teams themselves.
I also seem to struggle to get my message across to senior stakeholders within my organisation who are new to Agile & SAFe.
This is the 3rd in a series of posts where I dig into the Agile Testing Quadrants after a coaching session I had with James Bach. This post focuses on the left & right sides of the matrix; the columns.
In our team, I noticed the way we were speaking & the words we were using sounded as if we were trying to influence others of our thoughts & ideas.
Sometimes this made me feel uncomfortable, especially when the recipient didn’t realise they were being influenced (or didn’t know what to do about it) & consequently their opinion was altered as a result of the language used, not merely the content.
James Bach helped me to break down the quadrants in order to get a deeper understanding of what each quadrant meant. It was during this conversation I realised I had a very shallow understanding of the model & I was effectively diluting (& even twisting?!) the message the quadrants were trying to get across.
At my current client, we’re being coached in the Hexagonal Architecture pattern.
Admittedly, the primary focus is towards the Programmers, but the change in the development strategy has an impact on us Testers so we get a seat a table.
What is this change in the development strategy which will impact us Testers? The pattern considers integration tests as brittle & unneccessarily linking the business logic to the implementation. As such, with this pattern, you want as few integration tests as possible. So the question is:
As a Tester, how confident am I that the removal of (automated) integration tests have not decreased the stability of the code?
In this 3 part series, I hope to learn more about hexagonal architecture, what it does for the teams test strategy & what the impact is for Testers.
As you may be aware, I follow certain testing folks in the Context Driven community. Some of these Testers are members of the Miagi-Do School of Software Testing.
I have read & heard about this Miagi-Do school for a while – I knew I had to complete a challenge to ‘gain entry’ in order to prove my worth, but I had never got round to following up on how I go about receiving a challenge.