Yet Another “Why Waterfall Doesn’t Work” Post
Lately I have been plunged back into an extreme waterfall project and it is eating away at my soul. Don’t get me wrong. I don’t really believe in a soul and I have never done a text book agile project, but the longer I’m on this project the more I feel like I’m in an infinite loop. Document. Review. Document. Review. At some point we may do some coding.
The biggest problem with waterfall projects is that you can always add more detail to design documents. I have actually seen some documentation which had pseudo code for almost every line that the developer needs to type. Of course these are extreme cases, but they put a spotlight on the issue.
All of this would be less costly to refactor as we code than it would be to continue to refine the design document. A minimum of documentation to make sure we hit all the key requirements and make sure that the overall architecture is sound is really what a project needs. Spend your time finding the problems by writing code instead of theorizing and discussing.
Moral: Waterfalls are pretty to look at, not run projects with.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)