Defect Triaging

Defect Triaging is a process where all the defects of the current Sprint are discussed in a formal meeting and triaged based on severity, frequency, risk, impact, etc. Triaging is nothing but tagging the defects with severity and priority.

In this process where tester team/test lead demonstrates and explains the defects to the entire Scrum Team. Based on product owner, developer, leads inputs, the defects are classified into different categories.

The goal of the Defect Triage meeting is to evaluate, prioritize, and assign the resolution of defects. Based on the severities of the defect, resolutions are added to the defects, and resources are assigned to work on them.


Discussion pointers of Defect Triaging

Before the meeting, the test lead sends a bug report with all the active defects. The discussion on each of the defects is done based on the below questions:

Is it a known issue, a new defect, or a user error?

In case of a new defect, which software team is responsible for the fix?

How severe is the impact of the defect? Any workaround, prevention, etc. ?

A rough estimate of time to fix.


When Defect Triaging is required?

The defect triaging is conducted based on the project situation. Below are some of the factors which decide the need for defect triaging:

  1. Number of active defects in the product
  2. Project Schedule
  3. Team members availability
  4. Current product quality


Defect Triaging Process

Step 1: Scrum master scheduled a defect triaging meeting.

Step 2: Active defect list is prepared and send out to stakeholders by a test lead.

Step 3: Defect triage meeting:

  1. The test lead demonstrates and explains the defects.
  2. All the new defects are reviewed and evaluated, and priority and severity are assigned to each.
  3. The development team discusses the complexity of fixing defects.
  4. Defects get assigned to the respective team.

Step 4: Defects are updated in captured in the defect tracking system.

Step 5: Minutes of the meeting are sent by the scrum master.


Participants in Agile

Below scrum team members take participate in defect triaging process:

Main participant Optional participant
The Product Owner Developers
The Scrum Master Testers
Developer Lead Business Analyst
Test Lead  



Roles and Responsibilities

Test Lead

Send defect report to all attendees before the meeting

Explain the defect

Helps in Prioritization of the Defect.

Take note of all the action items, risk, etc. related to the defect

 
Developer Lead

Explain the root cause analysis.

Provide insight on the application areas impacted by the Defect.

Helps in Prioritization of the Defect.

Expresses the complexity involved in fixing the Defect.

Assign the Defect to the development team for Fixing.


Scrum Master

Scrum Master responsible for organizing the Defect Triaging Meeting.

Take notes if there are any impediments in fixing the defects

Checks that the meeting is time-boxed and does not deviate from the focus.

Assign Priority and Severity to defects as made a call in the meeting


Product Owner

Helps in prioritization of defects

Place the medium priority defects in the Product Backlog to be picked up for the subsequent releases.

Helps the team to understand the impact of the defect on the product and explain to them the user perspective.