Investigate and Design Phase Plan v1.3

CMS Programme
Stream 2 ClaimCenter v8 on IaaS

Delivery for Project Cre8 - Release 1
Investigate and Design Phase Plan
293286988
Table of Contents
1
DOCUMENT INFORMATION........................................................................................................................ 4
1.1
Document source...............................................................................................................................4
1.2
Revision history..................................................................................................................................4
1.3
Approvals...........................................................................................................................................4
1.3.1
Distribution......................................................................................................................................5
1.4
Related Documents............................................................................................................................5
INTRODUCTION........................................................................................................................................... 7
2.1
Purpose..............................................................................................................................................7
2.2
High-Level Timeline...........................................................................................................................7
2.3
Phases Summary...............................................................................................................................8
2.4
Resource Requirements....................................................................................................................8
2.5
Pre-Requisite Tasks...........................................................................................................................9
PROJECT START UP ACTIVITIES.............................................................................................................11

3.1
Pre-Project Activities for ClaimCenter..............................................................................................11
INCEPTION PHASE.................................................................................................................................... 12
4.1
Inception Phase Overview...............................................................................................................12
4.1.1
Objectives.......................................................................................................................................12
293286988
Private and Confidential
Page 2 of 44
4.1.2
Staffing...........................................................................................................................................12
4.1.3
Key Deliverables............................................................................................................................14
4.1.4
Roles During Inception Workshops................................................................................................14
4.2
High-Level Phase Plan.....................................................................................................................15
4.3
Detailed Phase Plan.........................................................................................................................17
4.3.1
Week 1 (11/05 15/05)...................................................................................................................17
4.3.2
Week 2 (18/05 23/05)..................................................................................................................18
4.3.3
Week 3 (25/05 29/05)..................................................................................................................19
4.3.4
Week 4 (01/06 05/06)..................................................................................................................21
4.3.5
Week 5 (08/06 12/06)..................................................................................................................22
SPRINT 0.................................................................................................................................................... 23
5.1
Objectives........................................................................................................................................23
5.2
Staffing.............................................................................................................................................23
5.3
Sprint Preparation............................................................................................................................23
5.4
Development Team Product Training No Further Training Required.............................................24
5.5
Sprint 0 Plan.....................................................................................................................................24
DEVELOPMENT SPRINTS......................................................................................................................... 25
6.1
Typical Development Sprint Cycle....................................................................................................25
IAAS DESIGN AND BUILD.......................................................................................................................... 27
293286988
Page 3 of 44
1 DOCUMENT INFORMATION
1.1
Document source
This document is maintained as an online document. Contact the IBM Project Executive for the latest version.
1.2
Revision history
Ver
Date
Summary of Changes
Revision
Marks
v0.1
7/04/2015
Initial Draft
v0.2, 0.3
9/04/2015
Further updates
Updated after review with EQC and Guidewire
V0.4, 0.5
101/04/201
5
v1.0
10/04/2015
Released to EQC to support updated Approach
v1.1
16/04/2015
Updated with feedback on v1.0
v1.2
17/04/2015
v1.2.1
17/04/2015
Further review with RS/LC. Inclusion of additional IaaS plan detail.
v1.3
17/04/2015
Version to release with Approach v1.6
Updated following walk-through with RS, LC. Inception planning, Roles &
Deliverables
Table 1 Document Versioning
1.3
Approvals
This document has been approved by the following people.
293286988
Page 4 of 44
Name
Role on Project
Date of
Signature
Approval
Paul Turnbull
IBM Project Executive (GBS)
Jason Barlow
IBM Project Executive (GTS)
Table 2 Document Approvers
1.3.1
Distribution
This document will be distributed to:

Name
Role on Project
John Callcut
CMS Programme Manager, EQC
Linda Smith
CIO, EQC
Ros Smith
CMS Project Manager, EQC
Paul Turnbull
Project Executive (GBS), IBM
Jason Barlow
Project Executive (GTS), IBM
Table 3 Document Distribution List
1.4
Related Documents
The following section will provide a list of key documents that were created as part of the project as well as key other reference documents:
Document Title
CMS Programme - Stream 2 _
Versio
Date
Issued
1.5
10/04/2015
Document Author
Comments
IBM
Project Approach and Budgetary

