No matter what kinds of products and services an organization offers, there are terms that are specific to them.  These terms must be carefully defined and consistently updated as things change.  This podcast is all about creating such a set of definitions.

This episode will introduce a useful framework for organizing requirements as the are identified.  Such organization can be very helpful in collaboration and validation throughout an agile process.

Various technologies provide us with the concept of "inheritance".  What should this used for, ideally, in an agile development environment?  This episode addresses this question in a way that should be interesting to non-technical people as well as developers and testers.

The way we create business automation in the modern environment has been influenced by the strength of various innovations that have preceded us.  This week I'll introduce this idea, and then over the next few episodes will examine some of the implications and opportunities.

Last week I pointed out that Test-Driven Development, even though it is named as it is, is not a testing activity but rather the creation of an executable specification.  So how does this change how they are written?  That's the subject of this episode.

This week I wrap up my answer to the question of three weeks ago and is so going point out, perhaps, the most important aspect of TDD, and how to make sure it delivers all the value it is capable of.

Part two of my answer to the question posted two weeks ago.  There is one more to come, next week.  It may be the most crucial of these answers.

This is my first answer to the question posed last week.  There will be two more in future weeks.

Teaching Test-Driven Development, either in the unit testing form for developers or the acceptance testing that anyone can learn and do, this questions almost always arises at some point.  It's actually an excellent question and can yield a lot of value in answering it.  This episode will explain why.

How does this principle apply to the notion of an agile process?  I think it fundamentally changes the way we create automation, and the value that automation ultimately provides.  This week I explain why.