Agile Tips

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