Agile:-

 It is a like SDLC process used for developing software

 Agile it is a iterative (continuous) process for developing software.
 Agile is a philosophy, it is not plane driven but it is a value driver.
 Frequent change in requirement doesn’t in impact neither on development nor on testing or
in production.
 There are various types of
 XP
 Scrum
 Lean
 Kanban
 DSDM
 FDD
 I have worked in scrum agile methodology.
 Duration of scrum agile methodology in my organization 2 week.
 Scrum- it is a subset of agile. It works on sprint and most widely used framework.

Architecture of agile-
1. Stake Holder- It is a top most body of company. This tells/gives requirement to product
owner.
2. Product Backlog-
 Stack holder gives requirement to product owner and these requirements are collected by
product owner in product backlog.
 Product backlog is master list of all requirements.
 Product backlog contains
1. Features
2. Epics
 These product backlog are converted into sprint backlog depends on priority or functionality
which is implanted first.
 Product backlog is created by product owner.
 Example product backlog contains 200 requirements for a project.

3. Sprint backlog-
 Sprint Backlog is the list of functionality that the team is committing that they will complete in
current iteration.
 Sprint Backlog created by product owner.
 Sprint 1 will contains (20 requirement), like sprint 2 contains (20 requirement)..etc
 Sprint Backlog contains
1. User stories (1 requirement called user stories)- contains
 Description – contains details description about functionality
 Acceptance criteria – defines what functionality contains or do & don’t or for
testing point of you what to test and what not to test.

 Example- Our first User story- describes the webpage search feature:
Description  As a website user
 I want to able to search on the webpage
 So that I can find necessary information
Acceptance  User searches for an item by its name
criteria-
 “Given that I’m in a role of registered or guest user.
In the When I open the “Products” page.
form/template Then the system shows me the list of all products.
of And the system shows the “Search” section in the right top corner of the screen.
Given/When/T When I fill in the “Search” field with the name of existing item in the product
hen list.
And I click the “Apply” button OR press the Enter key on keyboard.
Then the system shows products in the Search Results section with product
names matching entered product name.
And the system shows the number of search results in the top of the Search
Results section”.
 Specific user story assign to developer & tester. Developer do analysis, coding that time we
tester write test case (test case design).
 After completion of development developer sent build/application for testing & we start testing
(test case execution).
 Same process follows for every user story.
4. Advantages of agile-
 Check point after each module
 Daily scrum meeting
 Sprint wise delivery
  Implementation of automation

5. Disadvantages of agile-
 Early requirement should be clear before sprint start. If not then makes problem.

6. Different Meeting in agile-

Sr. Name of Purpose of meeting Who present Time
No. Meeting
1 Sprint planning To give estimation Product owner, 1-2 hr
meeting Designer, Scrum
master, Dev. Team & (conduct
Test team start of
sprint)
2 Daily stand Check status- Scrum master, 15-30 min
up/scrum 1.what we have done Designer, Dev team
meeting yesterday & Test team (Daily)
2. what we are doing today
3. Any issue/roadblock
facing
3 Sprint review Tester gives review to user Product owner, 1- 2 hr
meeting story which he has tested Designer, Dev team&
Test team (conduct
end of
sprint)
4 Sprint In these meeting discuss Scrum master, 1 hr
retrospective about what good things Designer, dev team & (conduct
meeting happens in current sprint Test team end of
& what happen bad things sprint)
in current sprint
5 Grooming If any user story not clear Product owner, 1 hr
meeting or if any new project Designer, developer
requirement come that will & tester for (conduct
understand in these respective before start
meeting module/project/user of sprint or
story any time
when
requirement
not clear)

Q. What is Principles of Agile?

 Welcome changing requirements, even late in development.
 Valuable Working Software delivered frequently. This is our primary measure of Agile
progress.
 Early visibility to Business
 Self-Organizing teams
  Product owners (Business) and developers must work together daily throughout the project, at
a sustainable pace
 Inspect and adapt
 Simplicity

Q. What is estimation in agile. How you decide estimation.

 In my organization at the time of sprint planning meeting we give estimation to user story.
 Estimation is nothing but to give time hours to user story. i.e. how much time will require
for developer to complete coding/development & how much time require for tester to
complete testing.
 Likewise we give estimation for respective user story.

Q. Terminology present in Agile.

1. Velocity- Velocity measuring the rate at which team consistently delivery business value
(requirement).

2. Epic- In agile epic is a body of work that can be broken down into specific tasks (called “stories,”
or “user stories”) based on the needs/requests of customers or end users.

 When Product Owner writes a user story for a feature or against customer request, which
looks simple in the beginning. But, while covering all related work and scenarios, same user
story expands so much that it cannot fit either in a week or a sprint time-frame. It is the time
to consider this big user story as epic and start slicing it in smaller user stories.
 Epics show in JIRA tool.
3. Burndwn Chart & Burnup chart-

4. Iteration-In the context of an Agile project, iteration is a time box during which development
takes place (development & testing) of all user story, the duration of which: Vary from project to
project, in my organization it is a 2 weeks.

5. Impediment - Any issue that prevents the Scrum Teams to progress or to start work should be
placed on the Impediment Log.

Any issue that is highlighted and known to impact the Scrum Teams at a future date or future sprint,
should be placed on the Impediment Log
It is the responsibility of Scrum Master to resolve impediments locally.

If the impediments cannot be resolved locally, then these need to be raised at the Scrum-of-Scrum
daily meetings for escalation

Anyone in the Team can raise an Impediment identifying a blocker to project progress.

Difference between sanity & Smoke testing-

Sr. No. Sanity Testing Smoke Testing
1 Zero level testing/Build level testing/tester Build level testing
acceptance testing
2 Sanity testing used for checking stability of Smoke testing is extra sake of sanity testing, used
build i.e. we are checking either build is for checking core functionality of application at end
stable for testing ya not to end.
3 In Sanity testing we perform, Smoke Testing is done to check either new
1. Core functionalities of the functionalities or bugs have been fixed properly
application. without going deeper.
2. Link validation
3. Tab Validation
4. Page validation
5. GUI
4 Objective of smoke testing is to verify the Objective of sanity testing is to verify the rationality
stability of the system to process of the system to proceed with more regression
regression testing testing
6 Sanity testing is performed by testers only. Smoke testing is performed either by developers or
testers.
7 Test cases are not written in sanity testing Test cases are written in
8
9 Sanity testing is not documented or Smoke Testing is usually documented and scripted
scripted
testing is a subset of regression testing Smoke testing is a subset of acceptance testing
Sanity testing focused on selected Smoke testing focuses on the entire system from
components of a system end to end
Smoke Testing is like a General health Sanity testing is like a special health check-up
check-up