Estimate Final
Table 4 Other Key Reference Documents
293286988
Page 5 of 44
2 INTRODUCTION
2.1
Purpose
This document is a deliverable of the CMS Programme Project Cre8 Stream 2 (Project Cre8) for Release 1. The purpose of this document is to provide
EQC with details of the plan for the Investigate and Design phase of Project Cre8. This document supports the IBM Approach document CMS Programme Stream 2 _ Project Approach and Budgetary Estimate Final .
2.2
High-Level Timeline
The following diagram shows a high level timeline of the technical delivery of Project Cre8 and how the different streams of activity are timed. This is
indicative at this stage.
293286988
Page 6 of 44
2.3
Phases Summary
The application stream for the Investigate & Design Phase, incorporating the commencement of development, is summarised as shown below:
Dates
Phase
Week 0
Project Start up Activities
Week 1 - 5
Inception
Week 6 7
Sprint PreparationSprint 0
Week 8 onwards
Development Sprints
2.4
Objectives / Activities
Prepare for Inception Phase
Perform project planning activities not completed prior to commencement
In a series of workshops, refine the overall project scope, schedule, and estimate,
and agree on a plan that governs the remainder of the project.
Pilot development sprint to Activities to prepare entire team for commencement of
main development sprint cycles (where not already completed during the Inception
phase.
Develop ClaimCenterre configurations, customisations and integrations via a
sequence of two week long sprints. A total of 8 development sprints are planned.
Resource Requirements
The suggested resource requirements for each Application Delivery phase are as below:
Role
ScrumMaster
Project Manager
Solution Architect
Product Owner
Business Owner
Business Analyst*
System Analyst
Process Experts
293286988
Organisation
EQC
EQC
EQC
EQC
EQC
EQC
EQC
EQC
Start-up
1
1
1 (PT)
0
1 (PT)
0
0
0
Inception
1
1
1
1
1 (PT)
2
1
2
Sprint 0Prep
1
1
1 (PT)
1 (PT)
1 (PT)
2
1
2
Dev Sprints
1
1
1 (PT)
1
1 (PT)
2
1
2
Page 7 of 44
Role
Subject Matter Experts
Organisation
EQC
Start-up
0
Inception
1 + FT 1 (PT)
Sprint 0Prep
0
Technical Specialist
(Network)*
Test Manager
EQC
Dev Sprints
1 FT + As required
(PT)
0
EQC
1 (PT)
1 (PT)
1 (PT)
Project Manager
Solution Architect
Configuration Lead
Technical Lead
Integration Lead
Configuration Developer
Integration Developer
Test Lead
Configuration Tester
Integration Tester
IBM
IBM
IBM
IBM
IBM
IBM
IBM
IBM
IBM
IBM
1
1 (PT)
0
0.51
0.5
0
0
0
0
0
1
1
1
0.51
0.5
1 (PT)
1 (PT)
1 (PT)
1 (PT)
0
1
1 (PT)
1 (PT)
10.5 (PT)
0.5
0
0
1
1 (PT)
0
1
1 (PT)
1
0.51
0.5
3
2-3
1
1 + 1 (PT)3
1
0
0
0
0
1
0
0
1
1
1
0
0
1
1
1
2
1 (PT/remote)
1
1
1
ArcGIS Developer
BluMark
GW Functional Consultant
GW Technical Consultant
ScrumMaster
Project Manager
Solution Architect
Product Owner
Business Analyst
Subject Matter Experts
Eagle
BluMark
GW
GW
EQC
EQC
EQC
EQC
EQC
EQC
1
1 (PT)
0
0
0
1
1
1
2
1 + FT 1 (PT)
1
1 (PT)
1 (PT)
2
0
System Analyst / BA
EQC
1
1 (PT)
1
2
1 FT + As required
(PT)
1
Additional resources can be added where specific needs are identified.* The Technical Specialist (Network) and Business Analyst will be required to review
IaaS documentation around Week 2-5 of Inception to input into, and review IaaS documentation for Network and Security / ACLs.
293286988
Page 8 of 44
2.5
Ref
1
2
3
4
5
6
7
8
9
10
11
12
13
Pre-Requisite Tasks
Task
Agree Integration Architecture
approach
Agree methodology to be used
Documented Inception Plan
Agree use of Rally
Document Inception team logistical
needs
Complete v8 training
Project Structure agreed
Prepare Kick-off Presentation
Provide BA plan
ArcGIS 9 and HIPPO10 functional
specification available to assist
preparation of the User Story
Arrange Rally access
Confirm sandbox availability
Create CMS v4 Problem Statement
293286988
Performed By
IBM Solution Architect works with IBM IBM
Tech Lead and Lead DeveloperIntegration
Lead, consulting with Guidewire Technical
Consultant
EQC and IBM Project Managers
EQC and IBM Project Managers + Guidewire
IBM Project Manager
Status
CompletedOpen
IBM Core Team

EQC Core Team
EQC BA
IBM Solution Architect
Completed
Planned for week 0 (commencing 4 May 2015)
In IBM Project Approach
Open
In progress
In progress
EQC IT (Paul Cooper)

IBM Dev Team, EQC Systems Analyst
EQC Business Analysts, Product Owner
Open need names to be provided to IT

Open
Open
Completed
Available
Completed
Completed
Page 9 of 44
3 PROJECT START UP ACTIVITIES

3.1
Pre-Project Activities for ClaimCenter
The table below notes some pre-project activities are planned to get prepared for the Project Inception
Week 0
Dates
TBD
Already Done
Implicit in Business
Case
Meetings and Activities

IBM Solution Architect works with IBM Tech Lead and Lead
Developer on Integration Architecture Approach
Discuss Guidewire project methodology and this inception

plan
Socialise the Agile delivery methodology
Inception team needs
Discuss Guidewire Software product training

needsGuidewire v8 Introduction Training
Project team structure
Kick-off meeting preparation
Refine project planning, project management and
Already completed
Needs to be covered
earlierScheduled for
Week 0
Needs to be iIncluded
in Proposal
TBD
Update in Wweek 0
293286988
Objectives and Deliverables

Review Architecture needs and formulate
an integration strategy
Review project methodology

Establish the Inception Plan
Agree use of Rally, as per joint EQC &

Guidewire discussion mid-April 2015
Discuss the logistical and technical needs
for inception. Establish a plan to have
everything in place for the start of inception
Set training expectations and establish a

target training schedule.
Communicate plan with the Education team
to insure training resources are available
and schedule for your projectTrain project
team in ClaimCenter v8 usage and
functions
Staffing plan
Distribute and discuss the sample kick-off

presentation
Project documents in place to support

Page 10 of 44
Update in wWeek 0
governance documents
Confirm logistics for meeting room bookings, delegates
project activities
All logistics in place for Inception
workshops
Note that there is also training for EQC staff planned for week 0.
293286988
Page 11 of 44
4 INCEPTION PHASE
4.1
Inception Phase Overview
Project Inception is the first phase in the Guidewire implementation methodology, and will be used as part of Project Cre8. During project inception, the joint
team refines the overall project scope, schedule, and estimate, and agrees on a plan that governs the remainder of the project.
The Inception phase will be used to organize the project team, set common objectives for all members of the team, and provide appropriate education about
ClaimCenter and EQC processes and systems. During this phase, a series of meetings will be held to kick off the project, confirm the scope of the project,
and establish guidelines for communication and governance. In addition, the activities and key deliverables for the project will be reviewed, confirmed and
assigned to the appropriate project resources. EQC's and IBMs project planning tools will be used to develop a project schedule, assumptions, and capacity
plan that matches available staff to the effort required to complete the project.
The Inception phase is also used to make high-level design decisions, for example to determine how the major systems will communicate with each other.
4.1.1
Objectives
The key objectives of this phase include:

Arrange all remaining logistics for the project team (where not covered in the project start up activities)
Agree on project governance, project management, and communication procedures (where not covered in the project start up activities)
Educate the Guidewire team on the customer's EQCs business and systems environment
Inform all project team and stakeholders as to the project methodology being utilised
Educate the EQC team on the Project Plans and Solution Architecture
Set up the technical infrastructure necessary for the following phase, excluding IaaS environments
Schedule project team training (where required)
Confirm detailed project scope and release planning if necessary
Refine the detailed project delivery estimate including all major configuration work and integration points
Estimate the staffing required for the next phase and identify the required people
Complete planning, scheduling and estimates for the Final Business Case to complete the project delivery
Inform parties outside of CMS (e.g. FMIS, BIU) of intended approach & schedule
4.1.2
Staffing
This phase should include participation by the following people:

293286988
Page 12 of 44
(The names indicated are those expected at time of writing to fill these roles)
Roles in the Core Team are divided into the Configuration Track for more Business and Functional discussion and/or the Integration Track for more technical
discussion.
Core team (full-time):

Role
EQC ScrumMaster
EQC Project Manager
EQC Solution Architect
EQC Product Owner
EQC Business Owner
(when available)
EQC Business Analysts
EQC Systems Analyst
EQC Process Experts
EQC Test Manager
IBM Project Manager
IBM Technical Lead and
configuration developers
IBM Configuration
Developers
IBM Integration Lead
IBM Integration
Developers
IBM Test Lead
Guidewire functional
consultant
Guidewire technical
consultant
EQC ScrumMaster
293286988
Name
Rob Dongol
Ros Smith
TBC
Julie Robertson
Jayne Lapin
Will Donnelly
Veronica Taylor
Mark OKeefe
Dan Taylor
Daniel Teasdale
Donna Gregory
Terrence Daken
Matt Haley
Chris Anderson
Config Track
Split
Split
Yes
Yes
Yes
Yes
Split
Yes
Split
Yes
Split
Split
Yes
Yes
Yes
If available
If available
Peter Tan
Ralph Fox
Dean Sole
Max Ilic
Chris Anderson
Sun Yi Jin
Raj Bhandaru
Ba Truong
Integration Track
Yes
Yes
Yes
Yes
Yes
Alex Zak
Yes
Rob Dongol
Page 13 of 44
EQC and IBM project manager

EQC Product Owner
EQC Business Owner
EQC business lead
IBM project manager
IBM Technical Lead and configuration developers
IBM integration lead and integration developers
Ros Smith
TBC
Julie Robertson
Jayne Lapin
Guidewire functional consultant

Guidewire technical consultant
Ba Truong
Alex Zak
Extended team: core team plus following roles

EQC Integration Project ManagerInfrastructure representative
Subject Mmatter eExperts
EQC Business Owner
GIS Developers
Content Manager Developer
IBM Infrastructure / IaaS Project Manager
IBM Infrastructure Architect
IBM ClaimCenter Testers
IBM Integration Testers
Agile Coach

IBM Test Lead
External Parties
EQC BIU Team
EQC Finance System
EQC ITechnical Specialists Ops (e.g. Network)
293286988
Will Donnelly Veronica Taylor

Terrence Daken
TBC
Chris Anderson + Peter Tan, Ralph Fox, Dean Sole, Max Ilic
Chris Anderson + Sun Yi JinIBM Test Lead Raj Bhandaru
TBC
TBC
Jayne Lapin
Dave Timmins + TBC
Harry SiemerTBC
TBC
Paul Eades
TBC
TBC
Jesse (Boost)
Paul Eades
Raj Bhandaru
TBC (e.g. Tamara Duran, Paul Abraham)

TBC
TBC (e.g. Mike Yalden)
Page 14 of 44
The inception phase activities may not require all of the business analysts, configuration developers, integration developers, and subject matter experts who
will be involved in the Implement phase. However, these roles should be represented in the Inception phase to review requirements, create high-level
designs, and develop estimates.
4.1.3
Key Deliverables
The following are key deliverables of the Inception Phase:

Completed Planning Matrix for project delivery
Updated estimates, schedule and plan to feed into the Implement PhaseFinal Business Ccase and Statement of Work(s)
Functional Gap Analysis
Project Risk Analysis
Conceptual sprint plan
Prioritized backlog list
Updated stories (not final, complete list)
High Level design documents for Integration interface points
4.1.4
Roles During Inception Workshops
Workshops are intended to be run as joint, collaborative efforts. Guidewire will be a key facilitator, and EQC and IBM staff will jointly drive the sessions to
achieve the objectives. The key staff will depend on the nature of the workshop, e.g. the integration sessions will be run jointly by the Guidewire Ttechnical
Consultant, resource and the IBM Iintegration Llead and IBM Architect(s).
4.2
High-Level Phase Plan
The table below describes the overall schedule for the project inception phase. A detailed schedule is provided in the following section.
Week 1

Core team orientation
Perform kick-off meeting and EQC
orientation (Sponsor, EQC PM)
Kickoff meeting
Install sandbox (if not already available)
Arrange Rally access (EQC IT)
293286988

Arrange logistics for Guidewire team (EQC)
Secure hardware for core team (per
Organisation in Staffing)
Introduce core team to sandbox application
Provision of Agile tracking tool and common
reference repository
Success Criteria to Start Week

Staff and Meeting rooms are identified
and booked
Guidewire Functional Consultant is
available on-site
Access to sandbox applications
Project Team has completed
Page 15 of 44

Perform kickoff meeting and EQC
orientation (Sponsor, EQC PM)
Scope review meeting
Guidewire Methodology TrainingCore
EQC Training (0.52 days)
ClaimCenter v4 ReviewLoad Guidewire

User Stories into Rally (GW)
Week 2
Detailed business process meetings

Detailed integration meetings

Confirm Project drivers, objectives, key
success criteria, scope and goals
Agree on project governance, project
management, and communication
ScheduleP project team training
Agree onConfirm estimating approach and
tool
Confirm overall scope, including integration
points
Core EQC Team Core Team are fully trained
in Guidewire methodology and Agile
processes
User Story development is consistent and
understood by all parties
Current State issues are understood
High-level process flows
Identify functional priorities
Identify development dependencies
Functional gaps recorded as new User
Stories
User Access Control type identified
(required for IaaS design)
Initial estimations

ClaimCenter v8 Introduction training
Week 3

(cont.)
GIS functional scope meeting
Detailed integration meetings
Infrastructure ReviewDraft Product
Backlog
Assessment of Gap Analysis
Week 4
293286988

Overall integration architecture
Draft consolidated estimate
Release plan with scope and integration
points per release (if necessary)
Identify functional priorities
Identify development dependencies
Complete estimates
Project team have completed

Guidewire methodology training
All Project team members are clear on
scope, objectives and Agile delivery
approach
ClaimCenter v4 problem statement is
socialised and understood by
Guidewire
Applicable ClaimCenter v8 OOTB
processes are identified
User Access Control requirements are
documented
Progress from Week 2 in on schedule
Guidewire Technical Consultant is
available
Progress from Week 2 in on schedule

Page 16 of 44

(cont.)
Detailed integration meetings (cont.)
Refine Product Backlog
Implement Phase preparation
Prepare draft Conceptual Sprint plan
Week 5
Finalise estimates and Final Business

Case Planning
Finalise Product Backlog
Prepare Final Conceptual Sprint plan

Staffing requirements
Grooming of backlog
Preparation of stories
Draft Sprint plan
Support drafting of Final Business Case by
EQC
Support drafting of EQC Board memo drafts
Grooming of backlog
Preparation of stories
Final Business Case by EQC
EQC Board memos by EQC
Hardware/software environment schedules
for next phase
Conceptual Sprint plan
Staffing for next phase
Estimates are completed and reviewed

Dev & SIT environments are physically
available
All business process meeting have
been completed
Product Backlog is finalised (ready for
prioritisation)
The Inception phase has been planned as having a five week duration. Consideration was given to reducing this to four weeks, but the period has been
retained as five to enable sufficient time to prepare business case information, revise estimates and refine the product backlog and user stories.
293286988
Page 17 of 44
4.3
4.3.1
Detailed Phase Plan

Week 1 (11/05 15/05)
Monday

Core Team introduction
Kick-off meeting
Guidewire Training
Tuesday
Estimation / Sizing
Approach
Arrange logistics
Arrange logistics for Guidewire team,

Ensure sandbox availability
Secure core team hardware
Load common documentation into Rally
Install Guidewire application
Distribute instructions to core team
Confirm sandbox
environment
293286988
Description or Topics
Orientation and team introductions
Review and confirm Inception Phase tasks and
deliverables
Introduce and review sample documents and
templates
Agree where / how Gap Analysis is recorded
Overall project objectives
Project governance / Project planning and
management
Tentative project plan
Inception phase activities
Staffing and roles
Communications
Estimating approach and tool
Guidewire methodology training for EQC Project
teamstaff (afternoon)day 1 of 2)
Estimating approach (1 hour)
Participants
Core team
Core Team
, Extended team
, Steering Committee,
business Business and IT
Stakeholders
Core EQC staffTeam

