Guidewire Module 2 Questions with
Actual Answers
1. What is a conceptual sprint plan? ✔️✔️A High level sprint plan is delivered at the
end of inception
1. Which model does a BA follow while writing the user story? ✔️✔️INVEST
1. Expand INVEST ✔️✔️I-Independent
N-Negotiable
V-Valuable
E-Estimable
S-Small
T-Testable
1. Expand Ms. Cow ✔️✔️Must Have
Should Have
Could Have
Will Not Have
1. What is a theme? ✔️✔️Theme is a common process with each product
1. Themes are broken down into what components? ✔️✔️Features, user stories and
tasks
1. What does Guidewire provide as starting point for your project? ✔️✔️Guidewire
provides approximately 5000 reusable assets or tools to facilitates progress during the
implementation project
1. What is the best practice for project planning? ✔️✔️Plan for what you know
Re-evaluate periodically
Make changes based on new knowledge
1. What are the customon? ✔️✔️Confirm scope, validate sizing, and baseline the
project
1. What does guidewire mean by an inception? ✔️✔️Guidewire projects include an
inception phase to
Confirm the scope of the project
Produce an initial sizing
Create the project baseline
, 1. Who typically attends inception? ✔️✔️Product owner, SME, BA, Developers and
Testers
1. Why does Guidewire timebox inception? ✔️✔️Time box discussions to avoid
excessive details
1. Which criteria are used to prioritize the backlog? ✔️✔️Priority, Value, Size and Risk
1. What are the key objectives from inception? ✔️✔️Formally kick off the project
Train the team on base product and methodology
Introduce the team to agile concepts
Determine an approach to address any product gaps
Document the high-level design for integrations
Explain estimation changes as a result of the workshops
1. What is the Inception best practices? ✔️✔️Utilize the Agile methodology
Map business case to the themes/sub-themes
Estimate stories using points
Introduce base product features and functionality
Document key requirements on story cards
Avoid deep discussions about details requirements
Manage time judiciously
Assess product alignment for each user story
Create new story cards for gap stories
Define a delivery backlog at the end of the inception
Assess business value to help prioritize the delivery backlog
1. Steps to plan a delivery sprint. ✔️✔️Determine team capacity
Define sprint backlog
Validate estimate for each user story
Define tasks for each user story in the sprint
- Assign a resource to each task
- Estimate each task
Add new stories and task as needed
Repeat step 1-5 until sprint capacity is full
1. What are Planning a delivery sprint best practice? ✔️✔️Standardize sizing
guidelines to improve predictability across the program
Standardize the task list before loading the product backlog
Prioritize the release backlog to facilitate planning
Move stories to sprints according to the conceptual sprint plan
Dedicate the team to sprint planning at the start of each sprint
1. What are the recommended guidewire principles? ✔️✔️We are not building a
system from scratch
Actual Answers
1. What is a conceptual sprint plan? ✔️✔️A High level sprint plan is delivered at the
end of inception
1. Which model does a BA follow while writing the user story? ✔️✔️INVEST
1. Expand INVEST ✔️✔️I-Independent
N-Negotiable
V-Valuable
E-Estimable
S-Small
T-Testable
1. Expand Ms. Cow ✔️✔️Must Have
Should Have
Could Have
Will Not Have
1. What is a theme? ✔️✔️Theme is a common process with each product
1. Themes are broken down into what components? ✔️✔️Features, user stories and
tasks
1. What does Guidewire provide as starting point for your project? ✔️✔️Guidewire
provides approximately 5000 reusable assets or tools to facilitates progress during the
implementation project
1. What is the best practice for project planning? ✔️✔️Plan for what you know
Re-evaluate periodically
Make changes based on new knowledge
1. What are the customon? ✔️✔️Confirm scope, validate sizing, and baseline the
project
1. What does guidewire mean by an inception? ✔️✔️Guidewire projects include an
inception phase to
Confirm the scope of the project
Produce an initial sizing
Create the project baseline
, 1. Who typically attends inception? ✔️✔️Product owner, SME, BA, Developers and
Testers
1. Why does Guidewire timebox inception? ✔️✔️Time box discussions to avoid
excessive details
1. Which criteria are used to prioritize the backlog? ✔️✔️Priority, Value, Size and Risk
1. What are the key objectives from inception? ✔️✔️Formally kick off the project
Train the team on base product and methodology
Introduce the team to agile concepts
Determine an approach to address any product gaps
Document the high-level design for integrations
Explain estimation changes as a result of the workshops
1. What is the Inception best practices? ✔️✔️Utilize the Agile methodology
Map business case to the themes/sub-themes
Estimate stories using points
Introduce base product features and functionality
Document key requirements on story cards
Avoid deep discussions about details requirements
Manage time judiciously
Assess product alignment for each user story
Create new story cards for gap stories
Define a delivery backlog at the end of the inception
Assess business value to help prioritize the delivery backlog
1. Steps to plan a delivery sprint. ✔️✔️Determine team capacity
Define sprint backlog
Validate estimate for each user story
Define tasks for each user story in the sprint
- Assign a resource to each task
- Estimate each task
Add new stories and task as needed
Repeat step 1-5 until sprint capacity is full
1. What are Planning a delivery sprint best practice? ✔️✔️Standardize sizing
guidelines to improve predictability across the program
Standardize the task list before loading the product backlog
Prioritize the release backlog to facilitate planning
Move stories to sprints according to the conceptual sprint plan
Dedicate the team to sprint planning at the start of each sprint
1. What are the recommended guidewire principles? ✔️✔️We are not building a
system from scratch
