Study guide

3.3 Review Process and Roles

ISTQB Certified Tester Foundation Level CTFL v4.0

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Fundamentals of Testing

1.1 What Testing Does 1.2 Verification, Validation, and Debugging 1.3 Testing, Quality, and Risk Reduction 1.4 The Seven Testing Principles 1.5 Test Process, Testware, and Traceability 1.6 Tester Skills, Roles, and Independence

2 Chapter 2: Testing Throughout the Software Development Lifecycle

2.1 SDLC Models and Good Testing Practices 2.2 Shift-Left, Test-First, and DevOps Testing 2.3 Test Levels: Component Through Acceptance 2.4 Test Types: Functional, Non-Functional, White-Box, and Change-Related 2.5 Confirmation, Regression, and Maintenance Testing 2.6 Collaboration Across the Lifecycle

3 Chapter 3: Static Testing

3.1 Static Testing Versus Dynamic Testing 3.2 Work Products and Static Analysis 3.3 Review Process and Roles 3.4 Review Types 3.5 Successful Review Practices

4 Chapter 4: Test Analysis and Design

4.1 Technique Selection and Coverage 4.2 Equivalence Partitioning 4.3 Boundary Value Analysis 4.4 Decision Table Testing 4.5 State Transition Testing 4.6 White-Box Coverage 4.7 Experience-Based Testing 4.8 Collaborative Test Design

5 Chapter 5: Managing the Test Activities

5.1 Test Planning, Strategy, Entry Criteria, and Exit Criteria 5.2 Test Estimation and Prioritization 5.3 Risk-Based Testing 5.4 Monitoring, Control, and Reporting 5.5 Configuration Management and Traceability 5.6 Defect Management 5.7 Test Completion and Retrospectives

6 Chapter 6: Test Tools

6.1 Test Tool Classification 6.2 Automation Benefits and Risks 6.3 Selecting and Introducing Tools 6.4 Tool Support Exam Traps

3.3 Review Process and Roles

Key Takeaways Explain This Topic AI

The generic review process has six activities: planning, review initiation, individual review, communication and analysis, fixing, and reporting.

Individual review (preparation) is where reviewers identify most anomalies, questions, and improvement suggestions.

Communication and analysis decides whether each anomaly is a defect and what follow-up actions are needed.

The principal review roles are manager, author, moderator (facilitator), scribe, reviewer, and review leader.

CTFL questions test the responsibility of each role rather than the person's organisational job title.

Last updated: June 2026

The Generic Review Process

A review is not just a meeting. In CTFL terms, the generic review process has activities before and after any group discussion. The process is tailored to the review type and context, but the syllabus defines six activities in a stable order.

# Activity Main purpose Exam clue

1 Planning Define scope, objectives, the work product, quality characteristics to evaluate, effort, timeframe, and entry/exit criteria What are we reviewing, and why?

2 Review initiation Ensure everyone understands the task and has the work product, supporting material, roles, and access Are people ready to begin?

3 Individual review Each reviewer examines the work product alone and logs anomalies, questions, and recommendations Private preparation and notes

4 Communication and analysis Communicate identified anomalies, decide whether each is a defect, assign status, ownership and actions Meeting, decision, ownership

  • 5 Fixing The author corrects confirmed defects in the work product Defects are fixed by the author
  • 6 Reporting Communicate review results; check exit criteria; record metrics Follow-up, closure, metrics

Individual review (also called individual preparation) matters because it prevents the group discussion from being the first time anyone reads the material; in formal reviews it is where the majority of anomalies are typically found . Reviewers can apply checklists, scenarios, perspectives, or risk focus areas.

During communication and analysis , not every anomaly becomes a defect. A reviewer may misunderstand a domain rule, or raise an improvement suggestion rather than a required correction. The group decides status, ownership, and next action; for high-formality reviews, decisions and metrics are recorded. Note that fixing defects is the author's responsibility , and reporting closes the loop by confirming exit criteria are met.

The Review Roles and Their Responsibilities

Roles are a frequent exam target, and the syllabus names a specific set of roles with distinct responsibilities. One person may hold more than one role in lower-formality contexts, but the responsibilities stay attached to the role.

Role Core responsibility

Manager Decides what is to be reviewed, allocates time, budget and people, and monitors ongoing cost-effectiveness

Author Creates and, when needed, fixes the work product under review

Moderator (facilitator) Ensures the review meeting runs effectively, creating a safe and productive environment

Scribe (recorder) Collates and records anomalies, decisions, and the meeting's outcomes

Reviewer Performs the review; may be subject-matter experts, people working on the project, stakeholders, or technical experts

Review leader Takes overall responsibility for the review: decides who is involved, and organises when and where it takes place

Notice the moderator and the review leader are distinct: the review leader has overall organisational responsibility (who, when, where), while the moderator focuses on facilitating an effective meeting. The manager controls resources and scope from outside the review; the author produces and fixes the product; the scribe documents; the reviewers find the issues.

The exam likes role traps . The moderator does not automatically fix the product — the author does. The scribe does not decide what must be reviewed — the manager does. The author should not dominate the conversation defensively, and in a formal inspection the author should not act as review leader or scribe, so that objectivity and traceability are preserved.

Map responsibilities to roles, not to job titles. A senior developer who wrote the code is still the author for that work product. A business analyst who examines acceptance criteria is a reviewer . A test manager who provides time and people is acting as manager . A person can wear two hats — for example reviewer and scribe — but the responsibilities of each role remain as defined.

Tailoring the Process and Reading Scenarios

The six activities are a generic template, not a rigid script. The syllabus is explicit that the process is scaled to the review type and context . An informal review may collapse planning, initiation, and individual review into a quick glance and skip formal reporting entirely. An inspection, by contrast, performs every activity deliberately, records metrics, and checks entry and exit criteria. So the number of activities you actually perform depends on the formality chosen in 3.4.

A frequent exam structure presents a short scenario and asks which activity is being described. Use these anchors:

"We agreed which document, set objectives, and booked two hours" → Planning .

"Everyone received the document and the checklist and confirmed their role" → Review initiation .

"Each reviewer marked up the spec on their own and noted questions" → Individual review .

"In the meeting we discussed each finding and decided which were defects" → Communication and analysis .

"The author corrected the confirmed defects" → Fixing .

"We confirmed exit criteria were met and recorded the defect-density metric" → Reporting .

Another common trap mixes roles with activities . Remember: the manager operates mainly around planning (deciding what to review and providing resources); the reviewers do the heavy lifting in individual review ; the author owns fixing ; the scribe documents during communication and analysis ; and the moderator facilitates that same meeting. The review leader spans organisation across the whole process.

  • Role Most active in which activity
  • Manager Planning (scope, resources)
  • Review leader Overall organisation across all activities
  • Reviewer Individual review
  • Moderator Communication and analysis (the meeting)
  • Scribe Communication and analysis (recording)
  • Author Fixing

Finally, the syllabus links the review process back to independence and objectivity . Separating roles — especially keeping the author out of the review-leader and scribe positions in formal reviews — reduces the bias of an author defending their own work, and produces a more trustworthy record of what was found and decided. This is the same independence principle that runs through the whole CTFL: fresh eyes find defects the author's eyes slid past.