Business Owner
Guidewire Functional Consultant
IBM Project Manager
IBM Tech Lead
IBM Test Lead
Business Analysts
EQC project manager,
IBM Project Manager, Guidewire
project manager
Guidewire consultants,
infrastructure lead, technical lead
Page 18 of 44

Guidewire Training
Arrange Rally access
Load sprint planning tool
Guidewire methodology training for EQC staff (day 2
of 2)
Provision logins required for new users
Import the prioritized product backlog list into Rally
(the sprint tracking tool)
Rally Sprint Tracking Tool

Maintenance
Functional team
overview (how to
document and configure
changes to Guidewire
applicationEQC led)
Technical team overview

(Guidewire architecture
and integration)
Scope review meeting
Wed (morning)
Business process
overview meeting (EQC
led)
Wed (afternoon)
/ Thursday
Business process
meetings to confirm high-
Wednesday
293286988
Ensure project teams are established

Ensure project team has tool access
Ensure tool and stories are ready for the first
planning session
Detailed demonstration of Overview of Guidewire v4
application
Review of current problem statement
High Level Requirements
High Level Processes
Overview of configuration
Overview of rules engine
Review requirements templates
Demonstrate and review Agile functionality
Review existing systems environmentHighlight areas
of functional alignment
Discussion of Guidewire architecture
Discussion of integration mechanisms
Review of existing customer EQC systems and
integration architecture
Confirm overall scope, including integration points
Introduce EQC processes and requirements
Confirm common understanding of high level
configuration
Describe overall functional scope
High-level Guidewire process flows
Coverages and mapping to exposure types
Participants
EQC staff
EQC IT
EQC Product Owner
EQC Subject Matter Experts
Rally Tool owner
EQC BA
Business team, configuration team,

