Agile Model Vs Waterfall Model

Agile Model

Waterfall Model

1. Agile method proposes incremental and iterative approach to software design

1. Development of the software flows sequentially from start point to end point.

2. The agile process is broken into individual models that designers work on

2. The design process is not broken into an individual models

3. The customer has early and frequent opportunities to look at the product and make decision and changes to the project

3. The customer can only see the product at the end of the project

4. Agile model is considered unstructured compared to the waterfall model

4. Waterfall model are more secure because they are so plan oriented

5. Small projects can be implemented very quickly. For large projects, it is difficult to estimate the development time.

5. All sorts of project can be estimated and completed.

6. Error can be fixed in the middle of the project.

6. Only at the end, the whole product is tested. If the requirement error is found or any changes have to be made, the project has to start from the beginning

7. Development process is iterative, and the project is executed in short (2-4) weeks iterations. Planning is very less.

7. The development process is phased, and the phase is much bigger than iteration. Every phase ends with the detailed description of the next phase.

8. Documentation attends less priority than software development

8. Documentation is a top priority and can even use for training staff and upgrade the software with another team.

9. Every iteration has its own testing phase. It allows implementing regression testing every time new functions or logic are released.

9. Only after the development phase, the testing phase is executed because separate parts are not fully functional.

10. In agile testing when an iteration end, shippable features of the product is delivered to the customer. New features are usable right after shipment. It is useful when you have good contact with customers.

10. All features developed are delivered at once after the long implementation phase.

11. Testers and developers work together

11. Testers work separately from developers

12. At the end of every sprint, user acceptance is performed

12. User acceptance is performed at the end of the project.

13. It requires close communication with developers and together analyse requirements and planning

13. Developer does not involve in requirement and planning process. Usually, time delays between tests and coding