ISTQB Agile Tester Practice Test

The type of review characterized by documented procedures and requirements is a formal review. Formal reviews are structured processes with defined objectives, roles, and responsibilities. They often have a clearly outlined agenda and provide a systematic approach to evaluating work products, such as requirements documents or design specifications.

In a formal review, documentation is critical, as it serves as a basis for the process and helps in generating measurable outcomes such as metrics on defects found or improvement areas identified. This approach ensures accountability and traceability, making it easier to track issues and follow up on them. Formal reviews may also involve multiple stakeholders, such as project managers, developers, and testers, to gather diverse perspectives and achieve a comprehensive assessment.

On the other hand, informal reviews lack the structured procedures and documentation that formal reviews have. They may involve casual discussions or ad-hoc meetings without rigorous documentation, making them less suitable for thorough evaluations. Peer reviews and technical reviews may have elements of formality, but they typically do not encompass the full framework and documentation requirements that define a formal review process.