According to the PMI Guide to Business Analysis and the PMBOK® Guide, elicitation is an iterative process. Errors in the requirements definition often stem from " noise " or misunderstandings that occur during the initial gathering of information.

Why Choice C is correct:

The Verification Loop: Elicitation and Confirmation are two distinct but inseparable steps. After a session (like an interview or workshop), the Business Analyst (BA) should summarize the findings and review them with the stakeholders to ensure what was heard is what was actually meant.

Error Prevention: By confirming results immediately, the BA catches ambiguities, contradictions, and missing details early—before they are formalized into the requirements definition.

Stakeholder Buy-in: This step ensures that stakeholders agree with the BA’s interpretation, which dramatically reduces the number of errors discovered during the formal " Verification " or " Validation " phases later in the project.

Analysis of other options:

A (Stakeholders write requirements): Stakeholders are subject matter experts in their business domain, but they are rarely trained in technical requirement writing. This often leads to vague, non-testable, or incomplete requirements, which would likely increase the error rate rather than decrease it.

B (Include the project manager): While the Project Manager (PM) provides oversight and ensures the sessions stay within scope, the PM is not responsible for the technical accuracy of the requirements themselves. Their presence does not solve the root cause of communication gaps between the BA and the stakeholders.

D (Update the RTM): The Requirements Traceability Matrix (RTM) tracks requirements throughout the project lifecycle. However, if the requirements themselves are fundamentally incorrect or contain errors, the RTM will simply be tracking " incorrect " information. It is a tracking tool, not a verification tool for accuracy.

Key Concept: The Project Management Institute (PMI) emphasizes that the Confirmation of Elicitation Results (Choice C) is a proactive quality control measure. It closes the feedback loop between the sender (Stakeholder) and the receiver (Business Analyst), ensuring that the foundation of the project scope is accurate and agreed upon before further resources are spent on development.