CAPM Practice: Determine how to gather requirements

The Five Whys technique iteratively asks why to trace symptoms to root causes. When a stakeholder states a requirement ('We need a report'), asking why repeatedly reveals the underlying need — often leading to simpler or more effective solutions.

**Why not B:** Asking five questions at the beginning of each stakeholder interview is a specific interview preparation practice, not the Five Whys technique. The Five Whys technique involves repeatedly asking "Why?" in response to each successive answer to drill down from a stated problem to its root cause.

**Why not C:** Requiring five stakeholder groups to validate each requirement describes a multi-party validation process, not the Five Whys. The Five Whys is a root cause analysis technique used during elicitation to uncover underlying business needs, not a validation step requiring specific numbers of stakeholder groups.

**Why not D:** A framework for evaluating requirements against five quality criteria describes a quality assessment rubric, not the Five Whys. The Five Whys is an investigative questioning technique that traces symptoms to root causes, helping BAs understand the real business need behind stated requirements.