Agile Vs Waterfall Model main difference

768px-Salto_del_Angel-Canaima-Venezuela08

Agile Vs Waterfall Model

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

What Is Waterfall Software Development

  1. Requirements – gathering the requirements of the system and what needs to be developed
  2. Design – designing the system
  3. Implementation – developing the software
  4. Verification – Both system and user testing
  5. Maintenance – ongoing support or maintenance of the system

Difference Between Agile & Waterfall

  1. Agile uses iterations, waterfall uses stages
  2. Agile has constant business interaction, waterfall has varied high and low interaction
  3. Agile has roles such as scrum master, waterfall has project manager.
  4. Can’t go back with Waterfall, can with agile

Which Is Better – Agile Vs Waterfall?

  1. Agile methods are more suited to those projects that need small and frequent functionality delivered to the users.
  2. Waterfall methods are suited to those projects where a high level of business involvement is not possible or not needed, and where quality is more important than speed to market.

4 responses to “Agile Vs Waterfall Model main difference”

  1. Hey there! This is my 1st comment here so I just wanted to give a quick shout out and say I genuinely enjoy reading your posts. Can you recommend any other blogs/websites/forums that cover the same topics? Many thanks!|

Leave a Reply