There has been a lot of conversation recently on the question of web and software project agility – that is, movement from traditional plan-driven methods in favor of iteration. 

Web strategists and developers are moving to agile processes because the technology marketplace demands higher response to change. Specifically, no sooner do you develop a plan document when the scope changes  – causing loss of time, productivity and bottom-line ROI.

A colleague of mine, Brian Molstad of Molstad Consulting summed it up nicely: 

"As much as I am a major proponent of documenting requirements and asking the right questions early on, I recognize that documents and prototypes have a shelf life. When it's time to move on to the next iteration, it's time to move on. 

Unfortunately, some development teams I've worked with get a little documentation, and they ask for more and more.  I've much preferred working with those teams who take the high-level structure I provide and innovate within (and outside of) the box. When other developers/clients have asked for more specs, I prefer to respond with, "can't we move into HTML to get this going?"

Perhaps I have no problem giving up "control" of a project since I don't come from a formal project management background and more that of information architecture, usability, user-centered design, etc., which has always favored designing in iterations. I look at project management as whatever it takes to get the project done and provide the most value quickly. Here's to agile development!"

If you feel you’re  ready to take the ‘agility’ plunge – here are some great resources to get started.

Discussion groups:

Agile Project Management

Scrum Development

Extreme Programmer

Best

Denice MacDonald