Waterfall

There are lots of interesting events coming up in 2006, but one of the ones I'm really looking forward to is the Waterfall conference at Niagara Falls on April 1st, which Colston Sanger just emailed me about.

After years of being disparaged by some in the software development community, the waterfall process is back with a vengeance. You've always known a good waterfall-based process is the right way to develop software projects. Come to the Waterfall 2006 conference and see how a sequential development process can benefit your next project. Learn how slow, deliberate handoffs (with signatures!) between groups can slow the rate of change on any project so that development teams have more time to spend on anticipating user needs through big, upfront design.

Trouble is, I'm having some difficulty getting the system to accept my registration. Can anyone suggest anything?

---

Update

Looks like the agile people are having a good laugh at the expense of the waterfall. But then Willems van den Ende has some second thoughts: Is the agile community its own worst enemy? It may be easy enough to set up the waterfall as the fall guy - an imaginary repository of process anti-patterns. But what if the effect is just to make everyone feel smug and self-righteous? Better by far to laugh at ourselves, than to laugh at some false Other.