AGILE

Training Material

1
 TABLE OF CONTENTS

CHAPTER 1: WHAT IS AGILE ....................................................... 3

CHAPTER 2: HOW DOES IT WORKS ............................................... 4
CHAPTER 3: WHY WE USE AGILE METHODS ................................. 5
ADVANTAGES OF AGILE MODEL .................................................. 5
DISADVANTAGES OF AGILE MODEL ............................................. 6
WATERFALL VS AGILE ............................................................... 6
CHAPTER 4: AGILE MANIFESTO .................................................. 7
CHAPTER 5: AGILE METHODOLOGIES .......................................... 8
CHAPTER 6: SCRUM .................................................................... 9
SCRUM ELEMENTS-ROLES .......................................................... 10
PRODUCT OWNER....................................................................... 10
SCRUM MASTER ......................................................................... 11
SCRUM DEVELOPMENT TEAM ..................................................... 11
CHAPTER 7: THE PROCESS .......................................................... 12
7.1 PROCESS............................................................................... 13
7.2 SPRINT PLANNING MEETING .................................................. 13
7.3 SPRINT ................................................................................. 14
SPRINT PLANNING ...................................................................... 14
PARTS OF SPRINT PLANNING MEETING ......................................... 15
DIFFERENCE BETWEEN PRODUCT BACKLOG & SPRINT BACKLOG. 15
PRE-PROJECT/KICK OFF MEETING ................................................ 17
7.4 DAILY SCRUM ...................................................................... 17
7.5 SPRINT REVIEW MEETING ..................................................... 17
CHAPTER 8: SCRUM ARTIFACTS .................................................. 17
PRODUCT BACKLOG ................................................................... 18
SPRINT BACKLOG ....................................................................... 18

2
 Chapter 1: What is Agile
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 utilize spry since of its
flexibility and customer-focused approach.

A awesome bargain has been composed approximately Spry. Much of

that composing is about things—tools, forms, strategies, advances, stages,
enormous information and the like.
While the 2015 Learning Consortium Venture found that these things
are important, people are more important—the objectives that individuals try
to, the mentality through which they get it how the world works, the way they
work together, the values that they share, and way in which they communicate
with each other. As the Dexterous Pronouncement itself said, people and
intelligent are esteemed more than instruments and forms. Without the
Dexterous mentality, instruments and forms accomplish small.

3
 Chapter 2: How does it works
The Agile methodology is a venture administration approach that
includes breaking the venture into stages and emphasizes ceaseless
collaboration and enhancement. Groups take after a cycle of arranging,
executing, and evaluating.

The taking after eight characteristics are continuously portion of the

culture of effective spry companies.
 Early and visit conveyance of working item increments
 Ongoing assessment and prioritization of work to maximize value
 Limiting work in progress
 Emergent engineering sponsored with computerized testing
 Empowered, cross-functional teams
 Transparency
 Close collaboration between clients and developers
 Safety, as a prerequisite

4
 Chapter 3: Why we use Agile methods
Agile methodologies are used in software development for a variety of
reasons, including: The Dexterous strategy is a venture administration
approach that includes breaking the extend into stages and emphasizes
ceaseless collaboration and enhancement. Groups take after a cycle of
arranging, executing, and evaluating.
Agile techniques are utilized in program advancement for a assortment
of reasons, counting:
 Adaptability: Agile strategies permit groups to rapidly alter procedures
without disturbing the extend stream.
 Customer fulfillment: Agile strategies center on client fulfillment and
conveying high-quality items.
 Communication: Spry techniques move forward communication between
improvement groups and item proprietors.
 Risk decrease: Dexterous techniques offer assistance diminish hazard by
conveying ventures in stages, which permits for early location and
determination of issues.
 Efficiency: Spry techniques utilize shorter advancement cycles, which can
lead to speedier item discharges.
 Flexibility: Dexterous strategies empower companies to convey adaptable
and versatile computer program improvement.
 Timeliness: Dexterous strategies offer assistance guarantee that
improvement groups total ventures on time and inside budget.

Advantages of Agile model:

The Agile methodology has many advantages, including:
 Customer satisfaction: Product owners are involved and center on client
fulfillment and conveying high-quality item.
 Increased collaboration: Agile encourages collaboration between team
