Waterfall, what ya fail
Here is an article against the myth of Waterfall Model, which is still commonly used and considered as correct standard in enterprise software development projects in Hong Kong.
Don’t draw diagrams of wrong practices - or: Why people still believe in the Waterfall model
Don’t draw diagrams of wrong practices - or: Why people still believe in the Waterfall model
Comments
Implementing then specificating?
Testing before coding? xD
I'm serious, what's the problem with this method?
The main problem is that we cannot practically complete a task in a phase. Software Development needs iterative and incremental process instead of sequential process as Waterfall.
I know that a modified Waterfall Model is added with iteration but it does not solve its sequential process problem.
See detail at http://en.wikipedia.org/wiki/Rational_Unified_Process
See the wikipedia article for more information.
Also, building the architecture as the needs grow is a central agile practice. And most user-centric design approaches emphasize the importance of iterative design with frequent user feedback, which means that you need to implement something in order to refine your specifications.
Thanks for your opinion. You raised a very good point - Iterative Refinement.