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.

No matter what kinds of products and services an organization offers, there are terms that are specific to them.  These terms must be carefully defined and consistently updated as things change.  This podcast is all about creating such a set of definitions.

This episode will introduce a useful framework for organizing requirements as the are identified.  Such organization can be very helpful in collaboration and validation throughout an agile process.

Various technologies provide us with the concept of "inheritance".  What should this used for, ideally, in an agile development environment?  This episode addresses this question in a way that should be interesting to non-technical people as well as developers and testers.

The way we create business automation in the modern environment has been influenced by the strength of various innovations that have preceded us.  This week I'll introduce this idea, and then over the next few episodes will examine some of the implications and opportunities.