What is Agile Methodology?

The term "agile methodology" refers to a process that encourages continuous development
and testing throughout the project's software development life cycle. Unlike the Waterfall
paradigm, both development and testing operations are contemporaneous under the Agile
style of software testing.

Agile Methodology Vs. Traditional Software Development

One of the easiest and most successful ways to transform a vision for a company requirement
into software solutions is to use the Agile software development approach. Continuous
planning, learning, improvement, team collaboration, evolutionary development, and early
delivery are all terms used to define agile software development methodologies. It increases
adaptability in the face of change.
The four essential values of agile software development are highlighted.
 Interactions between individuals and groups around processes and tools
 Working software trumps thorough documentation.
 Collaboration with customers is preferred above contract negotiations.
 Adapting to change in accordance with a strategy
This Agile project management tutorial will teach you how to −
 What is Agile Methodology, and how does it work?
 The Waterfall Model vs. the Agile Model
 Scrum
 Backlog of Products
 Scrum Methodologies
 Scrum Methodologies Process Flow:
 Extreme Programming (XP) is a kind of programming that (XP)
 eXtreme programming phases −
 Methodologies for Crystals
 Methodology for Developing Dynamic Software (DSDM)
 Feature-Oriented Design (FDD)
 Software Development using Lean Principles
 Kanban
 Flexible metrics

Waterfall Model vs. Agile Model

Agile and Waterfall models are two distinct approaches to software development. Despite
their differences in approach, both methodologies might be effective at times, depending on
the need and project type.

Agile Model Waterfall Model

Definition of Agile methodology: Agile approaches Waterfall Model − Software development

advocate for an incremental and iterative approach to proceeds in a logical order from beginning to
software development. conclusion.
 Agile Model Waterfall Model

In software engineering, the Agile process is split down The design process is not divided into several
into discrete models that designers work on. models.

Early and regular chances for the client to inspect the The product is only visible to the client after th
product and make decisions and adjustments to the project.
project are provided.

The product is only visible to the client after the project. When opposed to the waterfall paradigm, the
agile model is deemed unstructured.

Because they are so plan-focused, waterfall models are Small undertakings may be completed in a shor
more secure. period. It's tough to predict development time f
huge projects.

It is possible to estimate and finish a wide range of It is possible to correct an error during a projec
projects.

The whole product is only tested at the end. If a The development method is iterative, and the
requirement mistake is discovered or revisions are project is completed in short iterations (2-4
required, the project must be restarted from the beginning. weeks). There is virtually little planning.

The development process is divided into phases, each of Software development takes precedence over
which is substantially larger than an iteration. Each phase documentation.
concludes with a full summary of the next phase.

Documentation is a high responsibility, and it may be There is a testing step for each iteration. It
used to teach employees and update software with the enables regression testing to be implemented
help of another team. whenever new functions or logic are deployed.

After a lengthy implementation period, all of the designed Developers and testers collaborate.
features are supplied all at once.

Separate from the developers are the testers. User acceptance is completed after each sprint.

User acceptance is completed after each sprint. The project's user approval is completed in the
conclusion.

It necessitates strong collaboration with developers, as The developer is not involved in the requireme
well as joint analysis of needs and planning. or planning stages. Normally, there are time ga
between testing and coding.

Agile Process
Agile testing employs a variety of Agile methodologies, which are described below −

Scrum
SCRUM is an agile development methodology that focuses on task management within a
team-based development environment. Scrum is formed from the action that takes place
during a rugby match. Scrum promotes working in small teams and believes in empowering
the development team (say- 7 to 9 members). There are three jobs in Agile and Scrum, and
their duties are as follows −
 Scrum Master
o The master is in charge of organizing the team, holding sprint
meetings, and removing roadblocks to development.
 Owner of the product
o The Product Owner is in charge of creating the product backlog,
prioritizing it, and ensuring that the functionality is delivered at
each iteration.
 Scrum Group
o The team oversees and arranges their work to accomplish the
sprint or cycle.

Backlog of Products
This is a repository for tracking needs, including the number of requirements (user stories)
that must be satisfied for each release. The Product Owner should keep track of it and
prioritize it, and it should be provided to the scrum team. The team may also request the
inclusion, modification, or deletion of a new requirement.

Scrum Methodologies Process Flow

The following is the scrum testing process flow −
 Sprints are the iterations of a scrum.
 A product backlog is a list that contains all of the information needed to create
the final product.
 The top user stories from the Product backlog are chosen and translated into
Sprint backlogs during each Sprint.
 The team works on the sprint backlog that has been established.
 The team double-checks the everyday job.
 The team provides product functionality after the sprint.

Extreme Programming (XP)

When clients' needs or specifications are continually changing, or when they are unsure
about the system's operation, the Extreme Programming approach comes in handy. It
encourages numerous "releases" of the product in short development cycles, which increases
the system's efficiency and provides a checkpoint where any client needs may be quickly
incorporated. The XP creates software with the client in mind.
Stories are used to collect business needs. The parking lot is where all of those tales are kept.
Releases are based on shorter cycles called Iterations, which cover a 14- day time frame
under this technique. Each iteration involves steps like development, unit testing, and system
testing, with each phase resulting in the addition of small or large functionality to the
program.

