The Waterfall Method And The Agile Methods Of Development

2206 Words9 Pages
Evan Pierce
Marvin Hagen
Introduction to Business Intelligence – DSS600 - Lesson 9 Assignment
21 June 2015
Compare and Contrast the Waterfall Method and the Agile Methods of Development As it is with all decisions we make in the day, there are often multiple opportunities which often times lead to a single outcome. Such decisions as, “Do I take the turnpike today” can have such a profound impact on the outcomes. Will you hit traffic on turnpike and as a result miss a meeting. If you go the backway do you make the scheduled meeting? On any given day the same approach you have always taken can backfire. Keeping this in mind we must learn how the business methods we implement can often lead to the same outcome. What differs is the process
…show more content…
At no point in the process development can the next phase begin until the previous phase is completed. This is how the waterfall method received its name, it begins at the top and works its way down towards the bottom, and at no point can the process be reversed. Youssef Bassil in his article titled “A Simulation Model for the Waterfall Software Development Life Cycle”, defines the water fall method as the following, “The Waterfall model defines several consecutive phases that must be completed one after the other and moving to the next phase only when its preceding phase is completely done. For this reason, the Waterfall model is recursive in that each phase can be endlessly repeated until it is perfected.” There are certain situations where the waterfall method is advantageous in application and that involves the following; a short time frame, there3 are no unclear expectations, the technology is understood, the requirements are fixed and the product propose is stable.
There are distinct requirements of each phase in the water fall method, and the application of theses requirements often dictate the success or failure of any development project. The first phase is described as gathering and analysis which outlines and documents all possible requirements for the system being developed. This includes the
Get Access