What is Agile Software Development example? Image result for agile software development Examples of Agile Methodology. The most popular and common examples are Scrum, eXtreme Programming (XP), Feature Driven Development (FDD), Dynamic Systems Development Method (DSDM), Adaptive Software Development (ASD), Crystal, and Lean Software Development (LSD).

1. Phases in Agile Development
Course: Agile Software development

2. 1. Conception, initiation, Analysis (requirements analysis )
2. Design (DFD, ER)
3. Construction (implementation, coding)
4. Testing (different phases of testing)
5. Deployment

4. Phases in Agile
• Even though Agile Phases may look similar to the waterfall
model SDLC, there are several differences.
• The key differences is that Agile incorporate collaboration,
iteration and an incremental approach.
• In Agile Development, the features of the product to be
developed are first identified. New features identified in the
course of the life cycle are planned across sprints.

5. Sprint
• Sprint is the most basic unit of development and is defined as a fixed
period of time during which a specific task has to be completed and made
ready for review.
• The duration of each sprint depend on the feature to be developed
• Each sprint goes through all the phases.

6. Overview of Phases
• The actual implementation may differ in the real world.
• The Requirements Analysis phase, for example may consist of
three sub-stages, conception, initiation and analysis where the
project is first conceptualized, initiated and then finally
analyzed.
• The basic tasks in each phase are almost similar to the waterfall
model, however every phase is iterative and incremental.

7. Requirements Analysis
• The Conception phase, also called as Iteration -1, helps to
define the problem of business opportunity, that leads to identify
and assess a feasible strategy for the project.
• The next phase, initiation, take place during the first one week
or so and is sometimes called iteration 0. in this phase, the
project is initiated through a feasibility study and working with
stakeholders to determine the initial requirements.
• Analysis phase involves performing a requirement analysis.

8. • 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.

9. Design
• Design phase involve creating design strategies to model the
system.
• 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.

10. Development
• Implementation phase begins the project’s actual development
of the project.
• 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.

11. Testing and Deployment
• Testing will evaluate and test the completed project on various
aspects and factors.
• The Quality Assurance team examine the product's performance
and look for the bug.
• Deployment is the final stage of launching the project.

12. ASDLC

13. Agile SDLC Process Flow
• Concept: Project are imagined and prioritized.
• Inception: Team members are created, funding is put in place, and basic
environments and requirements are discussed.
• Iteration/Constriction: The software development team works to
deliver working software. It is based on requirement and feedback.
• Release: Perform quality assurance (QA) testing, provides internal and
external training, documentation development, and final version of
iteration into the product.
• Production: It is ongoing support of the software.

14. Advantages
• Project is divided into short and transparent iterations.
• It has a flexible change process.
• It minimizes the risk of software development.
• Quick release of the first product version.
• The correctness of functional requirement is implemented into the
development process.
• Customer can see the result and understand whether he/she is satisfied with
it or not.

15. Disadvantages
• The development team should be highly professional and client-oriented.
• New requirement may be a conflict with the existing architecture.
• With further correction and change, there may be chances that the project
will cross the expected time.
• There may be difficult to estimate the final coast of the project due to
constant iteration.
• A defined requirement is absent.