Top 5 reasons to use Waterfall


When to use Waterfall Methodology:


  1. Requirements are very well known
  2. Product definition is stable
  3. Technology is understood
  4. New version of an existing product
  5. Porting an existing product to a new platform.


Weakness of Waterfall:

  1. All requirements must be fully specified upfront
  2. Deliverables created for each phase are considered frozen – inhibits flexibility
  3. Can give a false impression of progress
  4. Does not reflect problem-solving nature of software development – iterations of phases
  5. Integration is one big bang at the end
  6. Little opportunity for customer to preview the system (until it may be too late)

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more