Guide Exam And Already Passed
Answers.
What is a user story ? - Answer High level requirement from a users perspective
Often captured on index card during early planning sessions
Role, Action, Reason
What is a story elaboration - Answer Conversations occurs between the users and the team to ensure
that all requirements are understood
High level requirements that emerge from the discussions are documented
What is a User Story (Card) ? - Answer A tool built by GW to support capturing requirements
each represents a GW user story
Or a customer gap story
A single user story can drive changes to mulitple story cards
User Story Cards are used in phases - Answer Pre Inception (Discovery),
Inception (Elaborate Requirements)
Sprint 0 (Story Elaboration)
Development ( Plan Sprints Build solution)
, Guidewire recommends the following naming convention for use story cards: - Answer xCenter -
Theme - Sub-theme - ID Number
PC9 - CancelReinstateRewrite - Rescind cancellation - 13270 - GW
User Story Card (Inception phase) - Answer - reviewed to confirm features scope & effort
- Details identified are captured in the user card for development
- New gap stories may be idenfited and added to the backlog
Completion should include:
( A confirmed scope and estmate is completed with assoicated User story cards)
(A conceptual Sprint plan is estblished to guide when user story cards will be built out)
What are themes? - Answer Common processes for insurancesuite products (claim center)
(PolicyCenter) (Billing Center)
Steps to plan a delivery sprint? - Answer 1. Determine team capacity
2. Define sprint backlog
3. Validate estimate for each user story
4. Define tasks for each user story in the sprint
- Assign a recourses to each task
- Estimate each task
5. Add new user stories and tasks as needed
6. Repeat step 1 - 5 until sprint capacity is full