You are on page 1of 2

Defect Process for User Story Testing

· Raise a Defect immediately


Is this a
Is this defect in · Criticality is Cosmetic Update “In
cosmetic change Continue testing the
relation to the · Link it to the User Story Progress” Channel
START Defect discovered YES but the YES rest of the Test
User story you · Add as much information as in Teams with
functionality Cases within story
are testing possible… Replication steps, details
works?
video, screen shots etc…

NO
NO

· Raise a Defect · Raise a Defect immediately


· Not linked to the current · Criticality is SHOWSTOPPER
User Story Is this stopping you · Linked to the User Story
· Add as much information Update “In
testing this and other · Add as much information as Inform Project
as possible… Replication Progress” Channel
User Stories i.e. Website YES possible… Replication steps, Manager/Scrum
steps, video, screen shots in Teams with
not working, Page is not video, screen shots etc… Master
etc... details
showing · Affected User Stories to show
as BLOCKED/Defect
outstanding
Is there any test cases Update status of
NO that you have been User Story to
Carry on Testing YES
unable to test due to BLOCKED/Defect
User Story outstanding defect? outstanding.

· Raise a Defect immediately


Is the defect stopping · Criticality is Major Update “In Continue testing the
you from testing · Link it to the User Story Progress” Channel rest of the Test Move to Waiting
YES
multiple test cases · Add as much information as in Teams with Cases that can be under the
within the User Story? possible… Replication steps, details tested appropriate Column
When Test has video, screen shots etc… on the Kanban
completed all Test
Cases and Passed,
User Story can
progress through No
Kanban · Raise a Defect immediately
· Criticality is Minor Update “In
Continue testing the
· Link it to the User Story Progress” Channel
No rest of the Test
· Add as much information as in Teams with
Cases
possible… Replication steps, details
video, screen shots etc…

Time bound
exploratory test on
User Story

When Test has


completed all Test
Cases and Passed,
User Story can
progress through
Kanban

Is there anything
that has been
END Select a ticket No
unblocked in the
Test Column

YES

Tester to select
these first before
selecting new User
Story from Ready
for Test Column
DEFECT MANAGEMENT FOR PO

This needs thrashing out as to who will assess this How does Test know when fixed?

PO to decide
PO to assess defect. Defect will be TEST Informed that
Defect in Expedited whether to
PO to decide actioned by this is fixed or raised
or Selected for expedite or put in Expedite
whether to expedite Developers. Once as bug - BLOCKER
Development Backlog as a bug.
or put in Backlog. fixed removed

Backlog

Unlink call from


User Story

You might also like