Wondershare EdrawMind
Galeria de mapas mentais Sujet central - Clés du succès des projets chez Guidewire
- 8
Sujet central - Clés du succès des projets chez Guidewire
Ce diagramme mental, créé avec EdrawMind, présente les sujets centraux pour assurer le succès des projets chez Guidewire. Il couvre des aspects tels que l'utilisation de l'expérience industrielle de Guidewire, la prise en compte des fonctionnalités non visibles, l'identification des outils et ressources disponibles, l'accès aux ressources, le retour à Guidewire pour assistance, les bonnes pratiques en matière d'exigences, les écueils courants, l'utilisation des principes directeurs et l'alignement stratégique du projet.
Editado em 2023-03-16 17:32:26
Sujet central - Clés du succès des projets chez Guidewire
- Recomendado para você
- Descrição
Sujet central
1. Describe how Guidewire’s industry experience can be leveraged for success
2. Discuss what to consider when not seeing features or functionality
3. Identify the different tools and resources available to aid in project success
4. Describe where to access the available resources
5. Describe when I might come back to Guidewire for assistance
6. List requirement best practices and describe the important aspects of good requirements
7. Identify common requirement pitfalls
8. Describe how using Guiding Principles supports project success
9. Understand how strategic Alignment of the project is key to success and value realization
Guidewire
Transform your business
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.
Keep up with industry trends
Self-Service
Cognitive Computing
Internet of things
Connected
Real-time
Plaformitation
Bundle technology services
Using industry Best practices
Work faster
with less problems of mistakes
arrive at better solutions
Research the best way
Bring innovation
Innovative in standard product
Harness Open Ecosystem Guidewire Cloud
Scalable SaaS model.
Choose when update
Integrations using APIs
Enabled Digital Transformation with Guidewire Digital
Real-time
Self-service
Transactional insurance experience
Integrate seamlessly with Guidewire core systems
Can be tailored to the needs of each end user.
Accelerate Product Lauch with Advanced Product Designer
Rapidly create insurance product
Development from a visual mind map,
Sandard tools
Guidewire expertive
Objectifs
Describe how Guidewire’s industry experience can be leveraged for success
How does Guidewire bring innovation
Not rebuild
Problemes
We have to detect
Why customer want rebuild ?
We want what familiar
Resistance to change
A large number of changes or customizations
A lot of gaps
Descriptions of "how" instead of the capability needed
No clear purpose or benefit
Before requirement workshop
Review the Business Case documentation
Plan a Strategic Value WorkShop
Build plan a Strategic Value Map
Strategic imperatives
Departmental objectives
Project goal
Reference for
Scope
Priority
Change control decision with value in mind
Review Process flows
Review Inception Artifacts
Understandanding
The business itself
The business requirements
The business objectives
The business requirement history
The business process
The InsuranceSuite standard functionality
Reach out Business resources
What system capabilities are they hoping for?
What is this functionality or information needed for?
What is the background behind the requirement?
Who reinventing the legacy system
who is advocating this solution.
Leverage the business value
Help the insurer see the costs versus the benefit
Current with Industry Trends
Leverage Standard Tools
Decreased Maintenance Costs
Built with Best Practices
Transform with Innovation
Abundance of Expertise
Benefits
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
Potential Impacts
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
Customization
Only apply customization to insurance suite when
Increase overall efficiency
Establish a completive advantage
Objectifs
Discuss what to consider when not seeing features or functionality
Guiding Principles
Stay as close as possible to the base configuration
What
Set of rules that help team
Assist decision making
Example
We are not building system from scratch
We are not bound by the way we have always done things
We will challenge current process
We will leverage vendor best practices
We will adherence to "Insurance suite" aligment
We will strive for common workflow, process, and system
We will only automate that witch can and should be automated
We will limit scope as far as practical to accelerate time-to-market
Process
Evaluate each option for alignment
If requirement not aligned, your decision should be clear
Who
Establish by the insurance company's leadership team.
Help for
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
Objectifs
Describe how using Guiding Principles supports project success
Tools
Every member of the implementation team should know the business objectives and business strategies of the insurance company. They should also know how InsuranceSuite supports the attainment of these goals.
Guidewire guiding Principales
Business case Document
Contents
Clear Business Objectif
Clear Business Strategy
Benefit
References
Goal
Defining the business value
Approval process
Focus on value
Strategic Value WorkShop
Guidewire Strategic Advisory Team
1 to three days
During Inception or Pre-inception
Help build benefits case
Complete
Defensible
Measurable
Strategic value
Financial value
Benefits Mapping
Avantages
Features
Theme
Stories
Strategic Value Map
Use to
Making Scope
Priority
Change Control Decision
Contain
Strategic Imperative
Departement Objectif
Project Goals
Metrics
Objectifs
Identify the different tools and resources available to aid in project success
Describe where to access the available resources
Vocabulaire
Projet Succes
Achieve a Business Strategiy
Business Objectives
What are the main goals of the business?
Business Strategy
How do they intend to accomplish these goals?
Strategic Value Aligment
Business align with Strategy
Business case
Project documents
Conflict
Move on
Document the decision
When/What/Who/Why
Priorities/Goals/Feature/Ressources
Alternative solution
Open a Risk item
Risk
Event endanger plan or goal
Something to look for
A risk unavoidable is a issue
Immediate problem is a issue
Log in a Risk Register
Exposure rating
Severe
Significant
Risk rating
Potential
Impact
Likelihood
Escalate the Decision
High severity
Critical path
End date
Financial impact
Scope impact
Provide
Description
Impact
Action plan
Implementation step
All option
Make the decision
Identify the desired outcome
Often disagreement is about how
Use the team's alignement on the outcome
Weigh the options
Guiding Principles
Benefict
System or process impact
Risk
Cost
Choose
Time
Budget
Highest value
Expect it.
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
Objectifs
Describe how using Guiding Principles supports project success
Elaborating requirement
Guide
Don't start from scratch
Don't use legacy system as requirement
Common problem
Solution given as Requirement
Identify need not want or had
What problem are they trying to solve?
What information do they need?
What is the purpose of having it?
How will they use it?
What do they need the system to do?
Why do they need it to function this way?
Don't be a problem-solvers
Requirement not solution
Dont be an order-taker
Challenge or question
Consider all impact
Misunderstanding Terminology
Meaning can change over time
Insurance Terminology
Establish dictionary
Make assumptions
Filters, Biases and Past Experiences
Developper
Solve problem
QA
Testable
Subject Matter Expert
Don't know Guidewire product
Don't know best practice
Business Analysts
Stick to standard
Keep customer happy
Failing to Ask Good Questions
Asking Yes/No question
Lead to predetermined solution
Asking multiple question without wait answer
Not asking question
Solving to soon
Objectifs
Identify common requirement pitfalls
Work Shop
Before
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.
During
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.
After
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.
Do not
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.
Priorize
How - Ms. Cow
Must have
Should have
Could have
Will not have
Criteria
Priority
Value
Size
Objectifs
List requirement best practices and describe the important aspects of good requirements