Prior to a Requirements Workshop, a BA should (1) review notes from the Inception Workshop to ensure continuity of vision and scope (B) and (2) study relevant base ClaimCenter functionality so that discussions stay grounded in out-of-the-box capabilities and gaps (C). These steps are cited as core preparation activities in Guidewire’s implementation methodology.

A. Inviting end users is logistical planning; preparation focuses on the BA’s advance study.

D. Acceptance criteria are created after requirements are captured, not before the workshop.

E. The BA—not the PM—drafts and circulates the agenda per Guidewire BA role definition.

1. Guidewire Implementation Methodology Handbook v10, §2.1 “Workshop Preparation Checklist,” items 2 & 3.

2. Guidewire Education: Business Analyst Role and Responsibilities v10, slide 23-24.

3. MIT OpenCourseWare 15.571, Lecture 6 “Preparing for Requirements Sessions,” segment 3.