GW Associate Certification - InsuranceSuite 10.0 Analyst Questions and Answers |Complete
Solutions Graded A+ |100% Correct
What are some planning best practices? -Standardize sizing guidelines and task list
-Move stories to sprints according to the conceptual sprint plan
-only estimate tasks and hours for stories in current sprint
-decide how you will baseline the project
-Define how you will handle group tasks and guiding principles
How/When do we estimate stories? By Points system at the start if the project and also
during each sprint
How/When do we estimate tasks? By Hours and only in the current sprint as part of sprint
planning
What is the reason we use points while estimating? People are better at estimating relative
sizes than detailed hours. There is little value estimating at that detailed level until the work
starts.
Why is team capacity important? Allows you to know what the team can accomplish during
a sprint
Which criteria are used to prioritize a backlog? Priority, Value, Size, and Risk
Iteration Burnout Chart hours on the left Y axis, Points on the right Y axis, and Calendar Days
on the X axis
Ideal Burndown per day = Total of all task hours in iteration/Calendar days in iteration
,What can a team determine based off velocity? they can predict the number of iterations it
will take to complete all work.
Project Velocity tip! Think of it like a marathon; you are trying to set a goal finish time but
you are estimating how long it is going to take you to finish currently based on your mile pace,
so you set your training to eventually get a pace that will allow you to finish in the time you
want, accommodating for sections of the track that are going to be trickier.
Velocity Best Practices -Constant backlog maintenance (prioritizing and estimating),
assessing velocity trends, and tracking Sprint burndowns are key
-update progress each day to produce best burndowns
-Define a trigger/workflow to alert product owners when a story is ready to be accepted
-accept stories in sprint to drive consistent velocity
Review burndown charts to drive timely updates by team
-Compare actual velocity to planned velocity to track overall project progress and assess project
health
-Timeliness drives accuracy; Estimate stories at the start of each sprint for best burndowns
Iteration Cumulative Flow diagram Displays all scheduled work products for the iteration in
incremental collections of days within an iteration as the horizontal axis.
The vertical axis of the chart references the total plan estimates displayed in your specified
units.
Release Cumulative Flow diagram helps you track releases depending on acceptance dates
Release Burnup Displays the exact number of units accepted and those planned for the
release per day
-Tracks how much work has been done on project
, Executive Rollup/Portfolio Item View -Visually track the progress and status of multiple
portfolio items at once
-Provides % complete for each portfolio item
-Red/Yellow/Green status wit respect to planned end dates
Color meanings in Exec Rollup -Do not display Yellow (at risk) until 20% of the portfolio item
duration has elapsed
-Do not display Red (late) until 40% of the portfolio item duration has elapsed
-White, no shading; work has been accepted
-Light grey, some work has been accepted , but the current date is prior to the Planned Start
Date
-Dark Grey, Complete: all work has been accepted
Program View/Release Tracking -Used to track status of teams and features in a common
release
-Provide a program view to the Project Manager
-Shows development work on features has started and the iterations and teams it ties across
-Scrum masters typically also use this type of a view to ensure there is alignment across the
streams
-Requires the PM to load the features into future iterations for planning purposes
What is the core programming language for Guidewire? Gosu
What does application logic control? Detail behavior of the application
Code is used in.... Rules, Classes, Extensions
What can be configured? Validation, Assignment, Function
Solutions Graded A+ |100% Correct
What are some planning best practices? -Standardize sizing guidelines and task list
-Move stories to sprints according to the conceptual sprint plan
-only estimate tasks and hours for stories in current sprint
-decide how you will baseline the project
-Define how you will handle group tasks and guiding principles
How/When do we estimate stories? By Points system at the start if the project and also
during each sprint
How/When do we estimate tasks? By Hours and only in the current sprint as part of sprint
planning
What is the reason we use points while estimating? People are better at estimating relative
sizes than detailed hours. There is little value estimating at that detailed level until the work
starts.
Why is team capacity important? Allows you to know what the team can accomplish during
a sprint
Which criteria are used to prioritize a backlog? Priority, Value, Size, and Risk
Iteration Burnout Chart hours on the left Y axis, Points on the right Y axis, and Calendar Days
on the X axis
Ideal Burndown per day = Total of all task hours in iteration/Calendar days in iteration
,What can a team determine based off velocity? they can predict the number of iterations it
will take to complete all work.
Project Velocity tip! Think of it like a marathon; you are trying to set a goal finish time but
you are estimating how long it is going to take you to finish currently based on your mile pace,
so you set your training to eventually get a pace that will allow you to finish in the time you
want, accommodating for sections of the track that are going to be trickier.
Velocity Best Practices -Constant backlog maintenance (prioritizing and estimating),
assessing velocity trends, and tracking Sprint burndowns are key
-update progress each day to produce best burndowns
-Define a trigger/workflow to alert product owners when a story is ready to be accepted
-accept stories in sprint to drive consistent velocity
Review burndown charts to drive timely updates by team
-Compare actual velocity to planned velocity to track overall project progress and assess project
health
-Timeliness drives accuracy; Estimate stories at the start of each sprint for best burndowns
Iteration Cumulative Flow diagram Displays all scheduled work products for the iteration in
incremental collections of days within an iteration as the horizontal axis.
The vertical axis of the chart references the total plan estimates displayed in your specified
units.
Release Cumulative Flow diagram helps you track releases depending on acceptance dates
Release Burnup Displays the exact number of units accepted and those planned for the
release per day
-Tracks how much work has been done on project
, Executive Rollup/Portfolio Item View -Visually track the progress and status of multiple
portfolio items at once
-Provides % complete for each portfolio item
-Red/Yellow/Green status wit respect to planned end dates
Color meanings in Exec Rollup -Do not display Yellow (at risk) until 20% of the portfolio item
duration has elapsed
-Do not display Red (late) until 40% of the portfolio item duration has elapsed
-White, no shading; work has been accepted
-Light grey, some work has been accepted , but the current date is prior to the Planned Start
Date
-Dark Grey, Complete: all work has been accepted
Program View/Release Tracking -Used to track status of teams and features in a common
release
-Provide a program view to the Project Manager
-Shows development work on features has started and the iterations and teams it ties across
-Scrum masters typically also use this type of a view to ensure there is alignment across the
streams
-Requires the PM to load the features into future iterations for planning purposes
What is the core programming language for Guidewire? Gosu
What does application logic control? Detail behavior of the application
Code is used in.... Rules, Classes, Extensions
What can be configured? Validation, Assignment, Function
