The business analyst (BA) is facilitating a requirements workshop with a large group of diverse stakeholders, some of whom are not entirely familiar with the goals and objectives of the project. The B

Change strategy addresses how the organization will transition to a future state, which is a separate concern from planning what and how to elicit requirements.

Requirements prioritization occurs after requirements are gathered and confirmed, not during the planning of elicitation activities.

Elicitation scope defines the boundaries of what will be elicited, who the participants are, and which techniques are appropriate - all of which require knowledge of the business domain, stakeholder diversity, and expected outputs. When stakeholders are unfamiliar with project goals, the BA must carefully scope elicitation to ensure the right information is gathered without overwhelming participants. Understanding corporate culture and group dynamics guides the BA in selecting communication approaches effective for the specific audience.

Enterprise architecture describes the structure of business processes and technology systems and is an input to analysis, not an output communicated by understanding group dynamics.