Part 2 of my analogy on product quality.

Part of the Agile approach, as well as the tenets of Lean, say to "build quality in."  This seems wise, but what specifically is meant by "quality"?  Also, how can we know if we have imbued our product with enough of the required qualities to make it releasable?  The next three episodes will examine the notion of quality using a hopefully familiar analogy.

TDD can help you to improve your product design for many reasons.  One of them is that it is difficult, if not impossible to write a good test for a bad design.  But what is a good test?  How would we know if it's good in the right sense?  That's what this episode will explain.

This episode relates a story that an ex-student and current colleague of mine related to me over lunch.  I felt it was an extremely revealing and useful example of how requirements are misunderstood, the disasters than can result, and what to do about this.

Scenarios, like requirements, can often be too large to work with effectively.  In this episode we'll examine why this is a problem, and some example of how we can deal with it.

The world has changed, and so has the technology we use to automate it.  But a lot of the traditions that guide our efforts to control automation projects are based on the realities that existed in the past.  Agile is a response to this, and this episode is all about why, and how this is so.

When collaborating with others, sometimes you will encounter reticence to ask or answer important questions.  There are a number of reasons for this, but in this episode I will outline an approach I take to counter this, one which has served me well in multiple occasions.

When creating something new of value, one must always consider the context within which it will operate.  Part of this is determining what, if anything, in the existing business processes will be effected by the new work.  Failing to take this into account can have serious consequences, as this episode will demonstrate.

Analysis is a fundamental part of system's development.  It is also one of the most difficult things to do right, and since everything that follows is based on it we need multiple skills to do it correctly.  Commonality-Variability Analysis, as suggested in the work of James O. Coplien, is a remarkably powerful approach to conducting requirements analysis.

Test-Driven Development (TDD) is not really a testing activity per-se, but an analysis process that drives product design.  That said, although it does not eliminate the need for after-development testing (QA/QC), it does contribute to that process.  This episode will show why this is.