Traditional - Waterfall

Waterfall model is the traditional software process. It is a good choice for customers, whose project has clear scope of work, and the customers need to tightly control its budget and timeline. “Over budget” and “Over run” are not accepted at this kind of project.

For these reasons, Waterfall model is still adopted by our customers, and by us.

This type of development is often planned using a Gantt chart – we complete one phase before moving on to the next phase.
In Waterfall approaches, we will rarely aim to re-visit a ‘phase’ once it’s completed. So when our clients provide us the request, we must get the clearly and fully request to analyze it and do right the first time!
Different to SCRUM, the waterfall model is a sequential process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation and Maintenance.

SEA-Solutions’ Waterfall process includes the following steps:
Why choose Waterfall Methodology?
  • The waterfall methodology stresses meticulous record keeping. Having such records allows for the ability to improve upon the existing program in the future
  • With the waterfall methodology, the client knows what to expect. They’ll have an idea of the size, cost, and timeline for the project. They’ll have a definite idea of what their program will do in the end
  • In the case of employee turnover, waterfall’s strong documentation allows for minimal project impact

When should you use waterfall methodology?

  • When there is a clear picture of what the final product should be
  • When you won’t have the ability to change the scope of the project once it has begun
  • When definition, not speed, is key to success