0% found this document useful (0 votes)

54 views9 pages

Testing Questions-Points

Backlog grooming, also known as backlog refinement or story time, is a recurring event for agile teams to prepare user stories in the product backlog for upcoming sprints. It helps ensure the right stories are prioritized and that the backlog does not become unusable. Key objectives are to break down large stories, discuss stories with the team, and sometimes estimate stories. The ideal outcome is a prioritized list of user stories.

Uploaded by

Niranjan Pathak

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

54 views9 pages

Testing Questions-Points

Uploaded by

Niranjan Pathak

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 9

Grooming

bug triage
spike and zero
pot of gold
agile principle
grooming
chicken and pigs
white and black why name
difference between agile and scrum
bug and defect difference
fishbowl in agile

What is the definition of Backlog Grooming/Backlog Refinement,

Story Time?

Backlog grooming, also referred to as backlog refinement or story

time, is a recurring event for agile product development teams. The
primary purpose of a backlog grooming session is to ensure the
next few sprints worth of user stories in the product backlog are
prepared for sprint planning.

Regular backlog grooming sessions also help ensure the right

stories are prioritized and that the product backlog does not
become a black hole.

Backlog refinement sessions present an opportunity for product

managers and product owners to explain the strategic purposes
behind prioritized items in the backlog. These conversations can
help improve alignment across the cross-functional team.

There are also several tactical objectives of backlog grooming

sessions:
Break down large user stories into smaller tasks.
Discuss user stories with the team.

Sometimes (but not always) the scrum master or project manager

and delivery team will use this session to estimate stories and
assign story points.

What is the ideal outcome of a backlog grooming session?

At the end of a backlog refinement session, you should have a
prioritized list of user stories.

Someone to facilitate the session: It could be a product owner,

product manager, scrum master, project manager, or even an agile
coach or consultant.
Product owner and/or other product team representatives.
Delivery team. (if the team is too large to include, you can consider
inviting management representatives.)
QA and dev (If required)

What is Defect Triage/Bug Triage.?

The term Triage is used in Software Testing to define the severity
and priority of defects. Defect triage is a process or mechanism
where each defect is prioritized based on its severity.

Bug Triage Meeting is done to sort out the priority of all open bugs.
When and how these open bugs need to be fixed is decided in this
Defect Triage Meeting.

During Defect Triage Meetings, Triage Teams decide how to

categorize and prioritize defects. Categories often used are

We are going to fix this now

We are going to fix this later
We are never going to fix this

Defect Triage comes into the picture in Software Testing when

there are no sufficient resources to handle the defects.

Imagine a situation where there are a number of defects are more

and the resources to handle those are limited. In this case, defect
triage helps to get as many defects resolved as possible by
assessing the defects and prioritize them based on the severity of
the defects.
The frequency of the Software Bug Triage meeting is weekly,
monthly, on each sprint (defect triage in Agile). It varies from project
to project.

What is a defect?
The variation between the actual results and expected results is
known as defect.

If a developer finds an issue and corrects it by himself in the

development phase then it’s called a defect.

What is a bug?
If testers find any mismatch in the application/system in testing
phase then they call it as Bug.

What is an error?
We can’t compile or run a program due to coding mistake in a
program. If a developer unable to successfully compile or run a
program then they call it as an error.Human mistake in code is
called error.

What is a failure?
Once the product is deployed and customers find any issues then
they call the product as a failure product. After release, if an end
user finds an issue then that particular issue is called as failure

The following 12 Principles are based on 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 development. Agile

processes harness change for the customer’s competitive
advantage.

3.Deliver working software frequently(Sprint wise), 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.(eg- maintain team velocity)

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 behavior accordingly.

Difference between agile and scrum

Spike- In Software Development when we are creating Spike in Sprint in Agile
it means we need to do some RnD work with reference to that requirement to
come up with the best possible solution to develop that Feature/Requirement.
Zero Sprint-Officially there are no such sprint as Zero Sprint in Scrum but
some organization are using it to set up the Project,Team and streamline their
Organizational and Project related activities which are not going to give any
productive product at the end of the sprint which can be demoed.
Spike is a name given to all the research items you want to carry on to
understand their feasibility and to be able to estimate these items for
implementation, if they are feasible enough to be implemented.
The team can decide how much effort they want to spend on investigating this
research item, in their Sprint, and accordingly give story points to it.
If at the end of the Sprint, the result in not achieved you might want to replan
and reprioritize it in the next Sprint as needed. You might end up totally
discarding this research item as well if it is not feasible to implement for
technical or business or any other reasons.

Zero Sprint is used by some organizations to enable the teams start working on,
let's say, a basic infrastructure or a basic foundation. Not everything can be
developed on a fly even in agile way of working and some foundation needs to
be in place to start delivering a working system or working features. So, the
minimum infrastructure, minimum code and minimum design and architecture
that is needed to be able to start delivering working system is generally what's
developed in Zero Sprint and then we build on top of it, working iteratively.

Chickens & Pigs in scrum:

The terms "chickens" and "pigs" define the stakeholders and roles
in Scrum.

The "Pigs" are usually the actual team members, the Scrum Master
or the Product Owner.

"Chickens" are the roles of the managers or stakeholders.

Why white box testing and black box testing named as white
and black:
The concept is called "white box" because it is symbolically see-through, as the
code is visible to the tester(Who do white box) during the examination.
In comparison, when the inner code isn't visible, it is called black box testing.

Pot of gold
A pot of gold is great, but what is even better to find at the end of a rainbow
would be all the benefits a thriving agile adoption can bring an organization.
Projects in agile organizations are more likely to be delivered successfully.
They’ll deliver more value at a lower cost with greater predictability and lower
risk.
Users and customers are therefore happier. Team members are more productive
and happier.

What is a conditional sign off?

Conditional sign off is prepared when release is moved to the next phase or next
box testing and known issues or defects are not fixed within given time frame
and it will code will move to the next box with known issue or along with
defects