Facts About Traditional Waterfall Methodology
Traditional Project Methodology also known as waterfall methodology is the old method of managing project that always starts from initiation and ending in the closing of the project. In this type of project methodology, any stage of the project that is already completed will never be revisited.
This type of project methodology makes use of a classical framework that takes a step by step approach to project execution. The project normally goes through initiating, planning, executing up to the closing of the project.
Waterfall methodology often called the linear approach to project management consist of different phases which are executed in a linear or chronological order. This is often used in engineering or construction project where little modification is expected from the beginning to the end of the project. Some Engineering projects have also embraced the use of waterfall methodology as well.
Waterfall methodology has been a dominant project methodology when it was described by Winston W Royce when he said” There are two essential steps common to all computer program developments, regardless of the size or complexity. There is first an analysis step, followed second by a coding step…This sort of very simple implementation concept is, in fact, all that is required if the effort is sufficiently small and if the final product is to be operated by those who built it-as is typically done with computer programs for internal use”.
Waterfall model has a strong emphasis on
planning and specifications development:
it is considered to take up to 40% of the project
time and budget. Another basic principle of this
the approach is a strict order of the project phases.
A new project stage does not begin until the
the previous one is finished.
The method works well for clearly defined
projects with a single deliverable and fixed
Waterfall approach requires thorough
planning, extensive project documentation and
tight control over the development process.
In theory, this should lead to on-time, on-budget
delivery, low project risks, and predictable final
However, when applied to the actual software
engineering process, the waterfall method tends
to be slow, costly and inflexible due to the
In many cases, its
inability to adjust the product to the evolving
market requirements often result in a huge
waste of resources and eventual project failure.
Now your take on this argument.
We would also like to hear what you feel about the topic we discussed today. Your feedback is very important to us. Feel free to drop your comments and recommendations. If you have a contrary opinion, you can drop that too.
You can also join our Facebook Page CRMNigeria for more updates. You can do that by clicking on the link or searching for our page on Facebook.