Scribd
Upload
77 views7 pages

Defect Triage Meeting Guidelines

Defect triage meetings are held to discuss and prioritize defects found during testing with stakeholders like developers, business analysts, and management. During these meetings, the test team presents the prioritized defect list which is then further reviewed and prioritized based on impact, efforts to fix, and whether the defect blocks release. Ship-stopping defects that block the customer or cause downtime must be fixed before release, while other lower priority defects may be deferred to a later release based on consensus.

Uploaded by

Vipin Kumar
Copyright
© © All Rights Reserved
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
77 views7 pages

Defect Triage Meeting Guidelines

Defect triage meetings are held to discuss and prioritize defects found during testing with stakeholders like developers, business analysts, and management. During these meetings, the test team presents the prioritized defect list which is then further reviewed and prioritized based on impact, efforts to fix, and whether the defect blocks release. Ship-stopping defects that block the customer or cause downtime must be fixed before release, while other lower priority defects may be deferred to a later release based on consensus.

Uploaded by

Vipin Kumar
Copyright
© © All Rights Reserved
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/ 7

Defect Triage Meetings

𝐖𝐡𝐚𝐭 𝐚𝐫𝐞 𝐃𝐞𝐟𝐞𝐜𝐭 𝐓𝐫𝐢𝐚𝐠𝐞 𝐦𝐞𝐞𝐭𝐢𝐧𝐠𝐬?

Defect Triage meetings are held to discuss


and prioritize the defects found by the
testing team with the development team,
business analysts, and other required
project stakeholders.
How do we review during triage meetings???

During triage meetings:

(a) The test team manager/lead gets the prioritized list of


defects based on defect severity and priority.

(b) It is during these meetings that the list of defects is further


reviewed with the development team and BA.

(c) This review of defects helps to further prioritize these defects


and helps the development team to plan for fixing the same.
How do we decide defect prioritization???

1. Customer impact:

(a) What will be the impact of the defect in the field?


(b) Would it block the customer's day-to-day work ?
(c) Would it cause downtime?

If yes, then such defects are the “ShipStopper” bugs.

The product cannot be released without a fix for such issues.


2. Efforts required

What will be the efforts required to fix the defect?

If it is not a ship-stopper and the efforts to fix are high,


then based on consensus, such defects may be
planned to be fixed in a future release.
3. Impact on other features:

Is the defect a minor UI cosmetic issue?


Is it causing any impact on other application features?

Post-discussion with Product and Business management on


low priority defects - the team can decide to defer the defect

You might also like