subject matter experts, Guidewire
functional consultantCore teams
Integration team, architect,

Guidewire technical consultant
Guidewire consultants, EQC and

IBM project managers, customer
EQC leads
Core team
Core Team
Page 19 of 44
Thursday

level configuration
requirements (Guidewire
led)
Business process
overview meeting
Identification of core OOTB ClaimCenter functionality
not in EQC scope (i.e. Areas to remove / disable)
Participants
Business team, configuration team,

subject matter experts, Guidewire
functional consultant
Infrastructure meeting
Introduce customer EQC processes and

requirements
Confirm common understanding of high level
configuration
Describe overall functional scope
Review current customer EQC infrastructure
Plan how Guidewire application will fit within the
systems environment
Identify potential architecture issues
Discuss hardware status and planned environments
(dev, test, QA, production)
Integration team, architect, DBA,

infrastructure, Guidewire technical
consultant
Friday
Review and
documentation
Guidewire consultants, EQC and

IBM project managers, customer
EQC leads
Friday
Review and Preparation

for Week 2
Estimation stocktake
(1 hour)
Core Team
4.3.2
Team review of estimates already loaded.
IBM Project Manager

EQC Project Manager
IBM Development & Test Teams
Week 2 (18/05 23/05)
Monday
Tuesday
(configuration
track)
293286988

Business process meetings to
confirm high-level
configuration requirements
Lines of business in scope
Jurisdictions
Coverages and mapping to exposure types
Participants
Project Team members
involved in business analysis,
design and discovery
Page 20 of 44

Thursday
(configuration
track)
Friday
Integration meetings to
confirm high-level integration
requirements and data flows
Monday
Business process meetings to

confirm high-level
configuration requirements
LOB-specific screens
Claim (Loss Details, Exposure, Incident, etc.)
New Claim Wizard
LOB-specific rules
Workplan
Pre-update
Validation
Tuesday
Wed / Thurs
293286988
Business process meetings

(continued)
Organisation structure
Groups, users, group types
User attributes
Regions
Security
Roles and permissions
Custom permissions
Authority limit profiles
ACL security
Activity management
Activity patterns
Workplan screens
Segmentation and assignment
Screens
Claim (Loss Details, Exposure, Incident, etc.)
New Claim Wizard
Rules
Workplan
Pre-update
Validation
Policy screens
Common screens
Participants

involved in integration,
conversion, or legacy system
modification
Core Team
(for Org Structure & Security
sessions only)

involved in business analysis,
design and discovery
Page 21 of 44
Thursday
(morning)
User Access Control types
Friday
Review and Review and

document findingsPreparation
for Week 3
(1 hour)Consolidate estimates
4.3.3
Desktop
Search
Team
Dashboard
Address Book
Claim (common screens only)
ContactManager
Single Customer View
Contact hierarchy
Search criteria
Screens
Business rules
Identify User Access Control requirements used in IaaS
security design. Built on Mondays session.
Participants
Core Team
Guidewire team, customer
EQC project manager,
customer EQC leadsCore
Team
IBM Project Manager
EQC Project Manager
IBM Development & Test
Teams
EQC Business
AnalystsGuidewire team,
customer EQC project
manager, customer EQC
leads
Week 3 (25/05 29/05)

