In part one of my series on Lean, I examine the concept of eliminating Muda, or waste.  I will show this in the context of manufacturing and software development, to compare and contrast the two.

This will be the first in a series on Lean Manufacturing and Lean Software Development, which is a major enabled of agile processes.

I conclude this series my summarizing my current views on AI and it's increasing role in the development of business automation.

In the episode I will reflect on what I have learned by interacting with the management of the corporations I teach for, regarding the thoughts, concerns, and plans around AI.

People fear being replaced by AI.  Should they?  This episode will examine why this concern may not be as founded as people think, at least when it comes to industries I am familiar with.

This episode will use software development as an example of how AI can be used to make the product development process more efficient, and less wasteful.  This is an example which I believe could apply to any kind of product.

This podcast will kick off a series of episodes on AI, and my personal view of it.

This week I will wrap up the notion of Shift Left, and introduce the next topic for this podcast.

The final "shift left" I will examine is the detection of defects during the planning process, specifically requirements analysis.  It represents one of the most important and also most difficult challenges that face us when developing pro...

In our continuing effort to shift the detection of defects and other mistakes to earlier and earlier phases in our development process, this week I'll discuss the role that design can play.

This week we will examine how defects can be detected and sometimes even prevented during the implementation of the product as analyzed and designed in the previous phases.

We're shifting left again, to the integration phase that precedes traditional testing.  What defects can and should ideally be detected at this point, and how can we accomplish this?  That's what this episode with examine.

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 u...

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.

Part three of this series on changing our relationship to change deals with the concept of encapsulating variation in business automation.  This is expressed in non-technical language and should be useful to those that lead product develop...

This episode will explore another aspect of the agile design process, from a non-technical point of view.

If we are to be successfully agile, we must embrace unpredictable change.  But to do that, we have to fundamentally alter our relationship to change itself.  This is part one of a series about how I recommend teams accomplish this.