Review Process Activities
The Review Process Activities in Static Testing, as per ISTQB Foundation Level, comprise a structured set of phases that ensure comprehensive evaluation of work products without code execution. The review process typically includes five main activities: Planning, Kickoff, Individual Review, Issues … The Review Process Activities in Static Testing, as per ISTQB Foundation Level, comprise a structured set of phases that ensure comprehensive evaluation of work products without code execution. The review process typically includes five main activities: Planning, Kickoff, Individual Review, Issues Discussion, and Rework & Follow-up. Planning involves defining the review's scope, objectives, and participants. Reviewers and authors are identified, review materials are prepared, and entry criteria are verified to ensure readiness. This phase establishes the foundation for effective reviews. Kickoff is a brief meeting where the review's purpose is communicated to all participants. The author provides context about the work product, review criteria are clarified, and roles are assigned. This ensures everyone understands expectations and maintains consistency. Individual Review is where each reviewer independently examines the work product against defined criteria. Reviewers document findings, identify defects, and note issues without discussion. This phase promotes objective evaluation and prevents groupthink. Issues Discussion involves the review team meeting to discuss identified issues collaboratively. The review leader facilitates discussions, clarifies findings, and determines severity levels. Issues are categorized, and consensus is reached on required actions. Open communication helps validate findings and prioritize resolutions. Rework & Follow-up is the final phase where the author addresses identified issues and implements corrections. A designated reviewer verifies that rework meets acceptance criteria. Exit criteria are confirmed, and review metrics are collected for process improvement. Throughout these activities, clear roles are maintained: the author presents work, reviewers evaluate it, the review leader coordinates proceedings, and the scribe documents findings. Effective communication, proper documentation, and adherence to entry and exit criteria ensure that review process activities deliver their intended quality assurance benefits.
Review Process Activities - ISTQB CTFL Guide
Introduction to Review Process Activities
Review process activities form a fundamental component of static testing in software quality assurance. Understanding these activities is essential for anyone preparing for the ISTQB Certified Tester Foundation Level (CTFL) examination.
Why Review Process Activities Matter
Review process activities are critical because they:
- Detect defects early - Finding issues before dynamic testing saves time and money
- Improve code quality - Systematic reviews ensure consistency and adherence to standards
- Share knowledge - Team members learn from each other during review activities
- Prevent defect propagation - Early detection prevents defects from reaching production
- Reduce testing costs - Fewer defects to test means lower overall project costs
- Enhance communication - Reviews facilitate discussion about requirements and design decisions
What Are Review Process Activities?
Review process activities are structured, documented examination of work products (code, requirements, design documents, test plans, etc.) performed by one or more people to identify issues before those products are used or released.
Key Characteristics:
- Conducted by qualified reviewers
- Documented and tracked
- Focus on finding defects, not fixing them
- Separate from the original author's work
- Formal or informal processes
- Results in actionable findings
Types of Reviews
1. Informal Reviews
- No defined process or documentation
- Quick feedback mechanism
- Low cost and minimal overhead
- Example: Pair programming or desk checking
2. Formal Reviews
- Structured process with defined roles and responsibilities
- Documented procedures and outcomes
- Higher cost but more comprehensive
- Includes inspections, walkthroughs, and technical reviews
Review Process Activities - Detailed Breakdown
1. Planning
- Define review scope and objectives
- Select reviewers with appropriate expertise
- Schedule the review meeting
- Allocate necessary resources
- Identify entry and exit criteria
- Why: Proper planning ensures the review is focused and uses time efficiently
2. Kick-off
- Distribute the work product to be reviewed
- Explain the review objectives and scope
- Clarify the process and roles
- Answer initial questions
- Why: Sets expectations and ensures all participants understand their roles
3. Individual Review (Preparation)
- Each reviewer independently examines the work product
- Reviewers make notes on potential defects or issues
- No group interaction during this phase
- Time is allocated for thorough examination
- Why: Reduces groupthink and allows individual critical analysis
4. Review Meeting (Discussion)
- Reviewers come together to discuss findings
- Defects are discussed and logged
- Root causes are explored
- Questions are resolved
- A moderator facilitates the discussion
- Why: Collaborative discussion validates findings and reaches consensus
5. Rework
- The author addresses identified defects
- Changes are made to the work product
- Severity determines priority of fixes
- Why: Ensures actual improvements are made to the work product
6. Follow-up
- Verification that defects have been fixed
- Checking that rework meets quality standards
- Closure of the review
- Collection of metrics and lessons learned
- Why: Ensures effectiveness of the review process and continuous improvement
Review Process Roles
Manager/Organizer: Plans and coordinates the review
Moderator: Facilitates the review meeting and ensures process adherence
Author: Created the work product; may or may not participate in discussion
Scribe/Recorder: Documents issues, decisions, and action items
Reviewers/Inspectors: Examine the work product and identify defects
Review Techniques
Ad-hoc Review: Informal, unstructured approach with minimal guidelines
Checklist-based Review: Uses predefined checklists to guide reviewers
Scenario-based Review: Reviews work product through specific use cases or scenarios
Perspective-based Review: Reviews from different stakeholder perspectives (user, tester, developer, etc.)
Success Criteria and Metrics
Entry Criteria (Review can begin when):
- Work product is complete enough to review
- All reviewers are available
- Required documentation is distributed
- Review objectives are clear
Exit Criteria (Review is complete when):
- All identified defects are documented
- Rework is verified
- Metrics are collected
- Lessons learned are captured
Important Metrics:
- Number of defects found per hour
- Defect density (defects per page/thousand lines of code)
- Review coverage (percentage of work product reviewed)
- Cost-benefit analysis
- Time spent in each phase
How Review Process Activities Work - Practical Example
Scenario: Reviewing a Requirements Document
Planning Phase: Project manager identifies requirements document for review, selects 3 reviewers (business analyst, tester, architect), schedules 2-hour meeting
Kick-off: Requirements distributed 3 days prior; meeting begins with objectives clarification
Individual Review: Each reviewer spends 3 hours independently reading and annotating
Review Meeting: Reviewers present findings (missing acceptance criteria, ambiguous wording, incomplete non-functional requirements); 12 defects identified
Rework: Requirements author corrects all identified issues within 2 days
Follow-up: Moderator verifies all changes; review officially closed
Exam Tips: Answering Questions on Review Process Activities
Tip 1: Memorize the Six Phases
The review process has six distinct phases: Planning, Kick-off, Individual Review, Review Meeting, Rework, and Follow-up. Questions often test whether you know these phases in order and what happens in each.
Tip 2: Understand the Difference Between Informal and Formal Reviews
Exam questions frequently ask about distinctions. Remember: informal reviews are quick with minimal documentation; formal reviews follow structured processes with defined roles. Know which type is being described.
Tip 3: Know the Roles and Responsibilities
Questions commonly ask which role performs which activity. The Moderator facilitates, the Scribe records, Reviewers find defects, the Author addresses them, and the Manager organizes. Study role definitions carefully.
Tip 4: Recognize Entry and Exit Criteria
When exam questions describe a scenario, identify whether entry or exit criteria are being met. Entry criteria are about readiness to begin; exit criteria confirm completion. Questions test this distinction.
Tip 5: Distinguish Review from Testing
Common confusion point: Reviews are static testing (no code execution); dynamic testing involves execution. Questions may test whether you recognize activities as review (static) or testing (dynamic).
Tip 6: Understand Why Individual Review Matters
Questions may ask about the purpose of individual review before the group meeting. The answer is: it prevents groupthink and allows each reviewer to form independent opinions. This is critically important.
Tip 7: Know the Purpose of Each Phase
Instead of just memorizing phases, understand why each phase exists. Questions often ask about the purpose of a particular activity.
Tip 8: Recognize Common Pitfalls
Exam questions may describe incorrect review process implementations. Watch for: skipping individual review, allowing the author to participate in defect discussion too heavily, incomplete rework follow-up, or missing entry criteria checks.
Tip 9: Connect to Defect Prevention
Remember that reviews are primarily for defect prevention and early detection. Questions may ask why reviews are valuable - the answer relates to cost savings through early issue discovery.
Tip 10: Study Review Effectiveness Metrics
Questions may ask about measuring review success. Key metrics include defect detection rate, defect density, and cost-benefit ratio. Know the difference between these metrics.
Tip 11: Answer Scenario-Based Questions Systematically
When questions present a review scenario, identify: (1) which phase is being described, (2) which role is acting, (3) what criteria apply. Breaking down scenarios makes them easier to answer.
Tip 12: Remember the Cost-Benefit Analysis
Questions test understanding that reviews have ROI. Be prepared to discuss why investing in reviews saves money overall compared to finding defects later in development.
Common Exam Question Patterns
Pattern 1: "Which phase comes next?"
Answer by remembering the sequence: Planning → Kick-off → Individual Review → Review Meeting → Rework → Follow-up
Pattern 2: "Who should perform this activity?"
Match activities to roles carefully. The Author addresses defects; Reviewers find them; Moderators manage discussion.
Pattern 3: "What is the primary purpose of...?"
Focus on why each activity exists. Individual review prevents groupthink; follow-up ensures effectiveness.
Pattern 4: "Which of these is a sign of a properly executed review?"
Look for proper role separation, documented findings, and verification of rework.
Pattern 5: "Which is NOT appropriate in a formal review?"
Things like skipping phases, undocumented findings, or no rework verification would be inappropriate.
Practice Questions to Consider
- What are the six phases of a formal review process?
- Why is individual review conducted before the review meeting?
- What is the primary difference between the moderator and the scribe?
- When would you use an informal review instead of a formal review?
- What should happen during the follow-up phase?
- How do entry criteria differ from exit criteria?
- Why are reviews considered static testing?
- What metrics would you use to evaluate review effectiveness?
Key Takeaways
- Review process activities are structured, documented examinations of work products
- Six phases: Planning, Kick-off, Individual Review, Review Meeting, Rework, Follow-up
- Formal reviews are more rigorous; informal reviews are quicker
- Each phase has specific purposes and participants
- Reviews detect defects early, preventing costly late-stage issues
- Proper metrics measure review effectiveness
- Understanding roles and responsibilities is essential for exam success
🎓 Unlock Premium Access
ISTQB Certified Tester Foundation Level + ALL Certifications
- 🎓 Access to ALL Certifications: Study for any certification on our platform with one subscription
- 3840 Superior-grade ISTQB Certified Tester Foundation Level practice questions
- Unlimited practice tests across all certifications
- Detailed explanations for every question
- CTFL: 5 full exams plus all other certification exams
- 100% Satisfaction Guaranteed: Full refund if unsatisfied
- Risk-Free: 7-day free trial with all premium features!