Last night, I went to a talk given by Luke Hohmann of Enthiosys for Agile Austin.

The talk was focused around prioritizing the backlog. A more in depth version will be presented by Luke at the Agile Conference in August. There were a few good points that I took away from it.

This was the title of a session hosted by Jeffrey Palermo at the Agile Austin Open Space Conference that I attended recently.

It got me thinking a bit about the relationships between the various agile methodologies. I've always stressed the use of Agile over a particular methodology (such as Scrum) because I wanted to ensure that we felt free to use the best of each. In the end, I've generally found myself using Scrum with some concepts from XP.

A common misconception is that agile doesn't scale to large and/or distributed teams. Many of the agile methodologies focus on smaller teams, but that doesn't mean that their usefulness is limited to that context.

Large, distributed teams present their own challenges. These situations can be more difficult in any project management approach (including waterfall). Agile has proven to be compatible (I would argue superior) with these scenarios.