GUIDEWIRE FUNDAMENTALS EXAM PREP
QUESTIONS AND ANSWERS FULL TEST
PAPER ACCURACY CHECKED
◉ What happens during the development phase of requirements
gathering?
Answer: User stories are refined to a functional detail level in
Requirements Refinement Workshops.
◉ Who approves and accepts the user story when it is complete?
Answer: The Product Owner.
◉ What should be reviewed in preparation for a requirements
workshop?
Answer: Current and future state processes, inception notes,
backlog grooming details, application guide, training materials,
and demonstration data.
◉ What is a best practice for conducting a requirements
workshop?
Answer: Start by reviewing the workshop agenda and
expectations.
◉ What should be documented during a requirements workshop?
, Answer: Decisions made during the workshop.
◉ What should not be allowed during a requirements workshop?
Answer: More than one conversation at a time.
◉ What should be done after a requirements workshop?
Answer: Ensure the User Story Card is fully updated and follow up
on action items.
◉ What is a common mistake when asking questions about
requirements?
Answer: Asking yes/no questions.
◉ What should be avoided when using requirements from a
legacy system?
Answer: Using them as a starting point, especially when trying to
stay close to the base configuration of the new system.
◉ What is a pitfall to avoid regarding requirements?
Answer: Accepting solutions as requirements, which eliminates
flexibility.
◉ What should be identified instead of what the insurer wants or
had in the past?
Answer: What the insurer needs.
QUESTIONS AND ANSWERS FULL TEST
PAPER ACCURACY CHECKED
◉ What happens during the development phase of requirements
gathering?
Answer: User stories are refined to a functional detail level in
Requirements Refinement Workshops.
◉ Who approves and accepts the user story when it is complete?
Answer: The Product Owner.
◉ What should be reviewed in preparation for a requirements
workshop?
Answer: Current and future state processes, inception notes,
backlog grooming details, application guide, training materials,
and demonstration data.
◉ What is a best practice for conducting a requirements
workshop?
Answer: Start by reviewing the workshop agenda and
expectations.
◉ What should be documented during a requirements workshop?
, Answer: Decisions made during the workshop.
◉ What should not be allowed during a requirements workshop?
Answer: More than one conversation at a time.
◉ What should be done after a requirements workshop?
Answer: Ensure the User Story Card is fully updated and follow up
on action items.
◉ What is a common mistake when asking questions about
requirements?
Answer: Asking yes/no questions.
◉ What should be avoided when using requirements from a
legacy system?
Answer: Using them as a starting point, especially when trying to
stay close to the base configuration of the new system.
◉ What is a pitfall to avoid regarding requirements?
Answer: Accepting solutions as requirements, which eliminates
flexibility.
◉ What should be identified instead of what the insurer wants or
had in the past?
Answer: What the insurer needs.
