When TDD Doesn't Matter

It is good to see a respected teacher and theorist of the agile movement making the point that good judgement is preferred over dogmatic adherence to a set of principles.

Apparently this was posted a year ago, which is kind of frustrating for me because it's exactly the sort of analysis I've been hoping for since I was first introduced to TDD.

I'm not really comfortable with the space that he's constructing, but at the very least it's a space. Like if you had a bunch of requirements you might be able to actually determine if TDD makes sense via somewhat objective criteria instead of via whomever makes the best appeal to pathos.

What I actually want (and have been working on creating) is some sort of problem space[1] that allows you to analyze any given problem such that you can determine whether TDD will benefit or harm the development and verification of a solution.

[1] - It looks suspiciously like a general purpose problem space is kind of a ridiculous thing to try and define mathematically. I've had to set my sights a bit lower than my initial goal, but the ultimate dream would be objective analysis based off of high level discussion of what the stake holders want.