CAPM Practice: Determine how to gather requirements

Prototyping presents a tangible model (wireframe, mockup, or functional prototype) for stakeholders to interact with. Hands-on experience triggers feedback that stakeholders couldn't provide from abstract descriptions, validating and refining requirements.

**Why not A:** Document analysis involves reviewing existing written materials like policies, forms, and manuals to extract requirements. It does not involve stakeholders handling a sample product or prototype to provide hands-on feedback.

**Why not B:** Benchmarking compares practices or performance against industry standards or competitors. It does not involve presenting stakeholders with a prototype or sample product for interactive feedback and requirements refinement.

**Why not C:** The Delphi technique gathers expert opinions through anonymous, iterative questionnaire rounds to reach consensus. It does not involve stakeholders interacting with a tangible prototype to elicit feedback on design and functionality.