Testing and Defects

Agile Testing Defects

• The defects must be addressed during the same sprint they were found in. Otherwise, your story will not match the acceptance criteria and definition of “done” and you won’t be able to close it. This is the classic “JUST FIX IT” situation.
• Never size defects! The original story already has a size that includes all work needed to get it done – design, coding, manual and automated testing, defect fixing, documentation and whatever else you might have in your definition of “done”.
• To reduce the number of defects, make sure the team works as one from the very beginning of the sprint, developers and testers plan their work together, collaborate and focus on quality.
• Never try to fix all bugs, unless your system is very small and very new. Product Owner needs to prioritize bugs and size by the team. Always consider the ROI of fixing bug vs. developing a new feature

 Defect Reporting

The short answer is the Product Owner. S/He should be the ultimate arbitrator in deciding if and when a defect should be addressed. Therefore, s/he asks for guidance and advice from the Scrum Development Team:

• The Product Owner could seek the business analysts (BAs) or the tester’s input in making priority decisions. The BAs and testers are usually involved in design, requirement gathering, and acceptance criteria writing. Thus, they possess the business knowledge to make such a priority judgment.
• Secondly, s/he could also consult with the developers to get their technical perspective on the impact of the defect and the cost to either fixing it or not fixing it.

Get certified and unlock more opportunities. Practice and Validate your skills to become a Certified Agile Testing Professional Now