Floreth's Blog 2016-10-28 19:13:00

The waterfall method

Waterfall is a linear approach to software development, this means that as each of the eight stages (conception, initiation, analysis, design, construction, testing, implementation, and maintenance) are completed, the developers move on to the next step (Base 36, 2016).

Waterfall vs Agile:


Benefits of the waterfall method:
  • Once a step has been completed, developers can’t go back to a previous stage and make changes and get things done a lot faster.
  • It relies heavily on initial requirements. However, if these requirements are faulty in any manner, the project is doomed.
  • If a requirement error is found, or a change needs to be made, the project has to start from the beginning with all new code.
  • The whole product is only tested at the end. If bugs are written early, but discovered late, their existence may have affected how other code was written.
  • Additionally, the temptation to delay thorough testing is often very high, as these delays allow short-term wins of staying on-schedule.
  • The plan doesn’t take into account a client’s evolving needs. If the client realizes that they need more than they initially thought, and demand change, the project will come in late and impact budget.




Sources & Links: