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

Elicitation and documentation are distinct: elicitation uses techniques (interviews, workshops, observation) to discover requirements; documentation organizes the output into formats (user stories, use cases, specifications) that the team can work from. Good elicitation that isn't documented is lost knowledge.

**Why not A:** Documentation does not come before elicitation. Elicitation must occur first because it is the process of drawing out information from stakeholders, research, and other sources. Documentation then captures and formalizes what was discovered during elicitation activities.

**Why not C:** Elicitation and documentation are clearly distinct activities with different purposes and techniques. Elicitation involves actively gathering information through interviews, workshops, observation, and other techniques, while documentation involves recording, organizing, and formalizing that information into structured requirements artifacts.

**Why not D:** Documentation of requirements is a core BA responsibility, not exclusively the project manager's job. While PMs may maintain project-level documents such as the project plan, the BA is responsible for documenting business requirements, functional specifications, and related analysis artifacts.