Effective preparation is critical for a successful elaboration workshop. Before the session, the business analyst should identify and understand the customer's key business requirements at a high level to provide context and guide the discussion. To facilitate the core activity of the workshop—demonstrating out-of-the-box functionality to elicit detailed requirements—it is essential to create realistic and relevant demonstration data. This allows stakeholders to see the system in a context they understand, leading to more productive gap analysis and story creation.

A. Reviewing deployment notes is a technical activity typically performed by the development or operations team during a release, not a prep task for a requirements workshop.

D. Acceptance criteria are the specific conditions a story must meet to be considered complete. They are defined during or after the story is discussed and understood in the workshop, not before.

1. Guidewire Education. (n.d.). AGL010 - Guidewire Agile for Analysts. Courseware materials, Module on "Inception Phase." [Emphasizes the need for pre-workshop analysis of business goals and preparation of the demo environment.]

2. Guidewire. (2021). An Agile Approach to Core System Transformation. White Paper. p. 4. [The description of story-writing workshops implies prior understanding of goals and preparation to "demonstrate functionality," which requires relevant data.]