Bug Triage Meeting

-
Bug Triage Meeting

Definition:
Bug Triage meeting is discussion and analyses for all open bug, and agenda of discussion is set the priority to team for which bug should take up first, classify the bug in different category, find the where team struggle to get help to debug RCA, if RCA is available then assign bug to right team, find the recreation step from reporter and severity of bug.
                           

Procedure:
Generally, below procedure is followed for Bug Triage Meeting

       QA lead sends out a bug report with the new Bugs introduced since the last meeting.
       Product owner calls out a meeting.
       During the meeting, each Bug is analyzed to see whether correct priority and severity are assigned to it. Priority        and severity are corrected if need be.
       Bugs are discussed by the team. This involves discussing RCA, Dependencies to resolved bug, risks
       Assignment, rejection, reassignment of Bugs.
       After meeting completion, minutes of meetings are used for the Sprint planning for closing the issues


Bug Triage Meeting goals:
The goal of Triage remains the same: evaluate, prioritize and assign the resolution of Bugs.

Involved parties:
Below members are involved in Bug Triage Meetings.
·       Product Manager
·       Product Owner
·       Test Lead
·       Tech Lead
·       Development Lead/Developer


The output expected of triage meeting is not supposed to be debugging, but answering the following questions as efficiently as possible:
·       Is it a known bug, new bug, or user error?
·       If a new bug, which team should be responsible for the fix?
·       How severe is the impact? Is there a workaround, is it preventing further testing, etc.
·       Rough estimate of time to fix.




Comments

Post a Comment

Popular posts from this blog

What is Test case

-
A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of Creating test cases can also help find problems in the requirements or design of a Software. Test Case Format Test scenario id test case id test  case Summary Related Requirement Prerequisites Test Procedure Test Data Expected Result Actual Result Status Comment Created By execution Date Tester Test Environment
Read more

The tester should have skill

-
The tester should have skill A destructive Mindset to crack or crash system under test frequently Bring bad news Under worst time pressure  Need to take a different view, a different mindset  How should fault information be communicated 
Read more

Priority vs Severity

-
High Severity – High Priority bug This is when major path through the application is broken, for example, on an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error of page not found. High Severity – Low Priority bug This happens when the bug causes major problems, but it only happens in very rare conditions or situations, for example, customers who use very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very old version, it is not a high priority to fix the issue. High Priority – Low Severity bug The logo or name of the company is not displayed on the website. It is important to fix the issue as soon as possible, although it may not create cause a System and other component. Low Priority – Low Severity bug The privacy policy page take a long time to load. Not many people view the privacy policy page and slow...
Read more