What is Agile?

Why Agile is
Used?
What are Agile

Overview on Agile Methodology

Values?
Overview What are Agile
Principles?

on What is Scrum?

Agile Methodology Agile Vs Scrum

Scrum Framework
or Process
Key Concepts in
Scrum

Spring Planning
•All Stakeholder will join (SM,
PO, Developers, Analysts &
Testers)
•Using Planning Poker will do
Story Points Estimation
•Estimation Technique Used is
Fibonacci series (3,6,8 & 13)
•Capacity Planning (# of Days
that resource is available for
that sprint)
•Velocity (# of user stories
planning for that Sprint)
Daily Scrum
• What did you do yesterday?
• What will you do today?
• Are there any impediments or
Blockers?
Agile/Scrum Process
Sprint Review
• Demo Features to All
• To showcase completed work
• Discussion about the
Incomplete ones
• Discussion about any
additional changes needed
Sprint Retrospective
•What Went Well?
•What didn't Well?
•What couldn't have been
Improved?
•Action Items
Backlog Grooming sessions
•Product Owner will drive this
meeting
•Discussion about Product
Backlogs
•Review and prioritize the
Product Backlogs
•Ensure that backlog items are
prepared for upcoming
sprints.
Scrum of Scrum
•Multiple scrum teams
meeting together
•Discussion about overall
project goal of all teams is
met
•Identify Dependencies and
problem resolution while
focusing on coordination
between teams
Sprint Demo
•Conducted at the end of the
sprint
•Each Scrum Team will present
the Features developed
•Opportunity to get feedback
and receive questions from
other team members
1. What is Agile?
The Agile model adopts Iterative or Incremental development. Each incremental part is
developed over an iteration (Sprint). Each iteration (Sprint) is intended to be small and easily
manageable and can be completed within a couple of weeks only. At a time one iteration is
planned, developed, Tested and deployed to the customers

2. Why Agile is Used?

The Agile process consists of short, time-boxed iterations known as sprints. Each sprint
delivers the working product/application/requirement. The success of this methodology relies
on shorter iterations and also on collaboration amongst the team that is hard to find in
traditional methodologies.
3. What are Agile Values?
The four values of the Agile Manifesto
• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation.
• Responding to change over following a plan.

4. What are Agile Principles?

The below are the 12 principles outlined in the Agile Manifesto:

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
2. Welcome changing requirements, even late in software development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software/product/application/component/Feature/Functionality frequently, from a couple of weeks to a couple of months, with a preference to the
shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity–the art of maximizing the amount of work not done–is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
5. What is Scrum? (iv). When we should use Scrum?
Scrum is a framework that helps teams work together. Scrum is an Agile methodology
Scrum is excellent for dealing with complex projects in
that is designed to develop products in an environment susceptible to change.
changing environments.
In Scrum, delivery cycles are called “sprints,” and generally last one to four weeks.

(i) What are Scrum Pillars?

Scrum is built on three pillars:

Transparency: All players involved have complete access to information, including progress and goals.
Adaptation: The project and work can change to mirror new priorities.
Inspection: The team strives to continuously improve the product and the process.

(ii). What are Scrum Values?

Below are the five values of Scrum:
• Courage
• Focus
• Commitment
• Respect
• Openness

(iii). What are 6 Principles of Scrum?

• Control over the empirical process. In Scrum, the empirical process is based on observation
of hard evidence and experimentation rather than theory. ...
• Self-organization. ...
• Collaboration. ...
• Value-based prioritization. ...
• Time-boxing. ...
• Iterative development.
7. Agile Vs Scrum?
The key difference between Agile and Scrum is that while Agile is a project management
philosophy that utilizes a core set of values or principles, Scrum is an Agile methodology
that is designed to develop products in an environment susceptible to change.
8. Scrum Framework or Process?
Scrum is an Agile methodology that is designed to develop products in an environment susceptible to change.
• Scrum Team
• Scrum Team Roles and Responsibilities
• Sprint Ceremonies
• Scrum Artifacts

8.1 Scrum Team

The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team
consists of one Scrum Master, one Product Owner, Developers, Analysts & Testers. Within a
Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals
focused on one objective at a time, the Product Goal.

8.2 Scrum Team Roles & Responsibilities

(i). Scrum Master: The scrum master helps to facilitate scrum to the larger team by
ensuring the scrum framework is followed. He/she is committed to the scrum values and
practices, but should also remain flexible and open to opportunities for the team to improve
their workflow.