members, stakeholders, and customers. This helps ensure that the final
product meets the needs of the end user.
 Adaptability: Agile is flexible and can adapt to almost any situation or
process. This makes it a good fit for the evolving market.
 Continuous improvement: Agile teams regularly evaluate their processes
and make adjustments to improve quality, efficiency, and customer
satisfaction.
 Continuous delivery: Agile software development can deliver high-
quality products in less time by combining continuous delivery with
continuous pretesting.
 Flexibility: Agile's flexible working model helps eliminate the possibility
of project failure by ensuring that there is always a working product.

5
Disadvantages of Agile model:
The Agile model has some disadvantages, including:
 Less predictable: The flexibility of Agile can make it less predictable.
 Poor resource planning: It's hard to predict the cost, time, and resources
required for a project because the end result isn't known from the start.
 Limited documentation: Documentation is often created "just in time"
for building the output, and may not be comprehensive.
 Fragmented output: Incremental delivery can lead to fragmented output
because teams work on each component in different cycles.
 Scope creep: Scope creep is a major obstacle for Agile.
 High demands on time: Agile can be time consuming.
 Unsuitable for long-term projects: Agile may not be the best
methodology for long-term projects.
 Teams can get sidetracked: Lack of processes can cause teams to get
sidetracked.
 Collaboration can be difficult: Maintaining the level of collaboration can
be difficult.
 Continuous testing: Users are required to test on an almost continuous
basis.
 Continuous involvement of stakeholders: Continuous involvement of all
stakeholders can be a challenge at times

Waterfall Vs Agile

6
 Chapter 4: Agile Manifesto
The Agile Manifesto is a set of directing values and standards for
dexterous program advancement. It was made by a gather of program
designers in 2001 to make strides and streamline the program advancement
prepare. Here’s a outline of the center values and standards:

Agile Manifesto Values

 People and intuitive over forms and tools

 Emphasize the significance of viable communication and cooperation over
strict adherence to apparatuses and processes.
 Working computer program over comprehensive documentation
 Prioritize conveying useful program that meets users' needs over making
broad documentation.
 Client collaboration over contract negotiation
 Center on working closely with clients to get it and meet their needs or
maybe than staying inflexibly to contract terms.
 Responding to alter over taking after a plan
 Grasp and adjust to changes indeed late in advancement or maybe than
entirely taking after an starting arrange.

Agile Manifesto Principles

 Client fulfillment through early and persistent conveyance

 Convey profitable computer program early and routinely to keep clients
satisfied.
 Welcome changing requirements
 Be adaptable and open to changing necessities at any arrange of
development.
 Provide working program habitually
 Provide useful computer program in brief cycles to give esteem and get
feedback.
 Trade individuals and engineers must work together day by day
 Advance collaboration between commerce partners and advancement
groups.
 Construct ventures around spurred people make an environment that
persuades and bolsters group members.
 Face-to-face discussion is the most efficient Incline toward face-to-face
communication for the most compelling data exchange.
 Working computer program is the essential degree of progress. The victory

7
 of the venture is decided by the conveyance of working software.
 Feasible development-Keep up a steady pace and dodge burnout for
progressing productivity.
 Ceaseless consideration to specialized brilliance and great plan
 Center on progressing specialized hones and plan to improve quality.
 Simplicity—the craftsmanship of maximizing the sum of work not done—
is essential .Keep the work as straightforward as conceivable by centering
as it were on what is necessary.
 The best designs, prerequisites, and plans rise from self-organizing teams.
Permit groups to organize themselves to deliver the best outcomes.
 Frequently reflect on how to ended up more successful
 Occasionally audit and alter group hones to move forward proficiency and
viability.

These values and standards offer assistance groups to be more versatile,

collaborative, and centered on conveying esteem all through the advancement
prepare.

Chapter 5: Agile Methodologies

Agile methodology is a extend administration system that includes
breaking ventures into stages, or sprints, and emphasizes nonstop
collaboration and change. It's an umbrella term for numerous sorts of
administration techniques, counting Scrum, Kanban, and Extraordinary
Programming (XP).

Here are a few key characteristics of Dexterous strategy:

 Iterative: Groups reflect and alter their methodology after each sprint.
 Adaptable: Dexterous is a mentality that can be utilized by any group.
 Values: Dexterous is based on four primary values: people over forms
