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

Agile methodologies prioritize working software and team collaboration over comprehensive documentation. In an Agile project, if a tester finds a defect and the developer can fix it immediately within the same iteration (sprint), it is highly acceptable—and often encouraged—to bypass writing a formal defect report. Instead, the tester and developer communicate directly (e.g., verbally or via a quick chat) to resolve the issue. This lightweight approach reduces administrative overhead, maintains the team's velocity, and fosters immediate cross-functional collaboration.

Option A: Stating "Never" contradicts core Agile principles, which advocate for minimizing unnecessary documentation when direct communication and immediate resolution are possible.
Option C: If a defect is deferred to a later sprint (such as a hardening sprint), it must be formally logged in the backlog to ensure it is tracked, prioritized, and not forgotten.
Option D: If a defect must be fixed by a different team, a formal defect report is mandatory to ensure proper tracking, clear communication, and a documented handover across team boundaries.

- ISTQB Foundation Level Agile Tester Extension Syllabus (v1.1), Section 2.1.2 (Status of Testing).

- ISTQB Advanced Level Test Manager Syllabus (v3.0), Section 4.2 (Defect Management).