Scribd
Upload
152 views2 pages

Agile Vs Waterfall Model

The document compares and contrasts the Agile and waterfall software development models. It notes that Agile focuses on adaptability and quick response to changing requirements, while waterfall prioritizes predictability and processes. Additionally, Agile allows for recursiveness where completed stages can be modified, unlike the waterfall model. The key advantages of Agile listed are its backward scalability, flexibility for error checking at any stage, better ability to adapt to customer requirements, and more effective modular partitioning of software.

Uploaded by

Carlon Baird
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
152 views2 pages

Agile Vs Waterfall Model

The document compares and contrasts the Agile and waterfall software development models. It notes that Agile focuses on adaptability and quick response to changing requirements, while waterfall prioritizes predictability and processes. Additionally, Agile allows for recursiveness where completed stages can be modified, unlike the waterfall model. The key advantages of Agile listed are its backward scalability, flexibility for error checking at any stage, better ability to adapt to customer requirements, and more effective modular partitioning of software.

Uploaded by

Carlon Baird
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Agile software development undoubtedly offers advantages that a waterfall approach cant

begin to address. Where the waterfall approach is based in predictability and processes, an
Agile approach focuses on adaptability and response time to changing requirements. Another
important advantage of Agile over the waterfall model is the recursiveness of the work pattern.
This means that we can make modifications to the completed stage in Agile while it is not
allowed under waterfall model.

Agile Vs Waterfall Model


It is worth mentioning here that the Waterfall model is the primitive model type and has been
implemented in the development phase time after time. Hence in the due course if time
developers found many drawbacks in this model which were later rectified to form various

other development models.

The common element to all of them being the basic phases of the waterfall approach. We can
hence conclude that Agile is also another of its successors which has all the advantages of the
primitive waterfall model and has also rectified the disadvantages in this evolved model.

Difference between Agile and Waterfall Model


1. The main advantage is the backward scalability in Agile. Under waterfall approach we
cannot change the decisions and implementations that we had made under the previous
stages. If we want to make changes under waterfall we will have to build the entire project
from the scratch once again.
2. The flexibility to error check under any part of the development stage makes Agile more
bug free and less erroneous as compared to Waterfall which can only test bugs at the end
of the development module.
3. Since Agile provides flexibility to make changes as per customer requirements it is more
inclined towards better client satisfaction. This is a real setback for the Waterfall model
which doesnt allow any modifications once the module has been completed.
4. Under Agile development modular partitioning of the software can be effectively carried
out as compared to its counterpart. Though both of them allows option for segregation
the later lacks the modifications in the implementation stage. The rules are set down
before the commencement of the project hence it hinders further break down of the logical
module. Whereas Agile can be of great help under such situations and can allow
simultaneous development of different modules at the same time as per time bound
requirement. If we want the project to be more segregated Agile comes as a pain relief
for developers.

You might also like