Scribd
Upload
63 views8 pages

Agile Life Cycle

The document describes the Agile software development life cycle (SDLC). It is an iterative and incremental process that focuses on adaptability and customer satisfaction through rapid delivery of working software in small, incremental builds within each iteration. Each iteration consists of cross-functional teams working through phases like requirements gathering, design, construction, deployment, testing, and feedback.

Uploaded by

palvi kapur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
63 views8 pages

Agile Life Cycle

The document describes the Agile software development life cycle (SDLC). It is an iterative and incremental process that focuses on adaptability and customer satisfaction through rapid delivery of working software in small, incremental builds within each iteration. Each iteration consists of cross-functional teams working through phases like requirements gathering, design, construction, deployment, testing, and feedback.

Uploaded by

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

Agile SDLC

Presented By:
Priya Sachdeva
AP, CSE
Agile Software Development Life Cycle (SDLC)

• Agile Software Development Life Cycle (SDLC) is


the combination of both iterative and incremental
process models.
• It focuses on process adaptability and customer
satisfaction by rapid delivery of working software
product.
• Agile SDLC breaks down the product into small
incremental builds.
• These builds are provided into iterations.
Each iteration of agile SDLC consists of cross-
functional teams working on various phases:

1. Requirements gathering and analysis

• 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.
2. 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.
3. Construction/ Iteration

• When the team defines the requirements, the work


begins.
• The designers and developers start working on their
project.
• The aims of designers and developers deploy the
working product within the estimated time.
• The product will go into various stages of
improvement, so it includes simple, minimal
functionality.
4. Deployment

• In this phase, the team issues a product for the user's


work environment.

5. Testing

• In this phase, the Quality Assurance team examine the


product's performance and look for the bug.
6. Feedback

• After releasing of the product, the last step is to


feedback it.
• In this step, the team receives feedback about the
product and works through the feedback.
THANK YOU

You might also like