Inefficient legacy systems to a better system.

Provide technology that transforms how they do business.

Replace systems that require coordination of data from multiple systems

Leveraging innovation built into our products.

Self-Service

Cognitive Computing

Internet of things

Plaformitation

Work faster

with less problems of mistakes

arrive at better solutions

Research the best way

Innovative in standard product

Harness Open Ecosystem Guidewire Cloud

Enabled Digital Transformation with Guidewire Digital

Accelerate Product Lauch with Advanced Product Designer

Describe how Guidewire’s industry experience can be leveraged for success

How does Guidewire bring innovation

We have to detect

Why customer want rebuild ?

A large number of changes or customizations

A lot of gaps

Descriptions of "how" instead of the capability needed

No clear purpose or benefit

Review the Business Case documentation

Plan a Strategic Value WorkShop

Build plan a Strategic Value Map

Review Process flows

Review Inception Artifacts

Understandanding

Reach out Business resources

Leverage the business value

Benefits of leveraging base configuration

Leverage project resources and tools more effectively

Decrease developement time

Decrease testing

Decrease maintenance cost

Decrease future upgrades efforts

Lower thier cost ownership

Recreating legacy system features

Missed opportunity to leverage new technology

Increase developement time

Increased testing

Performance issues

Maintenance ussues with release

Limitation and challenges with upgrades

Increase cost

Only apply customization to insurance suite when

Increase overall efficiency

Establish a completive advantage

Discuss what to consider when not seeing features or functionality

Set of rules that help team

Assist decision making

Example

Process

Establish by the insurance company's leadership team.

Requirements

Solve problem

Manage Scope

Change base configuration or stick standards

Develop requirement or place it out scope

Resolve problem choosing option 1 or 2

Describe how using Guiding Principles supports project success

Contents

Goal

Guidewire Strategic Advisory Team

1 to three days

During Inception or Pre-inception

Help build benefits case

Strategic value

Financial value

Benefits Mapping

Use to

Contain

Identify the different tools and resources available to aid in project success

Describe where to access the available resources

Projet Succes

Business Objectives

Business Strategy

Strategic Value Aligment

Business case

When/What/Who/Why

Priorities/Goals/Feature/Ressources

Alternative solution

Risk

Log in a Risk Register

Exposure rating

Risk rating

High severity

Provide

Identify the desired outcome

Weigh the options

Choose

Conflict is okay

It worse accept an wrong idea

Opportunity to uncover issue

Dive deeper into a topic

Questioning a Subject Matter Expert's idea.

Consider all option until you found the best

Strategy, project teams can reach an impasse

Describe how using Guiding Principles supports project success

Don't start from scratch

Don't use legacy system as requirement

Solution given as Requirement

Identify need not want or had

Don't be a problem-solvers

Misunderstanding Terminology

Make assumptions

Filters, Biases and Past Experiences

Failing to Ask Good Questions

Solving to soon

Identify common requirement pitfalls

Review current and future processes.

Review inception notes

Review the Application Guide

Review functionality in the Sandbox.

Review any training materials and training notes.

Prepare for demonstrating functionality.

Identify key questions

Prepare for your audience (supporters, detractors, and those new to the project).

Establish and communicate workshop participation expectations.

Start by reviewing the workshop agenda and expectations.

Review guiding principles and strategic objectives.

Identify participant roles.

Actively listen to the conversation.

Designate a note-taker.

Refer to the standard workflows and screens for the base configuration.

Keep the conversation focused on what the business needs are.

Focus on the “happy path” of the requirement first, and then edge cases.

Use the parking lot for off topic items.

Document decisions.

End by reviewing accomplishments, outstanding items, and action items.

Ensure the User Story Card is fully updated.

Follow-up on any Action Items.

Schedule future follow up meetings if needed.

Update related documents such as process flows, decision logs, or story status.

Escalate any risks or concerns to Scrum Master, PMO, or Steering Committee.

Permit more than one conversation at a time.

Reinvent the legacy system.

Be afraid to suggest: “Let us put that on the backlog".

Revisit decisions that have already been made.

How - Ms. Cow

Criteria

List requirement best practices and describe the important aspects of good requirements