and apparatuses, working computer program over comprehensive
documentation, client collaboration over contract arrangement, and
reacting to alter over taking after a arrange.
 Benefits: Spry techniques can lead to more prominent efficiency, group
arrangement, diminished hazard, speedier time to showcase, and higher
quality program.
Agile strategy was presented to overcome the issues of the waterfall
show, where the whole item is treated as a single unit. Spry breaks the whole
item handle into micro services or stages, which makes it speedier to execute
and convey changes.

8
 Chapter 6: Scrum
Scrum is a system for overseeing work that's regularly utilized in
program advancement, but can be connected to any kind of cooperation. It's a
set of parts, devices, and gatherings that offer assistance groups work together
to accomplish a common objective. Scrum is based on the thought of a rugby
scrum, where the group works together to move the ball forward.
Here are a few key viewpoints of Scrum:
 Sprints: Work is broken into objectives that are completed inside time-
boxed cycles called sprints, which are more often than not two weeks long.
 Self-organization: Scrum empowers groups to self-organize and learn
from their encounters. 
 Inspection: Groups routinely audit the advance of a extend to recognize
issues and make advancements. 
 Roles: Scrum incorporates parts such as the Item Proprietor, who orders
work into a Item Accumulation, and the Scrum Ace, who cultivates an
environment for the group to work in. 
 Adaptability: Scrum permits groups to adjust to alter and learn from their
encounters.
 Flexibility: Scrum gives structure and craved results, but clears out groups
room to choose how to accomplish them. 

9
Scrum Elements-Roles

Product Owner

A item proprietor is a part that's capable for maximizing the esteem of

a item. They are a key part of the item administration group and are dependable
for the taking after:
Defining the item vision
 The item proprietor makes a vision for the item based on advertise inquire
about and client and partner needs. 
Managing the item backlog
 The item proprietor makes and prioritizes a list of highlights and
prerequisites for the item excess. They refine the excess based on input and
changing trade needs.
Collaborating with teams
 The item proprietor works closely with cross-functional groups, such as
designers, originators, marketers, and quality affirmation. They encourage
communication between the group and clients and partners. 
Evaluating and observing progress
 The item proprietor compares the product's conveyance against the
anticipated conveyance. They take remedial activity if the group is behind
plan.

Making decisions
 The item proprietor makes choices almost trade-offs, arrange, and scope.
Being a client advocate
 The item proprietor is the essential client advocate for the group and
guarantees that the team's accumulation adjusts with client needs.
Being a leader

10
 The item proprietor motivates and spurs cross-functional groups to
cultivate collaboration and advancement 

Scrum Master

A Scrum Ace is a pioneer who makes a difference a group utilize

Dexterous venture administration to take after the Scrum system. They are
mindful for:

 Facilitating communication: Scrum Experts offer assistance guarantee

that the group and administration communicate and collaborate well. 
 Coaching and directing: They offer assistance the group learn the Scrum
system and its standards, values, and hones. 
 Removing hindrances: They offer assistance the group center on getting
work done by evacuating hindrances.
 Encouraging self-organization: They offer assistance the group gotten to
be self-reliant and engaged to make choices.
 Serving as a part show: They coordinated Scrum concepts into their
obligations and serve as a part demonstrate for others. 
 Asking capable questions: They inquire questions to reveal what's basic,
at that point direct others to tap into their information and ability. 

Scrum Experts are regularly people-oriented and appreciate making a

difference group individuals develop and progress. They are committed to the
Scrum strategy, dexterous standards, and best hones.

Scrum Development team

11
 In Scrum, the improvement group is a cross-functional and self-
organized gather of individuals who work together to convey a item increase.
The improvement team's duties incorporate:

Delivering products
The improvement group is dependable for conveying shippable items
inside the project's time increases.
Working collaboratively
The advancement group works together without a chain of command or
person titles.
Prioritizing quality
The advancement group prioritizes quality confirmation to guarantee
that the program meets guidelines and capacities as anticipated.
Estimating advancement time
The improvement group gauges how long it will take to total a client
story.
Meeting daily
The advancement group is portion of a scrum group, which too
incorporates a item proprietor and a scrum ace. The perfect estimate for a
advancement group is between 3 and 9 individuals, not counting the scrum ace
and item proprietor.
A scrum group needs three particular parts: item proprietor, scrum ace,
and the improvement group. And since scrum groups are cross-functional, the
advancement group incorporates analyzers, creators, UX masters, and ops
engineers in expansion to designers.

