Shri Vaishnav Vidyapeeth

Vishwavidyalaya, Indore (M.P.)

Lecture

on

“ Agile Model”

.
Prepared By
Virendra Dani
 Agile Model
 Agile SDLC model is a combination of iterative and
incremental process models with focus on process
adaptability and customer satisfaction by rapid
delivery of working software product.
 Agile Methods break the product into small
incremental builds. These builds are provided in
iterations.
 Agile Methodology meaning a practice that
promotes continuous iteration of development and
testing throughout the software development
lifecycle of the project.
 Agile Model
 In the Agile model in software testing, both
development and testing activities are concurrent,
unlike the Waterfall model.
 The Agile software development methodology is one
of the simplest and effective processes to turn a
vision for a business need into software solutions.
 Agile is a term used to describe software
development approaches that employ continual
planning, learning, improvement, team collaboration,
evolutionary development, and early delivery.
 Agile Model
 The agile software development emphasizes on four
core values :
1. Individual and team interactions over processes and
tools
2. Working software over comprehensive
documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan
 Phases of Agile Model
 The Following are the phases in the Agile model are
as follows:
1) Requirements gathering
2) Design the requirements
3) Construction/ iteration
4) Testing/ Quality assurance
5) Deployment
6) Feedback
 Agile Model
 Requirements gathering: In this phase, you must
define the requirements. You should explain business
opportunities and plan the time and effort needed to
build the project. Based on this information, you can
evaluate technical and economic feasibility.
 Design the requirements: When you have identified
the project, work with stakeholders to define
requirements. You can use the user flow diagram or
the high-level UML diagram to show the work of
new features and show how it will apply to your
existing system.
 Agile Model
 Construction/iteration: When the team defines the
requirements, the work begins. Designers and
developers start working on their project, which aims
to deploy a working product. The product will
undergo various stages of improvement, so it
includes simple, minimal functionality.
 Testing: In this phase, the Quality Assurance team
examines the product's performance and looks for the
bug
 Agile Model
 Deployment: In this phase, the team issues a product
for the user's work environment.
 Feedback: After releasing the product, the last step is
feedback. In this, the team receives feedback about
the product and works through the feedback.
 Agile Model
 The most popular Agile methods include Rational
Unified Process (1994), Scrum (1995), Crystal Clear,
Extreme Programming (1996), Adaptive Software
Development, Feature Driven Development, and
Dynamic Systems Development Method (DSDM)
(1995). These are now collectively referred to
as Agile Methodologies, after the Agile Manifesto
was published in 2001.
Agile Model
 Agile Model: Pros and Cons
 Agile methods are being widely accepted in the
software world recently. However, this method may
not always be suitable for all products. Here are
some pros and cons of the Agile model. The
advantages of the Agile Model are as follows −
1. A very realistic approach to software development.
2. Promotes teamwork and cross training.
3. Functionality can be developed rapidly and
demonstrated.
4. Resource requirements are minimum.
5. Suitable for fixed or changing requirements
 Agile Model
6. Good model for environments that change steadily.
7. Minimal rules, documentation easily employed.
8. Enables concurrent development and delivery within
an overall planned context.
9. Little or no planning required.
10. Easy to manage.
11. Gives flexibility to developers.
 Agile Model
 The disadvantages of the Agile Model are as follows:
1. Not suitable for handling complex dependencies.
2. More risk of sustainability, maintainability and
extensibility.
3. An overall plan, an agile leader and agile PM
practice is a must without which it will not work.
4. Strict delivery management dictates the scope,
functionality to be delivered, and adjustments to
meet the deadlines.
 Agile Model
5. Depends heavily on customer interaction, so if
customer is not clear, team can be driven in the
wrong direction.
6. There is a very high individual dependency, since
there is minimum documentation generated.
7. Transfer of technology to new team members may be
quite challenging due to lack of documentation.
Thank -You