In an Agile project, when Is it acceptable lo not write a formal defect report when a defect is found''

Context Analysis:

Agile emphasizes efficiency and collaboration. If a defect is quickly resolved within the same

iteration, documenting it formally may not add value.

Evaluation of Options:

A . Never:

Incorrect. Agile allows flexibility; not all defects require formal reports.

B . If the defect can be fixed in the same iteration in which it was found:

Correct. Aligns with Agile principles of immediacy and adaptability, minimizing overhead (Syllabus

section TM-1.2.4).

C . If the defect can be fixed in a later hardening sprint:

Incorrect. Documentation is needed if a defect remains unresolved within the iteration.

D . If the defect must be fixed by another team:

Incorrect. Clear documentation is critical for external team collaboration.

Syllabus Alignment:

ISTQB Advanced Test Management highlights Agile principles, including flexibility in defect reporting

based on project needs (TM-1.2.4).

Reference:

ISTQB Advanced Level Test Management Syllabus