109. To reduce the risk with this approach, which step should the business analyst take?
Answer: C
Asking the stakeholders in the elicitation sessions to speak on behalf of stakeholders in other time zones is the best step to reduce risk.
This approach mitigates the risk of incomplete requirements by ensuring that voices from different time zones are represented during the elicitation sessions, despite the logistical challenges posed by tight deadlines.
A) Request the project sponsor to approve this requirements elicitation approach for this project.
Requesting approval from the project sponsor does not directly address the risk associated with limited stakeholder participation. While it may lead to formal acknowledgment, it does not actively involve stakeholders from other time zones in the requirements gathering process, which is crucial for comprehensive understanding.
B) Add the risk to the risk register so other stakeholders are aware of the approach.
Adding the risk to the risk register is a passive response that only documents the issue without taking immediate action to mitigate it. Awareness of risks is important, but without a proactive solution, the risk remains unaddressed, potentially leading to gaps in requirements.
C) Ask the stakeholders in the elicitation sessions to speak on behalf of stakeholders in other time zones.
This option actively engages participants in the elicitation sessions to represent their counterparts in different time zones. By allowing stakeholders to articulate the needs and concerns of those who cannot participate, the business analyst can gather a more comprehensive set of requirements, reducing the risk of misalignment.
D) Distribute the documented requirements to relevant stakeholders in all time zones for review and comment.
While distributing documented requirements for review is a good practice, it is a reactive measure that follows the elicitation sessions. This approach may miss critical input during the initial gathering phase, as it does not ensure that all perspectives are considered upfront, leading to potential oversights.
Conclusion
The most effective way to mitigate the risk of incomplete requirements due to time zone constraints is to have stakeholders actively represent their peers in the elicitation sessions. This ensures diverse input is captured during the requirements phase, in contrast to the other options that either passively acknowledge the risk or respond after the fact.