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.

Attend these valuable tutorials:

• Take Control of Your Team’s Decisions NOW! by Ken Schwaber
• Avoiding the Seven Pitfalls of Lean by Mary Poppendieck
• Pair Managing: Two Managers per Programmer by Jim Highsmith
• Two-Phase Waterfall: Implementation Considered Harmful by Robert C. Martin
• User Interaction: It Was Hard to Build, It Should Be Hard to Use by Jeff Patton
• FIT Testing In When You Can; Otherwise Skip It by Ward Cunningham
• The Joy of Silence: Cube Farm Designs That Cut Out Conversation by Alistair Cockburn
• wordUnit: A Document Testing Framework by Kent Beck
• Slash and Burn: Rewrite Your Enterprise Applications Twice a Year by Michael Feathers
• Very Large Projects: How to Go So Slow No One Knows You’ll Never Deliver by Jutta Eckstein
• Eliminating Collaboration: Get More Done Alone by Jean Tabaka
• Retrospectives: Looking Back…Looking Aaaall the Way Back by Diana Larsen
• The Glacial Methodology™ Workshop: A Data-Centric Software Development Process by Scott Ambler
• Introduction to Dogmatic Programming by Andy Hunt and Dave Thomas
• Unfactoring from Patterns: Job Security through Unreadability by Joshua Kerievsky
• Honing Cut-Throat Competition Among Employees: The Art and Science of Forced-Rank Evaluations by Esther Derby
• Making Outsourcing Work: One Team Member per Continent by Babu Bhatt
• User Stories and Other Lies Users Tell Us by Mike Cohn
• Refuctoring by Jason Gorman
• Ruby On Snails: Slow Down Development With This New Framework by Dave Thomas and Mike Clark
• Defect-full Code: Ensuring Future Income with Maintenance Contracts by Kay Pentecost
• Testing: Saving the Best for Last by Lisa Crispin
• …

Because it’s possible you may want to attend all sessions, Waterfall 2006 features no concurrent sessions. All sessions are run sequentially for your enjoyment. However, since in a waterfall process we don’t want testers to know anything about coding, or programmers to know anything about design, and so on, you can only attend sessions that match your job function. When you register to attend you’ll be asked to select an appropriate job function. When sessions that are not relevant to you are running you will be required to sit idle in the lobby.