Agile Bug Triage Meeting

-
Agile 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

    Frequency :
    Bug Triage meeting should be run once in every sprint


    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

    Perception 
    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

    Scrum Framework ( Scrum Methods)

    -
    Image
    Scrum Framework A Scrum project involves a collaborative effort to create a new product, service, or another result as defined in the Project Vision Statement. Projects are impacted by constraints of time, cost, scope, quality, resources, organizational capabilities, and other limitations that make them difficult to plan, execute, manage, and ultimately succeed. However, successful implementation of the results of a finished project provides significant business benefits to an organization. It is therefore important for organizations to select and practice an appropriate project management methodology. Scrum is a framework rather than a methodology. It provides clarity of responsibilities through roles, visibility through artifacts, and opportunities for inspection and adaptation through its events. Within this structure, scrum is a container for other processes and tools that are appropriate for meeting the specific needs of a team, organization or pro
    Read more

    Release Planning in Agile

    -
    Image
    Release Planning in Scrum organizations that use a Scrum process have a number of Scrum Teams that must collaborate to produce products. Issues that arise in moving to a Multiple-Team context include release ·        How to divide a large organization that use a Scrum process have a number of Scrum Teams that must collaborate to produce products. Issues that arise in moving to a Multiple-Team context include release ·        How to divide a large group of potential Team members into a specific set of Teams ·        How many Scrum Masters are needed to support the Teams ·        How many Product Owners are needed to support the Teams ·        How to develop requirements that span many Teams ·        How to plan, track, and enable successful coordination of work that spans many Teams ·        How to balance the competing needs for Product Management for both customer focus and Team focus ·        How to plan and track work for longer time horizons than one Sprint
    Read more