In the Collect Requirements process, as defined by the PMBOK Guide and the PMI Guide to Business Analysis, missing the input of key stakeholders creates a significant risk of scope gaps and future rework.
When project constraints (like tight deadlines and time zone differences) prevent synchronous collaboration, the Business Analyst (BA) must implement asynchronous strategies to ensure completeness.
Why Choice B is correct:
Asynchronous Elicitation: By distributing the documents to the excluded time zones, the BA allows those stakeholders to provide input, identify missing requirements, and correct misunderstandings on their own schedule.
Risk Mitigation: This directly addresses the risk of " missing requirements " by ensuring that stakeholders with " similar functions " in other countries have a voice, even if they couldn ' t attend the live sessions.
Validation: This serves as a secondary check to ensure that the requirements captured in one region are globally applicable, which is critical for an international project.
Analysis of other options:
A (Add to the risk register): While the BA should log this risk, simply recording it does not reduce the actual threat to the project ' s success. PMBOK emphasizes active risk mitigation over passive documentation.
C (Ask stakeholders to speak on behalf of others): This is a high-risk approach. Even stakeholders with " similar functions " may have different local regulations, cultural nuances, or technical constraints. One region cannot accurately represent the specific needs of another without direct communication.
D (Request sponsor approval): Getting approval for a flawed process doesn ' t fix the flaw. The sponsor expects the BA to use professional judgment to gather accurate requirements; asking for permission to skip stakeholder groups is a failure of the BA's core responsibility.

Key Concept: The Project Management Institute (PMI) highlights that " Requirements are the foundation of the WBS. " If the foundation is built on partial data, the entire project is at risk. Choice B is the most effective way to balance the need for speed with the necessity of thoroughness, ensuring that the Requirements Traceability Matrix eventually reflects the needs of the entire global stakeholder base.