eXtreme programming phases

In the Agile XP approach, six stages are outlined as follows −

Planning
 Stakeholder and sponsor identification
 Needs for Infrastructure
 Information collecting and security-related information
 Service Level Agreements (SLAs) and their terms
Analysis
 Storytelling in the Parking Lot
 In the parking lot, prioritize the tales.
 Estimation of tales via scrubbing
 Iteration SPAN is a term that is used to describe the number of times a person
(Time)
 Both the Development and QA teams need to arrange their resources.
Design
 Tasks are broken down
 For each job, prepare a test scenario.
 Framework for Regression Automation
Execution
 Coding
 Testing at the unit level
 Manual test scenarios are carried out.
 Generation of a Defect Report
 Regression test cases converted from manual to automated
 Review of the second iteration
 Review at the end of each iteration
Wrapping
 Releases for Small Groups
 Testing for Regression
 Demonstrations and evaluations
 Create new tales depending on the requirements.
 Improvements to the process based on the feedback received after each
iteration
Closure
 Launch of a Pilot Program
 Training
 Launch of the Production
 Guaranteed Service Level Agreement
 Examine your SOA approach.
 Production Assistance
Two storyboards are available to monitor work daily, and they are given below for your
convenience.
 Cardboard Story
 o This is a typical method of storing all of the tales on a board in
the form of stick notes to keep track of daily XP activities.
Switching to an online form is preferable since this manual
process requires more work and time.
 Online Storyboard
o The tales may be saved using the online application Storyboard.
It may be used by several teams for various objectives.

Methodologies for Crystals

Three principles underpin Crystal Methodology.
 Creating a development team, doing a preliminary feasibility study, generating
an initial strategy, and fine-tuning the development technique are all part of the
chartering phase.
 Cyclic delivery − During the primary development period, there are two or
more delivery cycles in which the product is developed.
o The release strategy is updated and refined by the team.
o Through one or more program test integrates cycles, a portion of
the requirements is implemented.
o A fully integrated product is made available to actual
consumers.
o Examining the project strategy and the development technique
used
 Wrap Up − This phase includes activities like as deployment into the user
environment, post-deployment evaluations, and reflections.

Methodology for Developing Dynamic Software (DSDM)

DSDM is an agile project delivery methodology based on the Rapid Application
Development (RAD) approach to software development. The key feature of DSDM is that
users are obliged to participate actively, and teams are given decision-making authority.
With DSDM, the active emphasis shifts to product delivery regularly. DSDM employs a
variety of strategies.
 Time Boxing
 Rules of the MoSCoW
 Prototyping
There are seven stages to the DSDM project.
 Pre-project
 Study of Feasibility
 Business Research
 Iteration of the Functional Model
 Iteration on design and construction
 Implementation
 Post-project

Feature-Oriented Design (FDD)

This strategy focuses on "developing and constructing" features. Unlike other Agile software
engineering methodologies, FDD outlines highly precise and brief stages of work that must
be completed independently for each feature. Domain walkthrough, design inspection,
promote to build, code inspection and design are all part of it. FDD creates products with the
following criteria in mind.
 Modeling of Domain Objects
 Feature-based development
 Ownership of Components and Classes
 Teams to Watch
 Inspections
 Management of Configuration
 Regular Structures
 Progress and outcomes are shown.

Software Development using Lean Principles

The "Just in Time Production" premise underpins the lean software development process. Its
goal is to speed up software development while lowering costs. The process of lean
development may be broken down into seven parts.
 Waste Reduction
 Enhancing learning
 Postpone your commitment (deciding as late as possible)
 Delivery on time
 Increasing the team's autonomy
 Increasing Integrity
 Optimize the whole process.

Kanban
Kanban is a Japanese term that refers to a card that contains all of the information required to
complete a product at each step of its journey to completion. This framework or approach is
widely used in software testing, particularly in Agile methodologies.

Kanban vs. Scrum

The following table highlights the major differences between Kanban and Scrum −

Scrum Kanban

Tests must be split down in scrum method so that No specific item size is required.
they may be performed in one sprint.

Prescribes a product backlog that is prioritized. Prioritization is not required.

For each iteration, the Scrum team commits to a Commitment is a choice.

certain amount of work.
 Scrum Kanban

The use of a burndown chart is required. No specific item size is required.

A scrum board is reset after each sprint. A Kanban board is tenacious. It restricts the number o
things that may be in the workflow state.

It is not possible to add things to an ongoing It can add objects as capacity allows.
iteration.

Indirectly, WIP is restricted. WIP is very restricted.

Iterations with a set time limit are required. Iterations with a time limit are an option.

Metrics for Agile

The following are some metrics that may be gathered to ensure that Agile is used effectively
−
 Factor of drag
o Hours of effort that do not contribute to the sprint objective
o Reduce the number of shared resources and the amount of non-
contributing activities to improve the drag factor.
o New estimates may be enhanced by a percentage of the drag
factor, as follows: New estimate = (Old estimate+drag factor)
 Velocity
o The number of backlog items (user stories) that have been
turned into sprint-ready functionality.
 The number of unit tests that have been introduced has increased.
 The time it takes to finish a daily build
 Bugs discovered in a prior version or earlier iterations
 Leakage of production defects