Roles & Responsibilities:

• Coach team members

• Host daily stand-up meetings
• Assist the product owner with the product backlog
• Remove roadblocks/Blockers/Impediments
• Teach Scrum practices and principles
• Publishing Sprint Metrics
(ii). Product Owner: The product owner supports the development team by
prioritizing the product backlog and creating user stories. They serve as an internal customer
expert for engineering and development teams, answering questions and clarifying
requirements.
Roles & Responsibilities:
• Ensures user stories are “ready” for development to start work.
• Ensures each story has the correct acceptance criteria.
• Gathers, manages, and prioritizes the product backlog.
• Ensures close collaboration with the development team.
• Has technical product knowledge or specific domain expertise.
• Contributes to the work of the Product Manager as they define a product
differentiation strategy.
• Tracks progress towards the release of a product.
(iv). Analyst: The BA guides the team, helps them to understand the requirements, and
even at times has to approve the implementation and is an important participant in the
brainstorming sessions when the team meets to discuss the upcoming sprint’s backlog.
Roles & Responsibilities:
• Grooming the product backlog based on the prioritization provided by the
product owner.
• Analysing the customer needs and finding the solutions to address them.
• Creating the requirements in the form of User Stories with appropriate
Acceptance criteria and Business Rules to meet the user story functionality.
• Working with the product owner and the stakeholders to understand the scope,
suggest improvements to the requirements, etc.
• Reviewing Test Scenario's or Test cases or Execution results created by Testers
and providing review comments
(iii). Developer: The key responsibilities of the Development Team is to perform work
sprints as per the requirements provided by the Product Owner and coordinated by the
Scrum Master.
Roles & Responsibilities:
• Achieve the goals defined for each sprint
• Attend daily scrum meetings reporting the planned tasks for each day
• Assure to Product Owner and Scrum Master that the allocated work is being
performed as planned
• Provide inputs on the creation of User Stories to the Product Owner
• Understand the User Stories
• Estimate User Stories approved by the Product Owner
• Commit User Stories to be done in a sprint and develop the list of tasks based on
the User Story
• Report to the Scrum Master impediments to the progress of the project, if any
• Update Burndown Chart, Scrum Board, and Impediment Log
• Submit Change Requests, if any
• Participate in Prioritized Product Backlog Review Meetings
• Identify improvement opportunities, if any, from the current Sprint and agree on
any possible improvements for the next Sprint
• Participate in the Retrospect Project Meeting
(v). Tester: QA is a person who verifies the requirements by testing 6.3 Sprint/Scrum Ceremonies: A sprint employs below different scrum
it. Hence the Business Analysts / Stakeholders / Product Owners are ceremonies to ensure proper execution:
very eager to know about the feedback of a QA. The involvement of a
BA in testing is little more than what it is in development. o Sprint Planning
o Daily Scrum
Roles & Responsibilities: o Sprint Review
o Sprint Retrospective
• Analysing the requirements very deeply and point out the o Backlog Grooming Sessions
gaps in review meetings/brainstorming sessions etc. o Scrum of Scrum
• Attending Spring Planning meetings and Estimate Story points o Sprint Demo
• Attending Daily stand up’s
• Participating in Requirement walkthrough calls with Scrum
Team Backlog
• Once the Sprint Planning is done creating Testing tasks with Spring
Planning
Daily Scrum Sprint Review
Sprint
Retrospective
Grooming
Scrum of
Scrum
Sprint Demo
sessions
Estimated Hours
• Creating Test Scenario , Test cases and Execution Results
scheduling review calls with Analysts and Development team (i). Sprint Planning: In sprint planning, the entire scrum team decides below:
for feedback o Estimates Story points- Used Planning Poker tool for Estimation and Used
• Working on incorporating review comments based on the estimation technique as Fibonacci (i.e. 3-Low,5-Medium,8-High & 13-Critical
feedback received in the review calls story points)
• Reporting Blockers or Impediments to Scrum Master if o Discussion on Product & Sprint Backlogs:
anything halting execution activities Product Backlogs: Product Backlog contains all the items in the software
• Setting up Bug Triage calls based on the Need basis with
development project.
Analysts & Developers
Sprint Backlogs: Sprint Backlog contains only the items of the Backlog
• Attending below Sprint Ceremonies or Scrum Events
specific to the current Sprint
o Sprint Planning
o Capacity Planning- Capacity planning is to estimate the Scrum team's
o Daily Scrum
capacity for the work which can be accomplished in the sprint
o Sprint Review
Formula: Number of team members multiplied by number of days in the sprint
o Sprint Retrospective
multiplied by number of productive hours in a day. (5-Team Members*15-days*8
o Scrum of Scrum
hours per day)
o Backlog Grooming Sessions
o Velocity - Velocity is based on actual story points completed, which is
o Sprint Demo
typically an average of all previous sprints.
(ii). Daily Scrum or Daily Stand-up: The Daily Scrum is a 15-minute time-boxed event on daily
basis and below are the some discussion points during Daily Scrum: 6.4 Sprint/Scrum Artifacts:
Below are the list of Sprint/Scrum Artifacts delivered at the End of the
• What did you do yesterday? Sprint:
• What will you do today?
• Are there any impediments/blockers/Issues in your way?
i. Product Backlogs
(iii). Sprint Review: ii. Sprint Backlogs
iii. Sprint Metrics- Below are the Sprint Metrics:
• To showcase completed work o # of story points completed
• Scrum where the team gathers to review completed work and determine whether additional o Burn-up- burn-up chart shows how much work has been completed
changes are needed and the total scope of the project.
• User stories - To confirm which stories can be set to complete and what to do with the o Burn-down chart- A burn-down chart shows the amount of work
incomplete ones remaining on a project (the remaining effort)
o # of Defects Reported
(iv). Sprint Retrospective: The sprint retrospective is a recurring meeting held at the end of a
sprint used to discuss what went well during the previous sprint cycle and what can be o Defects Leakage (the bugs which are missed during the sprint
improved for the next sprint. by the Testing team)

