CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Requirements elicitation is the active process of drawing out stakeholder needs using techniques such as interviews, workshops, surveys, and observation. It's a core BA skill that precedes analysis and documentation.

**Why not B:** Creating project schedules and assigning resources are project management responsibilities, not BA elicitation work. While a BA may contribute to planning conversations, their core function is to surface and understand stakeholder needs — not to allocate time or people to tasks.

**Why not C:** Writing user acceptance tests is a quality assurance and validation activity that comes after requirements have been elicited and documented. Elicitation is the upstream discovery process; test writing is downstream verification. Conflating the two obscures the distinct nature of each responsibility.

**Why not D:** Reviewing completed work against quality standards is a validation and verification activity, typically performed during testing or acceptance phases. Elicitation occurs much earlier in the requirements lifecycle — its purpose is to discover what stakeholders need, not to confirm whether delivered work meets those needs.