Main Difference between Agile & Waterfall Methodologies
Waterfall | Agile |
In waterfall model once a step has been completed, developers can’t go back to a previous stage and make changes. | The Agile methodology allows for changes to be made after the initial planning. Re-writes to the program, as the client decides to make changes, are expected. you can make changes on next sprint |
Waterfall methodology relies heavily on initial requirements. However, if these requirements are faulty in any manner, the project is doomed. | The Agile methodology total deliverable is divided into some sprints, if there is any backlogs that can come in next sprint. |
If there is any change needs to be made, the project has to start from the beginning with all new code. | Agile methodology allows you to make changes, it’s easier to add features that will keep you up to date with the latest developments |
Whole product is only tested at the end. It may fail during integration testing then the product will not be delivered on time or even fail. | The testing at the end of each sprint ensures that the bugs are caught and taken care of in the development cycle. They won’t be found at the end. |
If the client realizes that they need more than they initially thought, and demand change, the project will come in late and impact budget. | Because the products are tested so thoroughly with Agile, the product could be launched at the end of any cycle. As a result, it’s more likely to reach its launch date. |
Latest posts by Gopal Das (see all)
- Salesforce Certified Platform Developer I – Winter ’18 Release Exam - November 23, 2017
- Salesforce Certified Platform App Builder – Winter ’18 Release Exam - November 22, 2017
- Salesforce Certified Administrator – Winter’ 18 Release Exam - November 21, 2017