Requirements gathering & refinement gets little love in the testing matrix. I want these activities to get more representation in the matrix, so using the language I already there I’ve coined a term “Stakeholder Tests”
And finally we come to the end of this exploration into the Testing Matrix, so what have I learned?
This post outlines some examples of how I’m currently using our current incarnation of the test matrix
Whilst digging into the test matrix / agile quadrants, I’ve come across several different representations of the model.
This post is a collection of some of those representations (in chronological order as far as I can tell).
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.
This is the first post attempting to document some of the conversation James Bach & I had whilst trying to determine what my understanding of the Agile test quadrants actually was.
This post is a WIP as I’m sure I’ll be updating it as I walk through each of the quadrants & work with some of the different ideas & terminology we discussed.
I’m a fan of the (Agile) Testing Quadrants, first described by Brian Marick back in 2003 as a matrix & later popularised by Lisa Crispin & Janet Gregory.
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.