Chapter 7 The Process

The Process includes

 Sprint Planning meeting

 Sprint
 Daily Scrum and
 Sprint Review Meeting

12
Chapter 7.1 Process:

Chapter 7.2 Sprint Planning Meeting

A sprint arranging assembly is a Scrum ceremony that happens some

time recently a sprint to choose what work will be completed and how. The
assembly makes a difference set desires, characterize the accumulation, and
give structure.
Here are a few things that happen amid a sprint arranging assembly:

 Set the sprint objective: The group chooses on the generally key objective
for the sprint.
 Review the accumulation: The group surveys the item excess and
chooses which things to incorporate in the following sprint. 
 Discuss capacity: The group examines the team's capacity, counting
working hours, time off, and commitments.
 Assign errands: The group relegates errands to group individuals based
on expertise sets and capacity. 
 Estimate time outlines: The group gauges how long each errand will take.
 Agree on what "done" looks like: The group concurs on what it implies
for each thing to be "done". 
 Determine speed: The group employments speed to foresee how much
work they can do in future sprints.
 Account for outside components: The group considers outside
components that may influence the sprint. 
The scrum ace organizes the assembly, making beyond any doubt the
group is arranged and the assembly room is booked.

13
Chapter 7.3 Sprint

 A month-long emphasis, amid which is augmented a item functionality

 NO exterior impact can obstructions with the scrum group amid the sprint
 Each sprint starts with the every day scrum assembly

Sprint Planning

Sprint planning is a assembly where a Scrum or Spry group plans the

work to be done amid a sprint:
 Define the sprint objective: The group chooses and refines a sprint
objective to reflect the work that will be done. 
 Select excess things: The group chooses the item excess things to work
on amid the sprint.
 Plan how to total the work: The group talks about how to actualize the
chosen excess things. 
 Identify potential challenges: The group examines specialized and plan
perspectives of the sprint errands, and distinguishes any potential
challenges or conditions.
 Determine capacity: Group individuals give data almost their
accessibility and how much time they can commit to the sprint.
 Create a shared understanding: The group clears out the assembly with
a shared understanding of the work, why it's vital, and how it will be
completed.
Sprint planing is a key portion of the Agile strategy. Sprints are ordinarily 2–
4 weeks long, but groups can characterize shorter or longer sprints based on
their needs. The objective of breaking down a venture into sprints is to provide
working highlights more as often as possible, get client criticism speedier, and
make changes rapidly.

14
Parts of Sprint Planning Meeting

1st Part:

 Creating Product Backlog

 Determine the Sprint Goal
 Participants: Product Owner, Scrum Master, Scrum Team

2nd Part:

 Participants: Scrum Master, Scrum Team

 Creating Sprint Backlog

Difference between Product Backlog & Sprint Backlog

The Item Excess and the Sprint Accumulation are two vital components
in Scrum, a well known Dexterous system for overseeing and conveying
ventures. Whereas they are related, they serve diverse purposes:

Product Backlog:
Definition: The Item Accumulation is a energetic, requested list of all the work
that needs to be done on the item. It incorporates highlights, bug fixes,
specialized advancements, and any other work required to move forward the
product.
Ownership: The Item Proprietor is capable for overseeing and prioritizing the
Item Backlog.
Content: It contains high-level things or "Item Excess Things" (PBIs) such as
client stories, errands, and specialized requirements.
Prioritization: Things are prioritized based on commerce esteem, client needs,
and other components. The most important things are at the best of the
backlog.

15
Scope: The Item Accumulation is a living archive and advances as unused data
is found and the extend progresses.

Sprint Backlog:
Definition: The Sprint Accumulation is a subset of the Item Accumulation that
the group commits to completing amid a particular Sprint (a time-boxed cycle,
as a rule enduring 2-4 weeks).
Ownership: The Scrum Group is mindful for overseeing the Sprint Excess, but
it is guided by the Scrum Ace and the Item Owner.
Content: It incorporates the Item Excess Things chosen for the Sprint, along
with a point by point arrange for conveying those things, frequently broken
down into tasks.
Prioritization: The things are chosen and organized amid Sprint Arranging,
based on the team's capacity and the need set by the Item Owner.
Scope: The Sprint Excess is settled for the length of the Sprint, in spite of the
fact that the group may alter errands as essential to meet the Sprint Goal.

