AGILE VS WATERFALL
Name: Vaibhav Gedigeri
MGT 609
Ricardo A. Collado
AGILE vs. WATERFALL
Agile and Waterfall are two sdistinct methods of software development. The Waterfall model can really be described as a linear model of software design. Like its name suggests, waterfall employs a sequential design process. Development essentially flows, sequentially from start point to end point, along several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.
In contrast, the agile method proposes an incremental and iterative approach to software design. It was essentially developed in response to the limitations of Waterfall methodology, as a way to give designers more freedom. The design process is split into individual models that designers work on. There is no pre-determined course of action or plan with the Agile method. Instead, designers are free to respond to changes in requirements as they arise and make changes as the project progresses. Agile is a pretty new player to the development game. However, it has made substantial gains in use and popularity in the last couple of years.
Pros of Waterfall model
1) The emphasis of Waterfall is the project plan and therefore before beginning any kind of development there needs to be a clear plan and a vision in order. Because the Waterfall method requires upfront, extensive planning, one can launch software fairly quickly.
2) One can also estimate timetables and budgets more accurately, which definitely tends to please clients.
3) Furthermore, Waterfall development processes tend to be more secure because they are so plan oriented. For example, if a designer drops out of the project it isn’t a huge problem, as the Waterfall method requires extensive planning and documentation. A new designer can easily take the old designer’s place, following the development plan without a problem.
4) Waterfall model works well for smaller projects where requirements are very well understood.
MGT 609
Ricardo A. Collado
AGILE vs. WATERFALL
Agile and Waterfall are two sdistinct methods of software development. The Waterfall model can really be described as a linear model of software design. Like its name suggests, waterfall employs a sequential design process. Development essentially flows, sequentially from start point to end point, along several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.
In contrast, the agile method proposes an incremental and iterative approach to software design. It was essentially developed in response to the limitations of Waterfall methodology, as a way to give designers more freedom. The design process is split into individual models that designers work on. There is no pre-determined course of action or plan with the Agile method. Instead, designers are free to respond to changes in requirements as they arise and make changes as the project progresses. Agile is a pretty new player to the development game. However, it has made substantial gains in use and popularity in the last couple of years.
Pros of Waterfall model
1) The emphasis of Waterfall is the project plan and therefore before beginning any kind of development there needs to be a clear plan and a vision in order. Because the Waterfall method requires upfront, extensive planning, one can launch software fairly quickly.
2) One can also estimate timetables and budgets more accurately, which definitely tends to please clients.
3) Furthermore, Waterfall development processes tend to be more secure because they are so plan oriented. For example, if a designer drops out of the project it isn’t a huge problem, as the Waterfall method requires extensive planning and documentation. A new designer can easily take the old designer’s place, following the development plan without a problem.
4) Waterfall model works well for smaller projects where requirements are very well understood.