CAPM Practice: Determine how to conduct stakeholder communication

A requirements walkthrough is a review technique where the BA presents requirements documentation to stakeholders for validation. The goal is to identify errors, ambiguities, and missing requirements through collaborative review.

**Why not A:** Taking stakeholders on a physical tour of a project facility is a site visit, not a requirements walkthrough. A requirements walkthrough is a structured review session where the BA presents requirements documentation for feedback, conducted in a meeting setting rather than a physical location tour.

**Why not B:** A presentation of completed software for final approval describes a demo or acceptance review, not a requirements walkthrough. Requirements walkthroughs occur during the requirements phase to review documentation before development, not after software is complete.

**Why not D:** Walking new team members through documentation describes an onboarding or knowledge transfer activity. A requirements walkthrough is specifically a validation technique where the BA presents requirements to stakeholders and subject matter experts to identify errors, gaps, and ambiguities.