Comparison of characteristics between the agile models with other models is
given below:
Agile model Vs. Waterfall model
Agile model
https://www.youtube.com/watch?
v=Z9QbYZh1YXY
The agile model is an incremental delivery
process where each incremental delivered
part is developed through an iteration after
each timebox.
While using an agile model, progress is
measured in terms of the developed and
delivered functionalities.
With the agile model, even if a project is
canceled midway, it still leaves the customer
with some worthwhile code that might
possibly have already been put into live
operation.
The agile model allows changing the
requirements after the development process
starts, so it is more flexible.
Customer interaction is very high. After
each iteration, an incremental version is
deployed to the customer.
The lack of proper formal documentation
leaves ample scope for confusion and
important decisions taken during various
Waterfall model
https://www.youtube.com/watch?
v=Y_A0E1ToC_I
The waterfall model is highly structured and
systematically steps through requirements
gathering, analysis, SRS document
preparation, design, coding, and testing in a
planned manner. These phases of the
Waterfall model follow a sequential order.
In the Waterfall model, progress is generally
measured in terms of the number of
completed and reviewed artifacts such as
requirement specifications, design
documents, test plans, code reviews, etc. for
which review is complete.
If a project is developed using the waterfall
model is canceled mid-way during
development, then there is nothing to show
from the abandoned project beyond several
documents.
The waterfall model is rigid, it does not
allow to change requirements after the
development process starts.
Customer interaction is very less. The
product is delivered to the customer after
the overall development is completed.
In the Waterfall model, proper
documentation is very important, which
gives a clear idea of what should be done to
 Agile model Waterfall model
https://www.youtube.com/watch? https://www.youtube.com/watch?
v=Z9QbYZh1YXY v=Y_A0E1ToC_I

complete the project and it also serves as an

phases can be misinterpreted in fewer later
agreement between the customer and the
phases.
development team.

The agile team consists less members (5 to 9 In the Waterfall model, teams may consist
people), but they coordinate and interact of more members but the interaction
with others very frequently. between them is limited.

The agile model is not suitable for small

This model is simple to use and understand
projects as the expenses of developing small
but not suitable for developing large
projects using it is more compared to other
projects using the Waterfall model.
models.

The testing is done simultaneously with

After the Build Step, testing is done.
software development.

It is a systematic developing method,

It is known for its versatility.
sometimes rigorous.

Testing is generally carried out in The test approach is rarely used in this
conjunction with the development phase. method.

Agile model Vs RAD model:

Agile model RAD model

The Agile model does not recommend

developing prototypes but emphasizes the The central theme of RAD is based on
systematic development of each designing quick and dirty prototypes, which
incremental feature at the end of each are then refined into production-quality code.
iteration.

Agile projects logically break down the The developers using the RAD model focus
 Agile model RAD model

on developing all the features of an

solution into features that are
application by first doing it badly and then
incrementally developed and delivered.
successively improving the code over time.

Whereas RAD teams demonstrate to

The Agile team only demonstrates
customers screen mocks up and prototypes,
completed work to the customer after each
that may be based on simplifications such as
iteration.
table lookup rather than actual computations.

The agile model is not suitable for small When the company has not developed an
projects as it is difficult to divide the almost similar type of project, then it is hard
project into small parts that can be to use the RAD model as it is unable to reuse
incrementally developed. the existing code.

Agile model Vs Incremental development model:

Agile model Incremental development model

The agile model is an incremental delivery

The requirements of the software are
process where each incremental delivered
divided into several modules that can be
part is developed through an iteration after
incrementally developed and delivered. The
each time box. The main principle of the
core features are developed first and the
Agile model is to achieve agility by
whole software is developed by adding new
removing unnecessary activities that waste
features in successive versions.
time and effort.

In the Agile model, the end date for an

iteration is fixed, it cannot be changed. The In the Incremental development model,
development team may have to decide to there is no fixed time to complete the next
reduce the delivered functionality to iteration.
complete that iteration on time.
Agile model Vs Spiral model:

Spiral model
Agile model https://www.youtube.com/watch?v=zbA91dYqw80

The main principle of

the Agile model is to
achieve agility by
The main principle of the Spiral model is risk handling.
removing unnecessary
activities that waste
time and effort.

The Agile model

focuses on the delivery
of an increment to the
The spiral model mainly deals with various kinds of
customer after each
unanticipated risks but customer interaction is less.
Time-box, so customer
interaction is more
frequent.

The agile model is

suitable for large
projects that are easy to
The Spiral model is suitable for those projects that are prone to
divide into small parts
various kinds of risks that are difficult to anticipate at the
that can be easily
beginning of the project.
developed
incrementally over
each iteration.

The agile model does

not rely on Proper documentation is required for the Spiral model.
documentation.
Agile and Iterative Model
Agile Model Iterative Model

The Iterative Model of software

The Agile Model of software
development is a type of model in which
development is a type of model in
implementation starts with small elements,
which specifications and solutions
and iteratively evolves to the final solution
enhance through the continuous
through a collaboration of functional
collaboration of functional teams.
teams.

The process of development in this The process of development in this model

model is called Sprint. is called an Iteration.

With the completion of a sprint, a With the completion of an iteration, a

meeting is carried out. meeting is carried out.

The preceding sprint affects the The preceding iteration affects the
subsequent sprint. subsequent iteration.

Collaborating teams can review Collaborating teams can review products

products during a Sprint. on the baseline of iteration.

There are two main roles in this

There are two roles in this model Project
model Scrum Master and Team
Manager and Team Member.
member.

Scrum Master is responsible for the The Project Manager is responsible for the
facility and team members do the estimation and completion of each
estimation. iteration.

Test cases are prepared, identified, Test cases are prepared, identified, and
and executed by team members. executed by Testers.

Deploying and Demonstration of Deploying and Demonstration of software

software are done at end of each are done at end of iteration.
 Agile Model Iterative Model

sprint.

In case of agile model, if a valued

A work product is obtained after every
work product is not obtained after
iteration that can be mapped to something
iteration then it is basically a failure
of value.
within the iteration.

When to use-
When to use-
 It is suitable to use when each
 It is suitable to use in case a required
component’s development is
change affects the large numbers of
separate in terms of coding or as
components as major changes are
a change task.
needed by relevant features.
 For quick and frequent changes

More on agile

https://www.youtube.com/watch?v=8eVXTyIZ1Hs

How agile work

https://www.youtube.com/watch?v=1iccpf2eN1Q