Waterfall Method Vs Agile Method

Waterfall VS Agile

Elicia Yates

CMGT/410

January 25, 2016

Rassoul Alizadeh

Waterfall VS Agile

The Waterfall and Agile methodologies are essentially the new way of completing a project verses the traditional way of project completion. While both use the same basic steps each methodology varies in the implementation of these steps. Depending of what the team and client and needing and wanting will be the ultimate decision in which method will work best for a specific project.

Waterfall project management is also known as the tradition project management style. This style of project management is done is numerous steps and implemented accordingly to accommodate the client. The steps are completed in this order. First all the requirements are gathered and documented; this is usually done through a series of meeting between the project managers and the clients. Second, a design is drafted. Third, the coding and unit testing is completed. Coding and testing takes the longest of all the steps. Fourth, system testing is performed followed by the fifth step that is user acceptance testing (UAT). The sixth step is to fix the issues that were identified in the testing steps. And the final step is to deliver the product. The positive attributes of the waterfall management style are the developers and clients agree on what will be delivered early on in the project cycle. The planning and designing is fairly straightforward because of the early decisions. Also, the project’s progress is easily measured and the client’s presence is not required. There are also negative attributes. One is that the software almost always falls short in effectiveness of requirements. Another negative attribute is the lingering possibility that the client will ultimately be dissatisfied.