Agile Methodology

 The Agile methodology is a project management and software

development approach that emphasizes flexibility,
collaboration, and customer-centricity.
 It is the latest model used by major companies today like
Facebook, google, amazon, etc.
 It follows the iterative as well as incremental approach which
means it’s known for breaking a project into smaller parts and
adjusting to changing requirements.
 It focuses on delivering smaller pieces of work regularly
instead of one big launch.
 This allows teams to adapt to changes quickly and provide
customer value faster.

Types of Agile Frameworks

1. Kanban
2. Scrum
3. Lean
4. DSDM or Dynamic Systems Development Method ·
5. XP or Extreme Programming
6. FDD or Feature Driven Development
7. Crystal
8. Scaled Agile Framework (SAFe)

Agile Methodology Advantage and Disadvantage

The main advantage and disadvantage of agile methodology are:
 Advantage : Agile methodologies allow for flexibility and
adaptability in responding to changes. Teams can easily
adjust their plans and priorities based on evolving
requirements or feedback during the project.
 Disadvantage: The iterative and adaptive nature of agile
can sometimes lead to uncertainty, especially in projects
with unclear or rapidly changing requirements. This may
pose challenges in estimating timelines and costs
accurately.

Life cycle of Agile Methodology

The Agile software development life cycle helps you break down
each project you take on into six simple stages:

1. Requirement Gathering
 In this stage, the project team identifies and documents the
needs and expectations of various stakeholders, including
clients, users, and subject matter experts.
 It involves defining the project’s scope, objectives, and
requirements.
 Establishing a budget and schedule.
 Creating a project plan and allocating resources.
2. Design
 Developing a high-level system architecture.
 Creating detailed specifications, which include data
structures, algorithms, and interfaces.
 Planning for the software’s user interface.
3. Development (Coding)
Writing the actual code for the software. Conducting unit testing to
verify the functionality of individual components.
4. Testing
This phase involves several types of testing:
1. Integration Testing: Ensuring that different components
work together.
2. System Testing: Testing the entire system as a whole.
 3. User Acceptance Testing: Confirming that the software
meets user requirements.
4. Performance Testing: Assessing the system’s speed,
scalability, and stability.
5. Deployment
1. Deploying the software to a production environment.
2. Put the software into the real world where people can use
it.
3. Make sure it works smoothly in the real world.
4. Providing training and support for end-users.
6. Review (Maintenance)
1. Addressing and resolving any issues that may arise after
deployment.
2. Releasing updates and patches to enhance the software
and address problems.

When to use Agile Method

It is particularly well-suited for projects and organizations where
the following conditions or needs are present:
1. Unclear or Changing Requirements: Agile is great for
projects with requirements that aren’t well-defined or might
change.
2. Complex Projects: It’s good for big, complex projects by
breaking them into smaller pieces.
3. Customer Focus: Use Agile when making customers
happy is a priority and you want to involve them
throughout.
4. Quick Time-to-Market: If you need to get your product
out fast, Agile can help.
5. Small to Medium Teams: Agile works well for teams of a
few to a few dozen people.
6. Team Skills: It’s best when you have a mix of skills in your
team, like development, testing, design, and more.
7. Collaboration: Agile promotes working together and open
communication.
8. Regular Updates: If you want to check progress often and
make changes as needed.
9. Transparency: Agile emphasizes being open and clear
with everyone involved in the project.
 10. Risk Control: It helps manage risks by tackling issues
as they come up.
11. Innovation: If you encourage trying new things and
learning from experience, Agile supports that.
12. Continuous Improvement: Agile fosters a culture of
always getting better over time.

Clearly defined user

Requires interactive
requirements before
user inputs.
User requirements coding.

Benefits of Agile Methodology

The advantages of the agile model are as follows:
1. Immediate Feedback: It allows immediate feedback,
which aids software improvement in the next increment.
2. Adapts to Changing Requirements: It is a highly
adaptable methodology in which rapidly changing
requirements, allowing responsive adjustments.
3. Face-to-Face Communication: Agile methodology
encourages effective face-to-face communication.
4. Time-Efficient: It is well-suited for its time-efficient
practices, which help in delivering software quickly and
reducing time-to-market.
5. Frequent Changes: It effectively manages and
accommodates frequent changes in project requirements
according to stakeholder convenience.
6. Customer Satisfaction: It prioritizes customer
satisfaction.
7. Flexibility and Adaptability: Agile methodologies are
known for their flexibility and adaptability.
Limitations of Agile Methodology
The disadvantages of the agile model are as follows:
1. Less Documentation: Agile methodologies focus on less
documentation; it prioritizes working on projects rather
than paperwork.
2. Challenges in Large Organizations: Busy schedule of
clients can make daily meetup and face-to-face
communication difficult.
 3. Need for Senior Programmers: It may require
experienced programmers to make critical decisions during
the development of software.
4. Limited Scope Control: It has less rigid scope control,
which may not be suitable in certain situations.
5. Predictability: Compared to more structured project
management methods, it may lack predictability.

Popular Agile Tools for Software Development

An Agile Tool for software development is a software application or
a platform that enables the teams to manage and track the Agile
project more efficiently.
Some popular agile tools are:
1. Jira
2. ClickUp
3. Mural
4. Kanbanize
5. GitHub
6. Monday.com
7. Jenkins
8. Shortcut

What is Scrum
 So, why is it called Scrum? People often ask, “Is Scrum an acronym for
something?” and the answer is no.
 It is actually inspired by a scrum in the sport of rugby.
 In rugby, the team comes together in what they call a scrum to work together
to move the ball forward.
 In this context, Scrum is where the team comes together to move the product
forward.
 Scrum is the type of Agile framework.
 It is a framework within which people can address complex adaptive problem
while productivity and creativity of delivering product is at highest possible
values.
 Scrum uses Iterative process.
 Scrum has three roles: product owner, scrum master, and the development
team members.

Silent features of Scrum are:

 Scrum is light-weighted framework
 Scrum emphasizes self-organization
 Scrum is simple to understand
 Scrum framework help the team to work together
Sprint:
A Sprint is a time box of one month or less.
A new Sprint starts immediately after the completion of the
previous Sprint.
Release: When the product is completed, it goes to the Release
stage.
Sprint Review: If the product still has some non-achievable
features, it will be checked in this stage and then passed to the
Sprint Retrospective stage.
Sprint Retrospective: In this stage quality or status of the
product is checked.
Product Backlog: According to the prioritized features the product
is organized.
Sprint Backlog: Sprint Backlog is divided into two parts Product
assigned features to sprint and Sprint planning meeting.