1. Agile Model
Software Development Life Cycle (SDLC)

2. Agile Model
★ It is a combination of iterative and incremental process
models.
★ The main aim is to help a project to adapt to change
requests quickly to facilitate quick project completion by
removing unnecessary activities that waste time and effort.
Agile : able to move quickly & easily.

3. Agile Model
★ The requirements are decomposed into many small parts
that can be incrementally developed.
★ The division of the entire project into smaller parts helps to
minimize the project risk and to reduce the overall project
delivery time requirements.

4. Agile Model
★ Each iterations are short time frames (timeboxes) that typically last
from one to four weeks.
★ Each iteration involves a cross-functional team working in all
functions:
planning, analysis, design, coding, unit testing, and acceptance testing.
★ At the end of the iteration a working product is demonstrated to
stakeholders.

5. Agile Model
★ An iteration might not add enough functionality to warrant a market
release, but the goal is to have an available release (with minimal bugs) at
the end of each iteration.
★ Multiple iterations might be required to release a product or new features.
★ Working software is the primary measure of progress.
An agile process focuses more on code development rather than documentation
and customer interaction is more frequent.

7. Agile Methodologies
There are several Agile Methodologies that support Agile Development.
The Agile Methodologies include −
★ Scrum
★ Crystal
★ Dynamic Software Development Method(DSDM)
★ Feature Driven Development(FDD)
★ Lean Software Development
★ eXtreme Programming(XP)

8. Advantages & Disadvantages
➢ Deployment of software is quicker.
➢ Can adapt to rapidly changing requirements and respond faster.
➢ Customer interaction and satisfaction is done in each iteration
➢ Helps in getting immediate feedback which can be used to improve the
software in the next iteration.
➢ More code focused and produces less documentation.
➢ Not suitable for handling complex dependencies.
➢ Depends heavily on customer interaction,