Difficulty: Medium

Average Score: 59%

A team is feeling pressured to begin development work due to tight project deadlines. There are stakeholders with similar functions located in multiple counter business analyst files, limited the requirements elicitation sessions to times that work for stakeholders in one time zone.

To reduce the risk with this approach, which step should the business analyst take?

Rationale

Ask the stakeholders in the elicitation sessions to speak on behalf of stakeholders in other time zones.

This approach allows for the inclusion of diverse perspectives, ensuring that the requirements gathered are representative of all stakeholders, even those who cannot attend the sessions due to time zone constraints.

A (Request the project sponsor to approve this requirements elicitation approach for this project.) YOUR ANSWER

This choice does not provide an actionable step to mitigate the risk associated with limited stakeholder participation. Instead, it merely describes the current situation without proposing a method to address it.

B (Add the risk to the risk register so other stakeholders are aware of the approach.) YOUR ANSWER

While seeking approval from the project sponsor is important, this step does not directly address the risk of excluding stakeholders from different time zones. Approval does not ensure that the requirements will be comprehensive or inclusive of all relevant perspectives.

C (Ask the stakeholders in the elicitation sessions to speak on behalf of stakeholders in other time zones.) CORRECT

Documenting the risk in the risk register is a good practice, but it does not mitigate the actual risk of insufficient stakeholder input. Awareness alone does not resolve the issue; proactive measures are necessary to ensure all voices are heard.

E () YOUR ANSWER

Distributing documented requirements for feedback is beneficial, but it occurs after the elicitation process. This step does not prevent the initial exclusion of stakeholders from the discussions, which is critical for gathering comprehensive requirements.

Conclusion

A business analyst must actively ensure that all stakeholder voices are included during requirements elicitation to minimize risks associated with project timelines and stakeholder engagement. By asking participants in the sessions to represent stakeholders from other time zones, the analyst fosters a more inclusive process, leading to better-informed decisions and project outcomes. All other options, while relevant in their contexts, fail to directly address the core issue of stakeholder representation during the elicitation sessions.

Related Questions

View all