AGILE METHODOLOGY

Agenda:

▪ What is agile?
▪ What are the principle of agile?
▪ What is agile testing?
▪ Types of agile methodologies?
▪ What is Scrum methodologies?
What is Agile?

► It is a standard procedure or step by step

procedure to develop the new software
► It is a Iterative and incremental Approach
PRINCIPLE OF AGILE METHODOLOGY

► The main goal of agile is customer satisfaction by quick

delivery of working software.
► Customer can change the requirement at any point of
development stage
► Release should be short
► There will be good communication between customer,
Product owner, developer and Test Engineer
► Developers and test engineers will be doing lot of meetings
at regular intervals in order to improve the quality of
process
What is agile testing?

► Testing the software by following the principle of agile

methodology is called agile testing
Types of agile methodologies?

► 1. Scrum methodologies
► 2. XP (Extreme Programming)
► 3. FDD (Feature driven development)
► 4. Crystal Clear
► 5. Lean and Kanban
► 6. ASDM (Adoptive software development method)
► 7. DSDM (Dynamic Software Development method)
Terminologies:
• Release
• EPIC
• User stories/stories/story card
• Story point
• Sprint
• Bug triage meeting
• Product Backlog meeting:
Scrum Events/Ceremonies

• Sprint planning.
• Daily stand-up.
• Sprint review.
• Sprint retrospective.
Scrum methodologies/Scrum Process:
Release: Combination of sprints is called release
EPIC: It is a larger requirement. Epics need to be broken into smaller
deliverables (stories). Or we can also defined as complete set of
requirement is called EPIC
► One EPIC consist of multiple stories
User Stories/Stories/Story Cards:
A requirement that the business wants. It is something that is
deliverable within a single sprint(Smaller pieces of requirement ). It
can be a feature or modules or functionalities.
Tasks - It is a task/work which is need to perform on that particular story
► Story Point:
It is rough estimation given developer and test engineer to
develop and test individual stories
Ex: 1 story point=9 hours
1 SP=6
1 SP=8
Story point should be in Fibonacci series
Testing Story points estimated based on the
following aspects:

► Time spent on understanding story

► Write test scenarios
► Write test cases
► Review test cases
► Test case execution
► Defect tracking
Developer Story points estimated based
on the following aspects:
► Understanding requirements
► Design
► Coding
► Reviewing code
► WBT
► Time spent on fixing the defects
Sprint:

► Sprint is the actual time spent by developers and test

engineer to develop and test one or more stories
Sprint planning:

► Sprint planning is an event in scrum that defines what can

be delivered in the upcoming sprint and how that work will
be achieved.
► Sprint planning is a meeting conducted by scrum master on
the first day every sprint
► Explain the requirement
► Identify list of task to be done
► Assign task to engineer
Scrum Master:

► Scrum master is a person who is responsible for delivery of

the software to the customer within a planned period of
time.
► Scrum master will tract all the activities done by developer,
test engineer and Product owner.
► Product owner./Senior test engineer / senior developer /
Project manager and even customer can become Scrum
Master.
Scrum Meeting:
► It is a meeting conducted by a scrum master on the daily basis.
► It is also called as daily standup meeting
► This meeting is strictly bounded for 15 minutes
► In this meeting we discuss below mentioned points
1. What you did yesterday
2. What have you planned today
3. Are there any obstacles or impediments
► Note: During a sprint, the team checks in during the daily scrum,
or standup, about how the work is progressing. The goal of this
meeting is to surface any blockers and challenges that would impact
the teams ability to deliver the sprint goal.
sprint review meeting

► After a sprint, the team demonstrates what they’ve

completed during the sprint review. This is your team’s
opportunity to showcase their work to stakeholders and
teammates before it hits production.
Sprint retrospective meeting

► It is a meeting conducted by scrum master on the last day

of every sprint
In this meeting we discuss the following points
1. What went well
2. What didn’t go well
3. Are there any actions plan
Release retrospective meeting

► It is the meeting conducted by scrum master on the last

day of every release
Bug triage meeting:

► This is the meeting conducted by the test engineer or

scrum master a week or 2 week before the release
► BA,TE,Developer and SM will be a part of meeting
► In this meeting test engineer list all the open and pending
bugs which are not fixed by the developers in the current
and previous release as a team we will re prioritize the
defect from the customers’ business point of view and
decide how many bugs should be fixed as part of a current
release and how many bugs can be move to upcoming
release.
Product Backlog meeting/ backlog
grooming / backlog refinement :
► This is a meeting conducted by a BA or SM a week or 2
week before the release
► In this meeting test engineer and developer come up with
list all the pending stories which are not implemented as
part of the current and previous release.
► As a team we will re prioritize all the stories from the
business point of view and move the stories to the next
upcoming sprint or releases.
Advantages

1. We can save time and cost of the project.

2. The quality can be ensured because each and every sprint
will be tested multiple times
3. The requirement changes can be handled
4. All are participating in Scrum so that transparency can be
maintained
5. Each and every sprint we are delivering to the client so we
can maintain the customer's satisfaction and we can avoid
delivery risk of the project
Resume points:

► Experience
► Worked on Agile Scrum Development process
► Involved in Sprint planning meeting,
► Actively Involved in Daily standup meeting
► Participated Sprint Retrospective meeting.
Fresher:
► Excellent knowledge on Agile Scrum Development process.

► Very good knowledge on Sprint planning meeting.

► Very good knowledge on Scrum meeting.

► Very good knowledge on Sprint Retrospective meeting.

Scrum Team

Roles

● Product Owner
● Development Team
● Scrum Master

Size

● Scrum Team Size – 5 to 9

Self-Organizing Team

● Knows the best way to complete their work.

● No one tells the self-organized team what to do.

Cross-Functional Team

● Has all the skill sets required to complete their work without needing any outside help.
Product Owner

● Represents the committee or is influenced by it.

● Collaborates with the Stakeholders and the Scrum Team.
● Manages product backlog
○ Explains the product backlog items.
○ Prioritizing the work items.
○ Makes sure that the product backlog is easily understandable & transparent.
○ Clearly defines what items to work on.
○ Ensures that the development team understands the item in the product backlog
○ Anything to be added/removed/changed in the Product Owner should come through the
Product Owners.
● Take a call as when to release the work items.
Scrum Master

● Makes sure that the Scrum is clearly understood and adopted by the team.
● Is a servant leader for the Scrum Team.
● Removing Impediments
● Safeguard the team from useless interactions to maximize the business
value created by the Scrum Team.
● Facilitating Scrum events whenever requested.
● Ensures that the meetings are time boxed.
Development Team

● Delivers a potentially releasable Increment of “Done” product at the end of

each Sprint.
● They are self-organizing and cross-functional.
● No one tells the Development Team what and How to do.
● No Titles are allowed. All are developers on the team.
● No sub-teams can be created.
● They stay accountable to work on the Sprint Items.
● Development Team is responsible for tasking and providing the estimates