Difference Between Agile And Waterfall Model

1779 Words8 Pages
White Paper Agile Model and Methodologies November 2015 Table of Contents Abstract 1 1. Agile Model 1 2. Agile versus Waterfall model 1 3. Agile Testing Methods 4 3.1 Scrum 4 3.2 Crystal Methodologies 4 3.3 Dynamic Software Development Method(DSDM) 4 3.4 Feature Driven Development(FDD) 4 3.5 Lean Software Development 4 3.6 eXtreme Programming(XP) 4 4. Conclusion 4 5. References 5 6. About the Authors 5 Abstract AGILE is a methodology that promotes continuous iteration of development and testing throughout the software development life cycle of the project. Both development and testing activities are concurrent unlike the Waterfall model This white paper describes the Agile Model…show more content…
Agile versus Waterfall model Agile and Waterfall model are two different methods for software development process. Though they are different in their approach, both methods are useful at times, depending on the requirement and the type of the project. Agile Model Waterfall Model • Agile method proposes incremental and iterative approach to software design • Development of the software flows sequentially from start point to end point. • The agile process is broken into individual models that designers work on • The design process is not broken into an individual models • The customer has early and frequent opportunities to look at the product and make decision and changes to the project • The customer can only see the product at the end of the project • Agile model is considered unstructured compared to the waterfall model • Waterfall model are more secure because they are so plan oriented • Small projects can be implemented very quickly. For large projects, it is difficult to estimate the development time. • All sorts of project can be estimated and completed. Agile Model Waterfall Model • Error can be fixed in the middle of the project. • 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…show more content…
Early delivery 5. Empowering the team 6. Building Integrity 7. Optimize the whole 3.6eXtreme Programming (XP): Extreme Programming technique is very helpful when there is constantly changing demands or requirements from the customers or when they are not sure about the functionality of the system. It advocates frequent "releases" of the product in short development cycles, which inherently improves the productivity of the system and also introduces a checkpoint where any customer requirements can be easily implemented. The XP develops software keeping customer in the target. Figure 4:QA Development cycle of Extreme Programming(XP) Business requirements are gathered in terms of stories. All those stories are stored in a place called the parking lot. In this type of methodology, releases are based on the shorter cycles called Iterations with span of 14 days time period. Each iteration includes phases like coding, unit testing and system testing where at each phase some minor or major functionality will be built in the application. Phases of eXtreme programming: There are 6 phases available in Agile XP method, and those are explained as follows: Planning • Identification of stakeholders and sponsors • Infrastructure
Get Access