We're shifting left, and the next shift involves uncovering bad or missing behavior during the traditional testing phase.  Such testing is important and necessary, but is it enough?  We'll see.

In this episode, I will investigate the first step in shifting left, which is to detect product defects at the time they are sold and deployed but before they are in use by the customer, and therefore cannot impact them.

The next series of podcasts will examine the concept of shift left, which deals with the way we determine and remediate defects in our product.  This week I will start with the notions of detecting these defects when the product is being used.

This episode will introduce the concept of the "Shift Left" initiative in product development, and will set the stage for a series of podcasts that examine key aspects and implications of it. 

This episode is about the creation of acceptance tests, who should write them and how they should be structured, to get the maximum value from them.

This episode will tell you a story about a time when missing a critical stakeholder caused a company to make a potentially disastrous mistake in their business automation.

This episode will examine the difference between Requirements and the Expectations that drive them, and suggest ways that we can better serve our organization by focusing on the latter.

Information radiators are extremely useful to an agile organization.  But often there are such radiators that have been missed.  This episode will investigate this problem.

 How you measure the progress of an agile team will fundamentally effect how much value that team will produce, since that measurement will reflect that value. What should that measurement consist of?  That's the topic for this week. 

This week I will relate the notion of "changing change" to the test-driven development process, in two different senses.