o What went well (keep doing these things)

o What could be improved (went OK, but could be better)
o What went badly (don't do these things again)
o Focus for next period/sprint/month/quarter (One or two things to focus on)
(v). Backlog Grooming Sessions: Grooming (or refinement) is a meeting of the Scrum team in
which the product backlog items are discussed and the next sprint planning is prepared.

(vi). Scrum of Scrum: Scrum of Scrums is a scaled Agile technique that offers a way to connect
multiple teams who need to work together to deliver complex solutions. The goal of the Scrum
of Scrums meeting is rather to make sure the individual teams make their sprint goals.

(vii). Sprint Demo: A sprint demo is when a completed product backlog item is demonstrated
in discussion between the Scrum team and other sprint review participants.
8.3 Key Concepts in Scrum:
Below are the some of the Key Concepts in Scrum:
Sprint: A sprint is a short, time-boxed period when a scrum team works to complete a set amount of work.

Epic: Epics can be broken down into specific pieces of work, called Features. These are based on the needs and requests of customers or end
users and is sized or split as necessary to be delivered by the Agile teams.

Who will Create Epics?- A product owner is responsible for writing Agile epics by discussing with stakeholders, such as clients and investors, to
ensure it satisfies the required needs.

Features: Features represent parts of the product that bring significant value to its users. Features are usually too big to big worked on directly
so they are broken down into smaller business units: stories.

Who will Create Features?- A product owner is responsible for writing Agile Features

User Stories: A user story is the smallest unit of work in an agile framework. It contains Acceptance Criteria & Business Rules (i.e. Requirements)
and they are written from the perspective of an end user or user of a system.

Who will Create User Stories?- Analysts with the help of Product Owner and below are the 3C’s need to be noted in the User Stories:

Tasks: A task represents work that needs to be done by the Scrum Team Members to on the User Story.
Who will Create Tasks?-

Analysts will create Analysts Tasks

Developer will create Developer Tasks
Tester will create Testing Tasks (Ex: Analysis, Test Design, Test Execution, Test Data Setup, Reviews etc..)

Story Point: A story point is a metric used in agile project management and development to estimate the difficulty of implementing a given user
story.
What is hardening of sprint? Hardening Sprint is defined as a sprint focused on “catching up” on technical test debt and readying a Scrum-
produced release. In this case, it typically focuses on completing testing activities such as integration, system, and full regression testing.
Frequently it includes some final defect repairs as well.

What is Acceptance Criteria? Acceptance criteria refer to a set of predefined requirements that must be met the scope and requirements of
user stories.

Business Rule: Business rules define behavior or expected result of the Acceptance criteria.