It does seem about that time that architects weigh in on whether all of the selling and pushing of SOA has indeed been justified by project success.

The verdict, at least from the view of those that have been painting the rosy picture of architectural utopia by the adoption of a brand new encompassing SOA implementation, is less than stellar.

I think this is a nice evolution in brief regarding Service Oriented Architecture.

Moving the SOA Goalposts

The sound fundamentals of software projects seem timeless no matter what the latest technology is. Understand the limitations of what you are using and don't use something unless you need it.

Robert Lefkowitz at the O'Reilly Open Source Convention presents a new process for Open Source.

Presentaion Here

I think that's pretty brilliant.

The 'no requirements' concept is way on the idealistic side. I don't see any project starting without even several basic requirements, even if they aren't recorded or detailed.

Also, for open source or any other project for that matter, in order to get momentum and attract interest, I don't see a project starting as sloppily as he described.

Good way to think about processes though.

Is being "test obsessed" reducing the efficiency of your agile project? This article, Agile Auto Testing, may spark some thoughts about that how that slick new automated test tool may fit into an agile project.

The theme for this site is a heavily modified version of a theme called "pushbutton", which can be found here drupal.org/project/Themes.

I chose that theme to modify because it was one of the first themes I found that worked well in Firefox, Safari, IE6 and IE7. There are of course others, for example, "aberdeen", which also works very well in each browser.