Mon ThursWednesday
293286988
Financial screens
Participants
Page 22 of 44

-Thursday
(configuration
track)
Monday
Technical team overview

(Guidewire architecture
and integration)
Wednesday
GIS Capabilities
Content Management
Tues ThursMondayThursday
(integration track)
Integration meetings
(continued)
Infrastructure meeting
293286988
Transactions
Limits and deductibles
Authority limits
Business rules:
Initial reserves
Transaction approval and approval routing
Notes and documents
Complex claims
Evaluations
Negotiations
Litigation
History
Claim actions
Discussion of Guidewire architecture
Discussion of integration mechanisms
Review of existing EQC systems and integration
architecture
Catastrophe Management
GIS Functionality
Linking
Address Validation
Document Storage
Document Retrieval
Overview of interfaces
Middleware and integration architecture
File sizes and formats
Guidewire and IBM EQC responsibilities
Individual integration points
Conversion Individual integration points
Conversion
Review current EQC infrastructure
Participants
IBM Core Team

Guidewire Technical Consultant
Core Team
GIS Developers (Eagle)
Core Team
Content Manager Developer
(remote)
Project Team members involved in
integration, conversion, or legacy
system modification
Tech Lead, IBM Solution Architect,
Page 23 of 44

(IBM led)
Friday

for Week 4Review and
document findings
(1 hour)Consolidate draft
estimates
Plan how Guidewire application will fit within the
systems environment
Identify potential architecture issues
Discuss hardware status and planned environments
(Dev, SIT, UAT, Perf-Test, Training, Prod, DR)
Initial draft SOW

Initial Gap Assessment
4.3.4
Participants
Infrastructure Architect, Guidewire
technical consultant
Core TeamGuidewire team, customer

EQC project manager, customer
EQC leads
IBM Project Manager
EQC Project Manager
EQC Business AnalystsGuidewire
team, customer EQC project
manager, customer EQC leads
IBM Project ManagerGuidewire
project manager
Guidewire project manager
Week 4 (01/06 05/06)
Monday
Tuesday
Thursday
Monday-Friday

Business process
meetings (continued)
Product Backlog
Grooming
Sprint Planning
Business process
meetings (continued)
Final requirements
293286988
Complete any business process meetings not completed
in previous two week
Review initial Product Backlog
Review documentation of gap analysis
Initial Prioritisation
Draft initial Sprint Plan
Review initial Conceptual Sprint Plan
Complete any business process meetings not completed
in previous two week
Participants
Core Team
Core Team
Project Team members involved in

business analysis, design and
discovery
Core team
Page 24 of 44
Friday
4.3.5

gathering
Prepare draft estimates
Develop Product Backlog
FinalInitial Business Case
preparationactivities
Risk Analysis
Document project risks and mitigation steps
Gap Assessment
Draft documentation of project gaps.

for Week 3Draft
Conceptual Sprint Plan
(1 hour)
Finalise schedule and plan for input to Final Business

Case
Participants
Core team
Core team
Guidewire project manager, EQC
Pproject Mmanager
IBM Project Manager
Guidewire project manager,
customer EQC project manager
Core TeamGuidewire project
manager, EQC + IBM project
manager, Scrum Master
IBM Project Manager
EQC Project Manager
Week 5 (08/06 12/06)
Monday
Monday-Friday
Tues - Thurs

Environment Preparation
Load sprint planning tool
Gap AssessmentFinal
requirements gathering
Prioritisation Workshops
Finalise estimates
Refine Product Backlog
Business Case
preparation
Risk Analysis
Gap Assessment
293286988
Preparation of Dev, SIT environment for Sprint 0
Import the product backlog list into Rally (the sprint
tracking tool)
Finalise documentation of project gaps.
Participants
IBM Technical Lead
Guidewire Technical Consultant,
ScrumMaster
EQC Project ManagerCore team
Prioritise the Product Backlog
Core Team
Core team
Core team
Document project risks and mitigation steps

Finalise documentation of project gaps.
Page 25 of 44
Thurs
Circulate and finalise

Conceptual Sprint Plan
Circulate and finalise Conceptual Sprint Plan
Friday
Sprint 0 Readiness
Finalise any outstanding impediments for Sprint 0
293286988
Participants
Guidewire project manager, EQC
Project Manager
+ IBM Pproject Mmanager, Scrum
master
Page 26 of 44
5 SPRINT PREPARATION PLAN0

The focus of Sprint Preparation for Project Cre8 is to prepare the development team and the product backlog for the first development sprint. For Project
Cre8, most of the training and backlog refinement activities that will could have been covered in a Sprint 0 will already have been performed prior to or
during the Inception phase. Therefore, the sprint 0 will consist of a pilot development sprint to prepare the team for the main development sprints to follow.se.
5.1
Objectives
The key objectives of this phase include:

Training the Development Team to configure the Guidewire product
Update and prioritize the product backlog list
Update story details using the backlog priority to insure they are prepared for the first development sprints
Load the sprint tracking tool with the product backlog
Make team and other needed updates to sprint tracking tool
Update stories and add new stories as necessaryFamiliarise the team with the agile development process to be used for the main development sprints
Identify and resolve questions and issues that may impact on the development and test process
Verify the environments are ready for development and testing
5.2
Staffing
This phase should include participation by the keyfollowing people involved in the development sprints. Not all developers and testers:
Core team (only where needed):
o EQC project manager
o EQC business lead and business analysts
o IBM configuration lead
o IBM integration lead
o Guidewire project manager and functional consultants
Guidewire will:
Provide coaching and assist in story writing and prioritisation (if needed)
Assist instructors during ClaimCenter training (if needed)
The IBM/EQC team will:
Attend training as needed
Continue requirements gathering as needed
Update stories and product backlog as needed
293286988
Page 27 of 44
5.3
Make final preparations for the start of development
Sprint Preparation
Before the first development sprint begins other important tasks must be completed to insure the project team and the product backlog are prepared. These
tasks, and their approach in Project Cre8, include:
Training in ClaimCenter v8 for Development Team
Business meetings to finalize Product Backlog and Stories
Prepare environment for Sprint 1
The approach for these tasks for Cre8 will be:

Development Sprint Preparation Task
Approach for Cre8
Training for Development team in ClaimCenter
Has been completed prior to the Inception phase for the core
Foundation
development team. The only training to be performed during
Configuration
Sprint 0 for Cre8 will be if training gaps are identified, or training
Integration
for new staff is decided as being necessary
Business meetings to finalize Product Backlog
Is planned to be performed during the Inception phase. Further
and Stories
activities will only be performed during Sprint 0 if the product

