Agile Methodology

Agile Methodology

 The dictionary meaning of Agile is to be able to move quickly and easily. 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 that
emphasizes the importance of delivering of working product very quickly.
 Agile methodology is a project management approach that emphasizes
continuous improvement and collaboration. It's often used for software
development, and involves breaking projects into phases and following a
cycle of planning, executing, and evaluating.
 Agile breaks the project into smaller modules, each module will be maintained
by team members and deliver those modules in a shorter time to the customer.
This allows a regular feedback loop.
What is Agile Methodology?

 Agile methodologies are iterative and incremental, which means it’s

known for breaking a project into smaller parts and adjusting to changing
requirements.
 They prioritize flexibility, collaboration, and customer satisfaction.
 Major companies like Facebook, Google, and Amazon use Agile because
of its adaptability and customer-focused approach.
Life cycle of Agile Methodology
 Life cycle of Agile Methodology

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:
 Integration Testing: Ensuring that different components work together.
 System Testing: Testing the entire system as a whole.
 User Acceptance Testing: Confirming that the software meets user requirements.
 Performance Testing: Assessing the system’s speed, scalability, and stability.

5. Deployment
 Deploying the software to a production environment.
 Put the software into the real world where people can use it.
 Make sure it works smoothly in the real world.
 Providing training and support for end-users.
6. Review (Maintenance)
 Addressing and resolving any issues that may arise after deployment.
 Releasing updates and patches to enhance the software and address
problems.
 Manifesto for Agile Software Development

The Manifesto for Agile Software Development is a document produced by 17

developers at Snowbird, Utah in 2001. This document consists of 4 Agile Values and 12
Agile Principles. These 12 principals and 4 agile values provide a guide to Software
Developers. The Manifesto for Agile Software Development emerged as a transformative
guide to Software Development.

4 Core Values of the Agile Manifesto:

 Individuals and Interactions over Processes and Tools: Focuses on the importance of effective
communication and collaboration among team members.
 Working Software over Comprehensive Documentation: Prioritizes the delivery of functional
software as the primary measure of progress.
 Customer Collaboration over Contract Negotiation: Encourages customers and stakeholders to
have active involvement throughout the development process.
 Responding to Change over Following a Plan: On changing requirements, embracing flexibility and
ability to adapt even late in the development process.
12 Principles of Agile Manifesto
 12 Principles of Agile Manifesto

1. Customer Satisfaction through Early and Continuous Delivery: This principle concentrates on the importance
of customer satisfaction by providing information to customers early on time and also with consistency
throughout the development process.

2. Welcome Changing Requirements, Even Late in Development: Agile processes tackle change for the
customer’s competitive advantage. Even late in development, changes in requirements are welcomed to
ensure the delivered software meets the evolving requirements of the customer.

3. Deliver Working Software Frequently: This principle encourages the regular release of functional software
increments in short iterations. This enables faster feedback and adaptation to changing requirements.

4. Collaboration between Business Stakeholders and Developers: This says the businesspeople and developers
must work together daily throughout the project. There should be communication and collaboration between
stakeholders and the development team regularly. This is crucial for understanding and prioritizing requirements
effectively.
 12 Principles of Agile Manifesto

5. Build Projects around Motivated Individuals: This promotes in giving developers the environment and support they need and
trusts them to complete the job successfully. Motivated and empowered individuals are more likely to produce work with
quality and make valuable contributions to the project.

6. Face-to-face communication is the Most Effective: Face-to-face communication is the most effective method of discussion
and conveying information. This principle depicts the importance of direct interaction which helps minimize misunderstandings,
and hence effective communication is achieved.

7. Working Software is the Primary Measure of Progress: This principle emphasizes delivering functional and working software as
the primary metric for project advancement. It encourages teams to prioritize the continuous delivery of valuable features, so it
ensures that good progress is consistently achieved throughout the process. The primary goal is to provide customers with
incremental value and also gather feedback early in the project life cycle.

