Manual Testing

- HemanthKumar C
Agile Model Definition ( what )?
Agile is a software development methodology to build a
software incrementally using short iterations of 1 to 4
weeks so that the development process and testing
happens parallelly.
The main goal of Agile is Customer Satisfaction through
quick delivery of working piece of software.
Types of Agile Processes
1 . Agile SCRUM methodology
2. Extreme Programing
3. Kanban processes
4.Crystal
5. Lean software development
Types of Agile Process
Scrum is a lightweight Agile project management framework
1 . Agile SCRUM methodology
that can be used to manage iterative and incremental projects ,
2. Extreme Programing where development & testing activity happens parallel
3. Kanban processes
4.Crystal
5. Lean software development
Agile Model Drawback of Agile.
 For bigger and complex project it is difficult to do “effort
Principles Behind the Agile Manifesto. estimation” during the beginning of s/w development.

 Customer Can change the requirement at any Stage of  “less scope” for Design(HLD & LLD) & documentation (
Development. Test Plan, Test Scenarios & Test Cases ).

 There will be good Communication b/w customer, BA, Dev  If customer are not “aware of about the requirement”
& TE. chances are there we might mess-up the project.

 Release will/should be very short.  For Agile, Experience resources are required.

 Our Highest Priority is “Customer Satisfaction” by quick

delivery of working piece of software.

 It is very simple model to follow.

 Dev,TE & BA will be having meetings very regularly, it will

be helpful to improve the Process.

 Teams will be Self-Organized.

 Software quality will be good.

 Here we convey the information Face to Face

Agile Model Terminologies
What is Story Point?
It is a ruff estimation given by developers and TE to develop & test every individual stories. 1 story point = 8 hours

It will be in the form of FIBONACCI SERIES 1 2 3 5 8 13 21. . .etc

