This is the 2nd in a series of posts drawing out the ideas in Dave Snowden’s State Of The Net 2013 Keynote “How Not to Manage Complexity” in an attempt to get my head around complexity. Today I look at…
This is the 1st in a series of posts drawing out the ideas in Dave Snowden’s State Of The Net 2013 Keynote “How Not to Manage Complexity” in an attempt to get my head around complexity. Today I look at…
I watched a great presentation from Dave Snowden called “How Not To Manage Complexity” (State OF The Net 2013).
In this series of posts, I take quotes & ideas from the talk I found memorable & attempt to apply them to the world of software development. I do this in order to share & hopefully improve my ideas on complexity.
I’m not the first to say this, but my experience is showing me that people are still being forgotten in “Agile” adoption.
Invariably in software development, we are writing software to create products to help solve other people’s problems. People writing software for people. The tools we use to write & distribute that software augment the work we do, not replace it.
From the 2nd of April 2015 I am available to help with testing challenges. How can I help you?
This post is my attempt to improve my understanding of Cynefin & how it can be applied to software testing.
I had a problem. I wanted to embed multiple hyperlinks into a single image. My solution turned out to be image mapping.
I’m writing this post to help cement my understanding & share the discovery I had in case any one else finds a use for image mapping. The first thought I had was those of you who dabble in sketch noting…
Like any respective course attendee, I feel I should write about my experience, but without giving too much away…
I need to fill in some gaps regarding the quote taken from my recent talk at the BBC Develop 2014 conference.
I told a story of when I was asked the question:
“Why wasn’t that bug found in test?”
“Why did you put that bug in the code?”
I have to confess, this isn’t my default response to that question, but as always there’s a story behind the story…
Continue reading “Why was that bug put in code?”
Cucumber is not a testing tool. I know this.
One of the big noises I make about Cucumber is that it is not a testing tool, it is a tool to help collaboration, discussion of requirements & generate living documentation.
How then did I fall into the trap of trying to use Cucumber as an automated testing tool?
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
When I was reading through “Domain Driven Design Quickly” (published on InfoQ) I had several aha moments as I linked the material I was reading to the “Heuristic Test Strategy Model” (HTSM) from James Bach which I work with daily.
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).
I have just finished some fantastic Ruby & Cucumber training with the most affable Chris Parsons.
There are some definite lessons to be learned (other than writing Cukes with Ruby)…
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.
(Parental Advisory – explicit content)
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.