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 development initiatives.

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.

The fourth point of the Agile Manifesto, that we value responding to change over following a plan, has massive implications for the way agile teams are managed.  This podcast will introduce the issues that result, and will lead to the next series.

This week I will answer the questions raised over the last four Agile Tips, each a different aspect of the Agile Manifesto.  I'll also set the stage for what to expect next from this series.

This week I will tackle the four point of the Agile Manifesto, with an eye toward my conclusion podcast next week.

This week I will cover part three of four in the Agile Manifesto, as preparation for my final entry in this series that will suggest how to address these implications in your organization.

This week I will investigate part 2 of the Agile Manifesto, as part of my series of four podcasts on the subject.

This week I'll examine the first point in the Agile Manifesto, as part of a series of four podcasts.

In this episode we will examine the roots of the Agile Movement, and delineate the Agile Manifesto that came from those roots.  This will begin a series of five podcasts that point out the implications of each item in this manifesto.