Roles and Responsibilities in an ISTQB Formal Review

In an ISTQB formal review, key roles include the Author (creates the work product), Management (allocates resources), Facilitator/Moderator (leads the review), Review Leader (takes overall responsibility), Reviewers (identify defects), and the Scribe (records issues). Proper role assignment is critical for success.

What is the Role of the Author?

The Author is the individual or team responsible for creating the work product under review. Whether it is a requirement document, a piece of code, or a test plan, the author is the primary subject matter expert regarding its intended purpose and logic. In the context of a formal review, the author's primary goal is to learn from the feedback and improve the quality of their work.

During the review process, the author provides necessary context. In the initiation phase, they might walk the team through the document to explain complex concepts. During the review meeting, they answer questions and provide clarifications, helping reviewers understand why certain decisions were made. It is vital that the author approaches the review with an open mind, viewing defects not as personal criticisms, but as opportunities for improvement.

After the review meeting, the author's responsibility shifts to fixing the identified defects. They must systematically address the issues logged by the scribe, update the work product, and submit it for verification. The author plays a central role in ensuring that the final output meets the required quality standards.

How Does Management Contribute to the Review?

While they rarely participate in the actual review meetings, Management plays a foundational role in the success of the formal review process. Their primary responsibility is to provide the necessary support, resources, and environment for reviews to take place effectively. Without management backing, reviews are often perceived as a waste of time and are easily skipped when schedules tighten.

Management is responsible for planning the overall review strategy within the project lifecycle. They must allocate sufficient time in the project schedule for planning, individual preparation, and review meetings. They also allocate the budget and ensure that the right personnel are available to participate. If reviewers are constantly pulled away for 'urgent' tasks, the review process will fail.

Furthermore, management decides what is to be reviewed based on risk analysis and project goals. They monitor the metrics generated from the reviews (such as defect density and time spent) to assess the return on investment. Ultimately, management is responsible for fostering a culture of quality where static testing is valued as an integral part of development, not an afterthought.

Why is the Facilitator (Moderator) So Important?

The Facilitator, historically referred to as the Moderator, is the linchpin of the formal review process. They are a neutral party responsible for managing the review from start to finish. A good facilitator ensures the review stays on track, meets its objectives, and remains a constructive, professional exercise rather than descending into arguments or personal attacks.

During the planning phase, the facilitator helps select reviewers, schedule meetings, and define entry and exit criteria. They ensure that the work product actually meets the entry criteria before allowing the review to proceed. During the review meeting, their role is crucial. They guide the team through the document, manage the time, and ensure that every identified defect is discussed and logged appropriately.

Most importantly, the facilitator manages the interpersonal dynamics of the meeting. They mediate disagreements between the author and reviewers, ensuring that the focus remains strictly on the product and not the person. After the meeting, they follow up with the author to ensure fixes are implemented and verify that the exit criteria have been met before officially closing the review.

What Do the Reviewers Do?

Reviewers are the individuals tasked with examining the work product to identify defects. They are selected based on their specific technical or business expertise. A diverse team of reviewers is highly desirable; for example, a design document should ideally be reviewed by a fellow architect, a developer, a tester, and perhaps a security specialist. This variety of perspectives ensures a comprehensive evaluation.

The bulk of a reviewer's work happens during the individual preparation phase. They must dedicate focused time to scrutinizing the work product, often using checklists or specific assigned perspectives to guide their analysis. They meticulously document any anomalies, inconsistencies, or deviations from standards. Their goal is to find problems, not solve them.

During the review meeting, reviewers present their findings to the team. They must communicate their identified defects clearly, objectively, and respectfully. They participate in the analysis of issues to determine if they are indeed defects and help assess their severity. Effective reviewers are detail-oriented, critical thinkers who are capable of communicating issues constructively.

What is the Function of the Scribe (Recorder)?

The Scribe, also known as the Recorder, plays a vital administrative role during the formal review meeting. Their sole responsibility is to accurately document all the defects, issues, and decisions discussed during the meeting. While it may seem like a simple task, a competent scribe is essential for ensuring that no valuable feedback is lost or misunderstood.

As the reviewers raise points and the team agrees on a defect, the scribe logs the details. This log typically includes the location of the defect (page number, line of code), a clear description of the issue, and the agreed-upon severity. The scribe must capture the consensus of the group accurately, often reading back what they have recorded to confirm alignment before moving on.

Having a dedicated scribe allows the facilitator to focus on managing the meeting dynamics and allows the author and reviewers to focus on analyzing the product. The author should never be the scribe, as they need to concentrate on understanding the feedback. The defect log created by the scribe becomes the actionable to-do list for the author during the fixing phase.

❓ Frequently Asked Questions