( because it will be easy to give estimation

User Story
It’s a customer requirement to fulfill end user requirement. It is normally written from the perspective of an end-user.
In most cases a story point uses one of the following scales for sizing:
• 1,2,4,8,16
• X-Small, Small, Medium, Large, Extra-Large , XXL
• Fibonacci sequence: 1,2,3,5,8,13,2
1 story points effort is 8 mph[man per hour] in service base company
1 story points effort is 6 mph[man per hour] in product base company
Agile Model Terminologies

Swag : It is a ruff estimation given by dev & TE to develop & test every individual stories in the form of HOURS.

Sprint
it is the actual time taken by dev & TE to develop & test one or more stories

(Fixed duration of time from define the  requirement  design test deliver the shippable final candidate )
The project divided sprints , each sprint will have specified time line (2 week to 1 month or 3 month), the end result of each sprint should
be shippable product
Agile Artifacts
Product backlog
The product backlog is a list of new features, enhancements, bug fixes, tasks, or work requirements needed to build a product. it’s compiled
from input sources like customer support, competitor analysis, market demands, and general business analysis.

Or
Product backlog

• It’s a repository (git hub) where all the list of user story are stored and maintained by the Scrum Master with the help of
BA and Customer ( product Owner ) Set of functional and non-functional product requirements repository which is
maintained by product owner

Sprint backlog
The sprint backlog is a set of product backlog tasks that have been promoted to be developed during the next product increment. sprint
backlogs are created by the development teams to plan deliverables for future increments and detail the work required to create the
increment.

Or
Sprint backlog

List of User Stories committed for the particular Sprint

Stakeholder
• is anyone that is potentially affected by the outcome
of the project. The term is usually used to name the
management or the customers.
• Stakeholders are a customer representative who
facilitate the requirement from the Customer side ,
• Is a program managers, subject matter experts act as
advisers as decisions are made around the release
planning.

Development Scrum team

Development Scrum team will take care of development activity

Manual Testing Scrum Team

Manual Scrum team will take care manual testing activity

Automation Scrum Team

Take care of handling automation scrum activity

DevOps Scrum Team

Take Care of Build management

Agile Roles
Scrum Master
A Scrum Master is a team leader and facilitator who helps the team members to follow agile practices so that they can meet their
commitments.

The responsibilities of a scrum master are as follows:

 He will plan each and every activities done by the developers, Test Engineers & BA.
 To enable close co-operation between all roles and functions.
 To remove any blocks
 To work with the organization to track the progress and processes of the company.
 Scrum Master handle the Daily standup meeting
 Scrum Master will be mainly working on PROJECT MANAGEMENT TOOL like JIRA, where in Scrum Master will create the Epic for
the Requirement, Create Stories for the EPIC & Task for the Stories & assign the task for each individual Engineers.

What is EPIC?
Epic consist of no of Stories
Product Owner
 A Product Owner is the one who drives the product from business perspective. The responsibilities or a Product Owner are as follows:
 To define the requirements and prioritize their values
 To determine the release date and contents.
 To take an active role in iteration planning and release planning meetings.
 To ensure that team is working on the most valued requirement.
 To represent the voice of the customer.
 To accept the user stories that meet the definition
WHAT ARE THE MEETINS/SCRUM CERIMONIES
DONE IN SCRUM MEETING?

1. PRODUCT BACKLOG MEETING

2. SPRINT GROOMING
3. SPRINT BACKLOG MEETING
4. SPRINT PLANNING
5. DAILY STANDUP MEETING
6. SPRINT RETROSPECTIVE MEETING
7. RELEASE RETROSPECTIVE MEETING
8. BUGTRIAGE MEETING
SPRINT PLANNING
Agile Ceremonies
IT IS A MEETING CONDUCTED BY THE SCRUM MASTER ON THE 1ST DAY
OF EVERY SPRINT.
BA, SCRUM MASTER,DEVELOPERS TEAM, TESTING TEAM, PM
(SOMETIMES) WILL BE PRESENT IN THIS MEETING.

IN THIS MEETING BA WILL EXPLAIN THE COMPLETE REQUIREMENT TO

THE ENTIRE TEAM.

WHERE IN BA WILL EXPLAIN HOW EACH AND EVERY STORY SHOULD

WORK & ALSO BA EXPLAIN CUSTOMER BUSINESS WORKFLOW TO
THE ENTIRE TEAM.

SCRUM MASTER WILL PRIORITISE THE STORIES FORM CUSTOMER

BUSINESS POINT OF VIEW. SCRUM MASTER WILL ASSIGN THE
STORIES TO DEVELOPERS & TEST ENGINEERS BASED ON THE
AVAILABILITY.

SCRUM MASTER WILL CALCULATE AVAILABLE HOURS OF EVERY

INDIVIDUAL ENGINEERS IN THIS MEETING.
Daily stand up
It Is A Meeting Conducted By Scrum Master On Daily
Basis.

Ba,Dev, TE& Pm (Sometimes) & Scrum Master Will Be

Present.

THIS MEETING WILL BE BOUND FOR 15 MINS

IN THIS MEETING WE WILL DISCUSS BELOW

MENTIONED.

1.) What Did You To Yesterday?

2.) What Will You Do Today?
3.) Are There Any Obstactles Or Impedements?
SPRINT RETROSPECTIVE

IT IS A MEETING CONDUCTED BY THE SCRUM MASTER ON THE LAST

DAY OF EVERY SPRINT.
BA, SCRUM MASTER,DEVELOPERS TEAM, TESTING TEAM, PM
(SOMETIMES) WILL BE PRESENT IN THIS MEETING.

IN THIS MEETING WE WILL DISCUSS ABOUT.

1.) WHAT WENT WELL? ( ACHIEVEMENTS)

2.) WHAT DIDN’T GO WELL? ( MISTAKES )
3.) WHAT ALL THE ACTIONS PLAN?
SPRINT REVIEW
Scrum development team present a demonstration of a
stable release candidates product . product owner declare
which item is completed & not completed , product owner
might add addition requirement based on stakeholder
feedback.
RELEASE RETROSPECTIVE MEETING

IT IS A MEETING CONDUCTED BY THE SCRUM MASTER ON THE LAST