Key Differences
1. Scope and Purpose:
Item Excess: Contains all the work required for the whole item. It's wide and
advances over time.
Sprint Excess: Centers on the work arranged for the current Sprint. It’s a point
by point arrange for the quick iteration.
2. Time frame:
Item Accumulation: Long-term and continuous; things can be included,
evacuated, or re prioritized at any time.
Sprint Accumulation: Short-term; settled for the length of the Sprint.
3. Proprietorship and Management:
Item Excess: Overseen by the Item Owner.
Sprint Accumulation: Overseen by the Scrum Group, in spite of the fact that
it’s impacted by the Item Owner’s priorities.
4. Flexibility:
Item Accumulation: Adaptable and ceaselessly updated.
Sprint Excess: Less adaptable once the Sprint begins; changes are made as it
were if completely necessary.

Understanding these contrasts makes a difference in keeping up clarity and

center all through the Scrum handle, guaranteeing that both the long-term
vision and the short-term objectives are successfully overseen.

16
Pre-Project/Kickoff Meeting

A special form of Sprint Planning Meeting

Meeting before the begin of the Project

Chapter 7.4 Daily Scrum

Chapter 7.5 Sprint Review Meeting

 Is held at the end of each Sprint

 Business functionality which was created during the Sprint is
demonstrated to the Product Owner
 Informal, should not distract Team members of doing their work
Sprint meetings are time boxed to a most extreme of four hours for a one-
month sprint. For shorter sprints, sprint surveys can be finished in an hour or
two. The sprint audit assembly is intentioned kept exceptionally casual,
ordinarily without slides and with negligible planning time for the assembly.
Sprint audits ought to not gotten to be a diversion or noteworthy reroute for
the group; or maybe, they should be a normal result of the sprint.

Chapter 8 Scrum Artifacts

Agile scrum artifacts are data that a scrum group and partners utilize to
detail the item being created, activities to deliver it, and the activities
performed amid the extend. The primary spry scrum artifacts are
 Product Backlog
 Sprint Backlog
 Burn down Charts

17
Product Backlog

The Item Accumulation is a prioritized list of all the work that needs to be
done on the item. It incorporates highlights, upgrades, fixes, and other
necessities that contribute to the product’s in general goals.
 Requirements for a framework, communicated as a prioritized list of
Excess items
 Is overseen and possessed by a Item Owner
 Spreadsheet (typically)
 Usually is made amid the Sprint Arranging Meeting
 Can be changed and re-prioritized some time recently each PMI

Dynamic: It advances as unused necessities rise and needs alter. It is

persistently upgraded by the Item Owner.
Ordered: Things in the Item Accumulation are prioritized based on their
esteem, chance, and conditions. The most important things are regularly at the
top.
Detailed Fittingly: Things at the beat of the accumulation are ordinarily more
point by point than those lower down, as they are closer to being worked on.
Product Excess Things (PBIs): Particular passages in the excess, such as
client stories, bug fixes, specialized work, or information securing
assignments.

Sprint Backlog
The Sprint Accumulation is a subset of the Item Excess chosen for a
particular Sprint. It incorporates all the assignments and Item Accumulation
Things (PBIs) that the group commits to completing amid the Sprint.
 No more than 300 errands in the list
 If a errand requires more than 16 hours, it ought to be broken down
 Team can include or subtract things from the list. Item Proprietor is not
permitted to do it

Time-boxed: The Sprint Accumulation is particular to a Sprint and is settled

once the Sprint starts, in spite of the fact that minor alterations can be made as
needed.
Detailed Arrange: It frequently incorporates a arrange for how the chosen
PBIs will be conveyed, broken down into significant tasks.
Owned by the Scrum Group: The group is capable for overseeing and
upgrading the Sprint Accumulation all through the Sprint.
Sprint Excess Things: The PBIs chosen for the Sprint.
Tasks: Particular work things or assignments required to total the Sprint
AccumulationThings.

18
19