8. Maintain a Sustainable Pace of Work: Agile promotes sustainable development. All people involved: The sponsors,
developers, and users should be able to maintain a constant pace indefinitely. This principle depicts the need for a sustainable
and consistent development pace. This helps in avoiding burnout and ensures long-term project success.
 12 Principles of Agile Manifesto

9. Continuous Attention to Technical Excellence and Good design: This principle is on the importance of
maintaining high standards of technical craft and design, so it ensures the long-term ability in maintenance
and adaptability of the software.

10. Simplicity—the Art of Maximizing the Amount of Work Not Done: Simplicity is essential. The objective here is
to concentrate on the most valuable features and tasks and avoid unnecessary complexity as the art of
maximizing the amount of work not done is crucial.

11. Self-Organizing Teams: Self-organizing teams provide the best architectures, requirements, and designs.
These help in empowering teams to make decisions and organize to optimize efficiency and creativity.

12. Regular Reflection on Team Effectiveness: This makes the team reflect on how to become more effective at
regular intervals and then adjust accordingly. Continuous improvement is very crucial for adapting to
changing circumstances and optimizing the team’s performance over time.
 What are Agile frameworks?

Agile frameworks are methods of organizing and dealing with software program development
initiatives that follow the principles and values of the Agile Manifesto. Agile frameworks intend to
supply value to clients faster and extra often, even also allowing groups to conform to converting
requirements and remarks.

 Types of Agile Frameworks

Kanban
Scrum
Lean
DSDM or Dynamic Systems Development Method ·
XP or Extreme Programming
FDD or Feature Driven Development
Crystal
Scaled Agile Framework (SAFe)
 Agile Methodology Advantage and Disadvantage

 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.
Agile Méthodologies vs Traditional Approaches

Parameters Agile Methodology Traditional Approach

Traditional approaches are like
Agile is like building a flexible and
Definition constructing a house with a
adaptable treehouse in stages.
detailed blueprint.
Testing and development Testing is done once the
Chronology of operations processes are performed development phase is
concurrently. completed.
It follows iterative organizational It follows linear organizational
Organizational structure
structure. structure.
Agile encourages face-to-face Traditional approach encourages
Communication
communication. formal communication.
Number of phases It consists of only three phases. It consists of five phases.
Development cost Less using this methodology. More using this methodology.
Clearly defined user requirements
User requirements Requires interactive user inputs.
before coding.
 Benefits of Agile Methodology

 Immediate Feedback: It allows immediate feedback, which aids software improvement in the
next increment.
 Adapts to Changing Requirements: It is a highly adaptable methodology in which rapidly
changing requirements, allowing responsive adjustments.
 Face-to-Face Communication: Agile methodology encourages effective face-to-face
communication.
 Time-Efficient: It is well-suited for its time-efficient practices, which help in delivering software
quickly and reducing time-to-market.
 Frequent Changes: It effectively manages and accommodates frequent changes in project
requirements according to stakeholder convenience.
 Customer Satisfaction: It prioritizes customer satisfaction.
 Flexibility and Adaptability: Agile methodologies are known for their flexibility and adaptability.
 Limitations of Agile Methodology

 Less Documentation: Agile methodologies focus on less documentation; it prioritizes working on

projects rather than paperwork.
 Challenges in Large Organizations: Busy schedule of clients can make daily meetup and face-to-
face communication difficult.
 Need for Senior Programmers: It may require experienced programmers to make critical decisions
during the development of software.
 Limited Scope Control: It has less rigid scope control, which may not be suitable in certain
situations.
 Predictability: Compared to more structured project management methods, it may lack
predictability.
 Finally

We can conclude that the Agile model is like building a project in small, flexible steps. It’s
about being quick to adapt, working closely with customers, and delivering value in small
doses. This approach has become popular for many companies because it helps them
meet changing needs and make customers happy.
Use the Agile model when your project needs to be flexible, your customers’ needs might
change, and you want to deliver small parts of your project regularly to make them happy.
It’s like building a puzzle piece by piece, adapting as needed.
 Thank You

 Popular Agile Tools for Software Development

Jira
ClickUp
Mural
Kanbanize
GitHub
Monday.com
Jenkins
Shortcut
Asana
Planbox