Defect management
The process of recognizing, recording, classifying, investigating, resolving, and closing defects.
Syllabus chapters: 5
Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.
Related terms
Defect management in a practice question
Question 1
A project's teams sit in three countries with little overlap in working hours, and its informal verbal status updates keep being missed. What is appropriate for a project in that situation?
- More formal communication, which may be more appropriate for distributed teams
- Reducing the frequency of reporting, so that fewer updates can be missed
- Appointing an independent test team to take over the status reporting
- Communicating status only through the defect management tool
Show answer
- Correct answer: More formal communication, which may be more appropriate for distributed teamsDistributed teams and time differences are exactly this circumstance.
- Reducing the frequency of reporting, so that fewer updates can be missedReporting less often does not address updates being missed.
- Appointing an independent test team to take over the status reportingIndependence of testing is a separate matter and does not solve distribution.
- Communicating status only through the defect management toolA defect tool records defects; it does not communicate overall test status.
More formal communication may be more appropriate for distributed teams where direct face-to-face communication is not always possible due to geographical distance or time differences. Typically, different stakeholders are interested in different types of information, so communication should be tailored accordingly.
Syllabus section 5.3.3
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.