I've recently finished reading Web Project Management: Delivering Successful Commercial Web Sites, by E-commerce guru Ashley Friedlein.

Mr. Friedlein comes from a television background, so he draws sort of a parallel between the steps of producing a TV show (pre-production, production, and post-production) and building a website - a metaphor which, when broken down further, actually works. They key difference being that once its done, the show is a finished product, whereas a web site is a living, malleable creation. One of the reviewers I think hit the nail on the head when he said:

This book is not about project management. In fact, someone versed in the Project Management Institute's Project Management Body of Knowledge will cringe at some of the statements made in the book (more about that below). It is, however, about delivering successful commercial web sites and it provides the best approach I have ever seen.

Even though its a pretty short book, he manages to touch on so many of the concerns you have to address when running a project and various ways to go about addressing those concerns effectively.

and now for something completely different..

I'm working on a project where I may be using Spring again. I've done three projects so far using it; obviously, it does a lot of a things right. However, the MVC piece is bit limited, hence Spring Webflow was created. I'm going through an example application now, and it seems to be essentially creating a state machine in XML to describe to page flow of an application. Perhaps more later after I get my hands a little dirtier.