DAY OF EVERY RELEASE.
BA, SCRUM MASTER,DEVELOPERS TEAM, TESTING TEAM, PM
(SOMETIMES) WILL BE PRESENT IN THIS MEETING.

IN THIS MEETING WE WILL DISCUSS ABOUT.

1.) WHAT WENT WELL? ( ACHIEVEMENTS)

2.) WHAT DIDN’T GO WELL? ( MISTAKES )
3.) WHAT ALL THE ACTIONS PLAN?
BUG TRIAGE OR DEFECT TRIAGE MEETING

IT IS A MEETING CONDUCTED BY THE SCRUM MASTER ON THE LAST

DAY OF EVERY RELEASE.
ba, scrum master,developers team, testing team, pm (sometimes) will
be present in this meeting.

In this meeting we will gather a list of all the pending & opened
defects. which are not fixed by the developers in current & previous
release / sprints.

Team will re-prioritize the defect from customer business p.o.v &
decide which bugs should be fixed in the current release or sprint &
which bugs can be moved to the upcoming release sprint. this process
is called as bug /defect triage meeting.
BUG BUCKET
Bug Bucket it is an epic or story created by the scrum master or BA in
the product management tool called “JIRA”.

WHAT IS CHICKEN & WHAT IS PIG?

Pigs and chicken both are the words used for scrum team members.

PIGS are the scrum team members, These are the people, who are
committed to the Project work or the project & complete all the task
in the given period of time.

Ex : Developers, TE, Scrum Master & BA etc…

CHICKENS are the people who get the business to the company & get
the work done from the team members.

EX: Management Team, Customers Stake Holders etc…

What is Zero Sprints?
Zero Sprint is a “Pre-Planning” Sprint” to get ready for the “Actual
Sprint”.
Ex : Deciding which technology, Infrastructure, System Configuration.
What is Spike?
Spike is an “issue”, where as spike cannot be treated as a story.
Because of “lack of Clarity on the given Task ( requirement ) ”
Ex : To upload a file ( how much size didn’t specify ).

What is Velocity?
Total amount of work completed by every individual engineer in the
given sprint is called as “VELOCITY”.

What is Capacity?
Total amount of “Available Hours of Every individual Engineers for the
given sprint is called as “CAPACITY”.
What is Story?
Story board is a powerful way to visually presenting the information
about “How the story works” explain about How the Process work” &
it shows the Passage of Time & what happening in the project.
What is Agile Board?
Agile Board is a tool that helps team to plan, visualize & manage to
work on time during a “series of consecutive sprints”.

Burn Up cart
burn up shows how much work has been completed, and the
total amount of work.
Burn Down Cart
A burn down chart shows how much work is remaining to be
done in the project
What is BUG BUCKETS?
It is a EPIC or Story created by the scrum master or BA in the project
management tool called “JIRA”.

This Bug Bucket consist of list of all pending defects which are not
fixed by the developers.

HAVE YOU DONE MIDDLE WARE TESTING?

YES! Through API TESTING.
HAVE YOU DONE LAST LAYERS TESTING?
YES! SQL TESTING.
 Agile Model

Agile SCRUM Methodology

Scrum is a lightweight Agile
project management framework
that can be used to manage
iterative and incremental projects ,
where development & testing
activity happens parallel.
 Test Management Tools- JIRA and ZEPHYR

• Jira is a project management tool used for issues and bugs tracking system. it is widely used as an issue-
tracking tool for all types of testing.
• Jira is an incident management tool.
• Jira is developed by Atlassian inc., an Australian company.
• Jira is a platform independent tool; it can be used with any OS.
• Jira is multi-lingual tool − English, French, German, Japanese, Spanish, etc.
• Jira supports MySQL, oracle, PostgreSQL and SQL server in the backend.
• Jira can be integrated with many other tools − subversion, git, ClearCase, team foundation software,
mercury, concurrent version system and many more.
• zephyr for Jira is a native application that exists in Jira and brings quality test management capabilities to
any Jira project. when zephyr is used with Jira, the test can be created, viewed in any Jira project, and
executed immediately or as part of a testing cycle that may be linked to other issues.
Thank you !!