why businesses are in deep yoghurt


Waterfall 2006 - International Conference on Sequential Development
At first, I thought it was serious - but this site is almost as good as the Curt Jester.
Waterfall methodologies are those that progress in linear fashion through a series of stages - for example, Feasibility, Requirements, External Design, Program Specifications, Coding, Testing, Production.

The problem with waterfall methodologies is that they don't work all that well. Trying to create complete, perfect system specifications before you start any coding simply ensures you've wasted a bunch of effort, because once developers start coding, design flaws become evident and require that you revisit earlier stages.

Except that you can't, because that stage is complete and there's no budget for going back.

February 2013

Sun Mon Tue Wed Thu Fri Sat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28    
The WeatherPixie

About this Entry

This page contains a single entry by alicia published on June 8, 2006 7:38 PM.

Relying on Experts? was the previous entry in this blog.

why, oh why? is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.