backlog has not been finalised.
Prepare environment for Sprint 0 and Sprint 11
After delivery of the DEV and SIT environments, the development

team will perform the final configuration and integration steps to
prepare the environments for use during Sprint 0 and Sprint 11
As both training and finalizsation of product backlog are being performed prior to the sprint preparation, the assessment is that the further sprint preparation
can be shorted to a two week duration, and will take the form of a pilot sprint.
293286988
Page 28 of 44
5.4
Key Deliverables
5.5
Updates to Prioritized backlog list (if needed)
Updated stories (if needed)

Trained Development Team
5.6
(if any training gaps are identified)
Development Team Product Training No Further Training Required
Listed below is the training plan for the development team. This shows that Aall planned training for the core team has will have been completed prior to the
Sprint Preparation phase, i.e. the three recommended courses will have been completed as per below:.
Dates
Has been
completed
Has been
completed
Has been
completed
Course
Introduction to ClaimCenter 4 days
Configuration Foundation 4 days

ClaimCenter Advanced Configuration 4 days
ClaimCenter Integration 4 days
Attendance
Business Analysts
Configuration resources
Integration resources
Any further training for new IBM resources will be arranged and managed by the IBM team.
5.7
Sprint Preparation 0 Plan
Week 61/2
(Start Mon 15/06)
293286988

Prepare environment for Sprint 0 (if not performed in
final week of inception)Sprint Planning meeting.
Business meetings to finalize Product Backlog and

Dev/SIT environments configured sufficiently to
commence Sprint 0
Prepare product backlog and stories for
Page 29 of 44

Week 72/2
(End Tues 23/06)
StoriesPilot development sprint,Daily Scrum

meetings
Sprint execution
Daily Scrum meetings
Sprint execution
Sprint Retrospective
Sprint ReviewPilot development sprint,Business
meetings to finalize Product Backlog and Stories
Prepare environment for Sprint 1
developmentRefer Development Sprints section for details
Refer Development Sprints section for detailsPrepare

product backlog and stories for development
Dev/SIT environments configured sufficiently to

commence Sprint 1
Notes on Sprint Preparation Plan:

The Introduction to ClaimCenter Training has been completed by the development team prior to the sprint 0
The Foundation Training has been completed by the development team prior to the sprint 0
The Product configuration and Product Integration training has been completed by the development team prior to the sprint 0
293286988
Page 30 of 44
6 DEVELOPMENT SPRINTS
The Implement Phase is being scheduled for at least eight development sprints. This process would also be repeated in the Stabilisation Phase should
additional sprints be required and warranted.
The sprints follow a continuous, collaborative and repeated process.
All Developers include ClaimCenter, Integration, GIS and DB2 Content Manager developers. There is no distinction in the nature of the role.
6.1
Typical Development Sprint Cycle
Week 1 of 2
Week 2 of 2

Sprint Planning Meeting
(Tues afternoon of first
weekstart of week 1)
Sprint Review
(Tues morning of second
week)
Sprint Retrospective
(Tues morning of second
week)
293286988
Identification of sprint scope
User Stories logged into Sprint Backlog from Product
Backlog
Agree definition of done and ready status for sprint
Define acceptance criteria against each user story
Create and agree on tasks for each user story
Assign estimate effort for each task
Initial prioritisation of user stories in current sprint
Review of sprint delivery
Demo functioning delivery
Capture good / bad / ugly learnings from previous Sprint

Highlight what should change in subsequent sprints
Assign owner and incorporate action items from
retrospective into next sprint
Participants
ScrumMaster
Product Owner (lead)
All Developers
All Business Analysts
All Testers
Guidewire Consultants
Solution Architects
SMEs (if required)
ScrumMaster (lead)
Product Owner
All Developers
All Testers
Solution Architects
SMEs (if required)
ScrumMaster (lead)
Product Owner
All Developers
All Testers
Guidewire Technical Consultant
Page 31 of 44
Week 2 of 2
Daily Activities
Sprint Retrospective (end

of week 2)
Review of sprint delivery

Assign owner and incorporate action items from
retrospective into next sprint
Backlog Refinement
Meeting
Grooming of Product Backlog

Estimation of complexity
Preparation for next Spring Planning Meeting
Review of Sprint progress / burndown / reporting metrics
Identification of impediments
Re-prioritisation of sprint workload
User story refinement

Development for sprint tasks
Code check in
Code review and UTP documentation
Demo/walkthrough of user story and functional delivery
Sign-off of user story
Code check in
Defect resolution
Rally Administration
Build & continuous deployment for sprint delivery
Test Planning
Test Execution
Issue and Defect Identification and Reporting
Daily Scrum (30 min)
Sprint Execution
Deployment
Testing
293286988
Participants
ScrumMaster (lead)
Product Owner
All Developers
All Testers
Solution Architects
SMEs (if required)
ScrumMaster (lead)
Product Owner
ScrumMaster (lead)
Product Owner
All Developers
All Testers
Solution Architects
SMEs (if required)
All Developers
Product Owner
Lead DeveloperTechnical Lead

Integration Lead
/ Release Manager
All Developers
All Testers
Page 32 of 44
Rally Administration
Participants
Moving into the next Sprint

Prior to completing one sprint and moving into the next, the status of delivery for each User Story in the sprint is assessed, both at the daily scrum and at the
Retrospective. Stories which have not completed successfully may be held over for the next sprint.
293286988
Page 33 of 44
7 IAAS DESIGN AND BUILD

Refer also the GTS work request and Project Approach document for further information on this phase.
Week
Week 1
Meetings and
Activities
Create connectivity to
IBM Government IaaS
service offering
Outputs
Participants
Network access in place
IBM IaaS Infrastructure

specialists
Detailed design documents
IBM IaaS Infrastructure

specialists
Week 1 - 8
Create Detailed
Designs based on
current Solution
Architecture
documentation
Week
Implementation based
on Detailed Designs
293286988
Establish access to IaaS resources and

