During iterative Quality Assurance testing, the QA department logs defects, they also involve assigning or rejecting new defects created from the last triage meeting and existing defects are reassigned if need arises.
Triage meeting should regularly conducted during the development phase or testing phase of a project. Usually, Quality Assurance (QA) lead calls these meetings. Generally, below procedure is followed for Triage Meetings.
- QA lead sends out a bug report with the new defects. During this meeting, each defect is analyzed to see whether correct priority and severity are assigned to it.
- Priority and severity are corrected if needed. Defects are discussed by the team. This involves discussing complexity of the defect, risks, Assignment, rejection, reassignment of defects is done. Updates are captured in bug tracking system. After meeting completion, minutes of meetings are sent out to involved parties.
- The goal of Triage remains the same: evaluate, prioritize and assign the resolution of defects. As a minimum, you want to validate defect severities, make changes as needed, prioritize resolution of the defects, and assign resources.
- Frequency of these meetings depends on project situation. Multiple factors will play role in deciding the frequency of Defect Triage Meetings. These factors could be:
- Project schedule
- Number of defects
- Impact on schedules of team members and their availability
- Project health in terms of defects
- Typically, Defect Triage Meetings takes place 2-3 times a week.