configuration Portal
Establish a segregated network to provision
application environments
Establish connectivity bi-directional to the
current EQC CMS platform
Access and Authentication System and
User authentication to application
components and directories
Systems Management Backup,
Monitoring, Antivirus, DNS configuration
Application functionality Installation and
configuration of applications
IBM Integration Bus
Claim Centre including Oracle Database
Content Manager including DB2 Database
ArcGIS provide input (GBS delivered
document)
Application connectivity Connectivity
between applications Security Detailed
Design
Server and Operating System Resource
allocation and OS configuration
Install and configure application
environments
Configure each environment with
environment specific configuration
Application configuration
Page 34 of 44
Week
Meetings and
Activities
Week
Week 1
Week 2
Week 3
Participants
Network and firewall configuration
Connectivity testing
Application testing
Finalise Detailed Design documents
Handover
Meetings and
Activities
Resource allocation
Outputs
Participants
Request resources as per Work

breakdown Structure
None
IBM Infrastructure Project

Manager
Project resources
engaged
Project resources assigned

Project overview provided
Network Design continues
Project Resources engaged
Project schedule defined

Establish project meetings and reporting
Detailed Designs starts for all System and
Infrastructure Detailed Designs
Interim environment build starts
Oracle infrastructure configuration starts
None

Manager
IBM Network Architect
EQC Technical Specialist
(Network)
Manager
IBM Security Operations
Manager
IBM Technical SMEs
Completed connectivity documents and

supplied to Design Authority (IBM) for
approval to implement
WAN connectivity
documentation completed
Document network
connectivity to IaaS
over and above POC
requirements
Detailed Design starts
Security Design Starts
Interim Environment
build Starts
Week 4
Outputs
Oracle infrastructure
configuration Starts
Security and Network
Designs for EQC to
IaaS for WAN
connectivity completed
293286988
IBM Network architect

IBM Security Operation
Manager
Page 35 of 44
Week
Meetings and
Activities
Resource allocation
Outputs
Participants

breakdown Structure
None

Manager
Week 5
WAN access
implemented
Network/Security design for WAN

connectivity is implemented
WAN connectivity
established
IBM Technical SMEs
Week 6
IBM Design Authority

Final Approvals
IBM Design Authority approvals final

design documents
Completion and availability of Interim
environments
Interim environments
available for GBS/EQC
application development
IBM Technical SMEs
Oracle infrastructure configuration

implemented
Detailed Design and infrastructure designs
provided to EQC for review and input
Oracle infrastructure ready

for use
none
IBM Technical SMEs
Finalise As Designed documents with

EQC feedback and additional required EQC
environment specific information
Patterning of environments is applied and
tested
Pattern deployment as a process is
finalised
Detailed Designs As Built

are finalised
Implemented development environment as

per designs
PM engages EQC for signoff of deliverables
and milestones to date
Development Environment
available for EQC/GTS
Week 1
Interim Environment
build completes
Week 7
Week 8
Week 9
configuration finishes
Provide As Designed
Design Documents to
EQC for review and
input where required
Incorporate EQC
feedback of Design
Documents
Pattern Development
environment and test
pattern deployment
Week 10
Finalise build of
development
environment ready for
hand over
PM requests formal sign
off
293286988
IBM Technical SMEs

Manager
(Network)
IBM Technical SMEs
(Network)
EQC Business Analyst
(security)
IBM Technical SME

Manager
(Network)
Page 36 of 44
Week
Week 1
Week
Week 1
Week 2
Week 3
Meetings and
Activities
Resource allocation
Outputs
Participants
None

Manager

breakdown Structure
EQC Business Analyst

(security)
Participants
Meetings and
Activities
Resource allocation
Outputs
None
IBM Project Manager

Document network
connectivity to IaaS
over and above POC
requirements
Project resources
engaged

breakdown Structure
Network Design continues
Project resources assigned

Project over view provided
Project Resources engaged
IBM Project Manager

IBM technical SMEs
Detailed Design starts
Project schedule defined

Establish project meetings and reporting
Detailed Designs starts for all System and
Infrastructure Detailed Designs
Interim environment build starts
Oracle infrastructure configuration starts
None
IBM Architect
Manager
IBM Technical SMEs
Completed connectivity documents and

supplied to Design Authority (IBM) for
approval to implement
WAN connectivity
documentation completed
IBM Network architect

IBM Security Operation
Manager
Security Design Starts

Interim Environment
build Starts
Week 4
configuration Starts
Security and Network
Designs for EQC to
IaaS for WAN
connectivity completed
Week 5
Wan access
implemented
Network/Security design for Wan

connectivity is implemented
WAN connectivity
established
IBM Technical SME
Week 6
IBM Design Authority
IBM design authority approvals final design
Interim environments
IBM Technical SMEs
293286988
Page 37 of 44
Week
Week 1
Meetings and
Activities
Resource allocation
Outputs
Participants

breakdown Structure
None

Manager
documents
Completion and availability of Interim
environments
available for GBS/EQC

Oracle infrastructure configuration

implemented
Detailed Design and infrastructure designs
provided to EQC for review and input
Note: may also be available in week 7 for
review.
Finalise As Designed documents with
EQC fed back and additional required EQC
environment specific information
Patterning of environments is applied and
tested
Pattern deployment as a process is
finalised
Oracle infrastructure ready

for use
none
Implemented development environment as

per designs
PM engages EQC for signoff of deliverables
and milestones to date
available for EQC/GTS
Final Approvals
Interim Environment
build completes
Week 7
Week 8
Week 9
configuration finishes
Provide As Designed
Design Documents to
EQC for review and
input where required
Incorporate EQC Feed
Back of Design
Documents
Pattern Development
environment and test
pattern deployment
Week 10
Finalise build of
development
environment ready for
hand over
PM requests formal
sign off
Detailed Designs As built

are finalised
IBM Technical SMEs

IBM Technical SMEs
IBM Project Manager
IBM Architect
EQC Design review
IBM Technical SMEs
IBM Architect
IBM Technical SMEs

IBMC Architect
Manager
While no significant EQC input into the IaaS design is expected week 1 to week 7, there may be occasional ad hoc questions submitted to the EQC team. The
expectation is that the effort to respond to these will not be major, and can be accommodated by the existing BAU teams.
293286988
Page 38 of 44
Iaas IaaS Deliverables (Investigate and Design Phase):

IBM Deliverable
Bi-directional connectivity
from IBM IaaS to EQC
network
Review Period
3 Day
Acceptance Method
Verification by
operational
demonstration
Draft Design Documents

delivered for review
5 Day
Verification by visual
inspection
Physical Hardware
configured for use
3 Day
inspection
Built
3 Day
SIT Environment Built
3 Day
UAT Environment Built
3 Day
Training Environment Built
3 Day
Pre-Prod Environment Built
3 Day
DR Environment Built
3 Day
Production Environment
Built
3 Day
Design Documents finalised
5 Day
Verification by
operational
demonstration
Verification by
operational
demonstration
Verification by
operational
demonstration
Verification by
operational
demonstration
Verification by
operational
demonstration
Verification by
operational
demonstration
Verification by
operational
demonstration
293286988
Acceptance Criteria
Connectivity established for
resources to gain access to
IaaS for provisioning of CMS
V8 Platform
Detailed designs, Network
Design and Security Design
completed to planed
implementation state and
submitted for review
Physical Hardware for
Oracle configured and
available for Oracle install
Environment deployed and
configured
Accepted by (EQC)
EQC Project
Manager

configured
EQC Project
Manager

configured
EQC Project
Manager

configured
EQC Project
Manager

configured
EQC Project
Manager

configured
EQC Project
Manager

configured
EQC Project
Manager
Design documents finalised
EQC Project
Required by
EQC Project
Manager
EQC Project
Manager
EQC Project
Manager
Page 39 of 44
IBM Deliverable
Review Period
Acceptance Method
inspection
BAU handover complete
3 Day
Verification by mutually
agreed criteria
Acceptance Criteria
to As built state and
submitted for final review
Accepted by (EQC)
Manager
Required by
EQC Project
Manager
Ref
Deliverable
Estimated
Date
Acceptance Criteria
DV04
Network Detailed Design
13/07/2015
IBM has delivered the report to EQC covering the contents listed in the Deliverable
description;
EQC have reviewed the report for completeness, comprehension and accuracy, and
any requested clarifications or revisions have been supplied; and
EQC have formally accepted the report in accordance with Appendix B-1 Deliverables
Acceptance Procedure.
description;
Acceptance Procedure
description;
description;
IBM has completed the implementation of CMS V8 environment; and
DV05
DV06
DV07
DV09
Infrastructure Solution
Design
System Solution Design
Security Detailed Design
CMS v8 on IaaS
293286988
13/07/2015
13/07/2015
13/07/2015
24/07/2015
Page 40 of 44
Ref
Deliverable
Estimated
Date
Development
Environment
DV10
DV11
CMS v8 on IaaS Systems

Integration Testing
Environment
24/07/2015
CMS v8 on IaaS User

Acceptance Testing
Environment
07/08/2015
Acceptance Criteria
IBM has notified the EQC Project Manager that the environment is available for project
activities.
activities.
activities.
Deliverable Descriptions:
Network Design
Purpose: This Design provides an over view of the overall network layout
Content: The Network Design will contain the following:
Connectivity from CMS V4 to CMS V8 WAN connectivity

Multi-tiered firewall configuration for segregation and security of application and data
Delivery: IBM will deliver one electronic copy of this document twice throughout the project. The first release will be an As Designed release and
provide to EQC for review at M09. The second release will be As Built and provide to EQC for review and final sign off at M15.
Infrastructure Design
Purpose: This Design will Server Provisioning
Content: The Infrastructure will contain the following:
Server resource allocation
293286988
Page 41 of 44
Server IP allocation
Server Base configuration including Operating system configuration
System Solution Design

Purpose: This will document a number of designs to cover System management, Server Operating System and Software Components that
make up the CMS V8 Stack
Content: The System Designs will contain the following:
System Management Backup/Restore, Monitoring, Antivirus DNS configuration

IBM Integration Bus Installation and configuration
ClaimCenter and Oracle - Installation and configuration
IBM Content Manager - Installation and configuration
Access and Authentication Installation and configuration
Delivery: IBM will deliver one electronic copies of each document twice throughout the project. The first release will be an As Designed release and
Security Design
Purpose: This Design will provide Firewall Configuration
Content: The Security Design will contain the following:
CMS V8 internal communication flows

CMS V4 to CMS V8 communication flows
Internal Routing
Configuration requirements for all Firewalls
External Connectivity into CMS V8 Platform for vendors and business partners.
293286988
Page 42 of 44
293286988
Page 43 of 44
Schedule: (this version to be updatedGantt chart is truncated to the right. Original MSP is available separately)
293286988
Page 44 of 44

Investigate and Design Phase Plan v1.3

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Investigate and Design Phase Plan v1.3

Caricato da

Copyright:

Formati disponibili

CMS Programme

Stream 2 ClaimCenter v8 on IaaS

Investigate and Design Phase Plan

PROJECT START UP ACTIVITIES.............................................................................................................11

Pre-Project Activities for ClaimCenter..............................................................................................11

Inception Phase Overview...............................................................................................................12

Roles During Inception Workshops................................................................................................14

High-Level Phase Plan.....................................................................................................................15

Detailed Phase Plan.........................................................................................................................17

Week 1 (11/05 15/05)...................................................................................................................17

Week 2 (18/05 23/05)..................................................................................................................18

Week 3 (25/05 29/05)..................................................................................................................19

Week 4 (01/06 05/06)..................................................................................................................21

Week 5 (08/06 12/06)..................................................................................................................22

Development Team Product Training No Further Training Required.............................................24

Typical Development Sprint Cycle....................................................................................................25

IAAS DESIGN AND BUILD.......................................................................................................................... 27

Updated after review with EQC and Guidewire

Released to EQC to support updated Approach

Updated with feedback on v1.0

Further review with RS/LC. Inclusion of additional IaaS plan detail.

Version to release with Approach v1.6

Table 1 Document Versioning

This document has been approved by the following people.

IBM Project Executive (GBS)

IBM Project Executive (GTS)

Table 2 Document Approvers

This document will be distributed to:

CMS Programme Manager, EQC

CMS Project Manager, EQC

Project Executive (GBS), IBM

Project Executive (GTS), IBM

Table 3 Document Distribution List

CMS Programme - Stream 2 _

Project Approach and Budgetary

Project Start up Activities

IBM Core Team

EQC IT (Paul Cooper)

Open need names to be provided to IT

3 PROJECT START UP ACTIVITIES

Pre-Project Activities for ClaimCenter

Meetings and Activities

Discuss Guidewire project methodology and this inception

Socialise the Agile delivery methodology

Inception team needs

Discuss Guidewire Software product training

Project team structure

Kick-off meeting preparation

Refine project planning, project management and

Objectives and Deliverables

Review project methodology

Agree use of Rally, as per joint EQC &

Set training expectations and establish a

Distribute and discuss the sample kick-off

Project documents in place to support

Inception Phase Overview

The key objectives of this phase include:

This phase should include participation by the following people:

Core team (full-time):

EQC and IBM project manager

Guidewire functional consultant

Extended team: core team plus following roles

IBM Infrastructure Architect