Documente Academic
Documente Profesional
Documente Cultură
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
INCEPTION PHASE.................................................................................................................................... 12
4.1
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
4.2
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
SPRINT 0.................................................................................................................................................... 23
5.1
Objectives........................................................................................................................................23
5.2
Staffing.............................................................................................................................................23
5.3
Sprint Preparation............................................................................................................................23
5.4
5.5
Sprint 0 Plan.....................................................................................................................................24
DEVELOPMENT SPRINTS......................................................................................................................... 25
6.1
293286988
Private and Confidential
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
V0.4, 0.5
101/04/201
5
v1.0
10/04/2015
v1.1
16/04/2015
v1.2
17/04/2015
v1.2.1
17/04/2015
v1.3
17/04/2015
Updated following walk-through with RS, LC. Inception planning, Roles &
Deliverables
1.3
Approvals
293286988
Private and Confidential
Page 4 of 44
Name
Role on Project
Date of
Signature
Approval
Paul Turnbull
Jason Barlow
1.3.1
Distribution
Role on Project
John Callcut
Linda Smith
CIO, EQC
Ros Smith
Paul Turnbull
Jason Barlow
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
Versio
Date
Issued
1.5
10/04/2015
Document Author
Comments
IBM
293286988
Private and Confidential
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
Private and Confidential
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
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
Private and Confidential
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
Private and Confidential
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
Private and Confidential
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
EQC and IBM Project Managers + Guidewire
IBM Project Manager
Status
CompletedOpen
Completed
Planned for week 0 (commencing 4 May 2015)
In IBM Project Approach
Open
In progress
In progress
Completed
Available
Completed
Completed
Page 9 of 44
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
Already completed
Needs to be covered
earlierScheduled for
Week 0
Needs to be iIncluded
in Proposal
TBD
Update in Wweek 0
293286988
Private and Confidential
Staffing plan
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
Private and Confidential
Page 11 of 44
4 INCEPTION PHASE
4.1
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
Staffing
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.
EQC ScrumMaster
293286988
Private and Confidential
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
Ros Smith
TBC
Julie Robertson
Jayne Lapin
Ba Truong
Alex Zak
External Parties
EQC BIU Team
EQC Finance System
EQC ITechnical Specialists Ops (e.g. Network)
293286988
Private and Confidential
TBC
TBC
Jayne Lapin
Dave Timmins + TBC
Harry SiemerTBC
TBC
Paul Eades
TBC
TBC
Jesse (Boost)
Paul Eades
Raj Bhandaru
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
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
The table below describes the overall schedule for the project inception phase. A detailed schedule is provided in the following section.
Week 1
293286988
Private and Confidential
Page 15 of 44
Week 2
Week 3
Week 4
293286988
Private and Confidential
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
Private and Confidential
Page 17 of 44
4.3
4.3.1
Monday
Kick-off meeting
Guidewire Training
Tuesday
Estimation / Sizing
Approach
Arrange logistics
Confirm sandbox
environment
293286988
Private and Confidential
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
Page 18 of 44
Description or Topics
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)
Functional team
overview (how to
document and configure
changes to Guidewire
applicationEQC led)
Wed (morning)
Business process
overview meeting (EQC
led)
Wed (afternoon)
/ Thursday
Business process
meetings to confirm high-
Wednesday
293286988
Private and Confidential
Participants
EQC staff
EQC IT
EQC Product Owner
EQC Subject Matter Experts
Guidewire Functional Consultant
Rally Tool owner
EQC BA
Core Team
Page 19 of 44
Thursday
Description or Topics
Identification of core OOTB ClaimCenter functionality
not in EQC scope (i.e. Areas to remove / disable)
Participants
Infrastructure meeting
Friday
Review and
documentation
Friday
Core Team
4.3.2
Monday
Tuesday
(configuration
track)
293286988
Private and Confidential
Description or Topics
Lines of business in scope
Jurisdictions
High-level process flows
Coverages and mapping to exposure types
Participants
Project Team members
involved in business analysis,
design and discovery
Page 20 of 44
Friday
Integration meetings to
confirm high-level integration
requirements and data flows
Monday
Description or Topics
LOB-specific screens
Claim (Loss Details, Exposure, Incident, etc.)
New Claim Wizard
LOB-specific rules
Workplan
Pre-update
Validation
Tuesday
Wed / Thurs
293286988
Private and Confidential
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
Thursday
(morning)
Friday
4.3.3
Description or Topics
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
IBM Infrastructure Architect
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
Mon ThursWednesday
293286988
Private and Confidential
Description or Topics
Financial screens
Participants
Page 22 of 44
Monday
Wednesday
GIS Capabilities
Content Management
Tues ThursMondayThursday
(integration track)
Integration meetings
(continued)
Infrastructure meeting
293286988
Private and Confidential
Description or Topics
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
Core Team
Content Manager Developer
(remote)
Project Team members involved in
integration, conversion, or legacy
system modification
Page 23 of 44
Friday
Description or Topics
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)
4.3.4
Participants
Infrastructure Architect, Guidewire
technical consultant
Monday
Tuesday
Thursday
Monday-Friday
Sprint Planning
Business process
meetings (continued)
Final requirements
293286988
Private and Confidential
Description or Topics
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
Friday
4.3.5
Description or Topics
Risk Analysis
Gap Assessment
Participants
Core team
Core team
Guidewire project manager, EQC
Pproject Mmanager
IBM Project Manager
Guidewire project manager,
customer EQC 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
IBM Development & Test Teams
EQC Business Analysts
Monday
Monday-Friday
Tues - Thurs
293286988
Private and Confidential
Description or Topics
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
Core Team
Core team
Core team
Guidewire project manager,
customer EQC project manager
Guidewire project manager,
customer EQC project manager
Guidewire project manager,
Page 25 of 44
Description or Topics
Thurs
Friday
Sprint 0 Readiness
293286988
Private and Confidential
Participants
customer EQC project manager
Guidewire project manager, EQC
Project Manager
+ IBM Pproject Mmanager, Scrum
master
Page 26 of 44
5.1
Objectives
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
Private and Confidential
Page 27 of 44
5.3
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
Has been completed prior to the Inception phase for the core
Foundation
Configuration
Integration
and Stories
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
Private and Confidential
Page 28 of 44
5.4
Key Deliverables
5.5
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
Attendance
Business Analysts
Configuration resources
Integration resources
Configuration resources
Integration resources
Configuration resources
Integration resources
Any further training for new IBM resources will be arranged and managed by the IBM team.
5.7
Week 61/2
(Start Mon 15/06)
293286988
Private and Confidential
Page 29 of 44
Week 72/2
(End Tues 23/06)
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
Private and Confidential
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
Week 1 of 2
Week 2 of 2
Sprint Review
(Tues morning of second
week)
Sprint Retrospective
(Tues morning of second
week)
293286988
Private and Confidential
Description or Topics
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
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 Business Analysts
All Testers
Guidewire Consultants
Solution Architects
SMEs (if required)
ScrumMaster (lead)
Product Owner
All Developers
All Business Analysts
All Testers
Guidewire Functional Consultant
Guidewire Technical Consultant
IBM Solution Architect
Page 31 of 44
Week 2 of 2
Daily Activities
Description or Topics
Backlog Refinement
Meeting
Test Planning
Test Execution
Issue and Defect Identification and Reporting
Sprint Execution
Deployment
Testing
293286988
Private and Confidential
Participants
EQC Solution Architect
ScrumMaster (lead)
Product Owner
All Developers
All Business Analysts
All Testers
Guidewire Consultants
Solution Architects
SMEs (if required)
ScrumMaster (lead)
Product Owner
ScrumMaster (lead)
Product Owner
All Developers
All Business Analysts
All Testers
Guidewire Consultants
Solution Architects
SMEs (if required)
All Developers
All Business Analysts
Product Owner
Page 32 of 44
Description or Topics
Rally Administration
Participants
293286988
Private and Confidential
Page 33 of 44
Meetings and
Activities
Create connectivity to
IBM Government IaaS
service offering
Description or Topics
Outputs
Participants
Week 1 - 8
Create Detailed
Designs based on
current Solution
Architecture
documentation
Week
Implementation based
on Detailed Designs
293286988
Private and Confidential
Page 34 of 44
Week
Meetings and
Activities
Description or Topics
Week
Week 1
Week 2
Week 3
Participants
Connectivity testing
Application testing
Finalise Detailed Design documents
Handover
Meetings and
Activities
Resource allocation
Description or Topics
Outputs
Participants
None
Project resources
engaged
None
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
Private and Confidential
Page 35 of 44
Week
Meetings and
Activities
Resource allocation
Description or Topics
Outputs
Participants
None
Week 5
WAN access
implemented
WAN connectivity
established
Week 6
Interim environments
available for GBS/EQC
application development
Development Environment
available for EQC/GTS
application development
Week 1
Interim Environment
build completes
Week 7
Week 8
Week 9
Oracle infrastructure
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
Private and Confidential
Week
Week 1
Week
Week 1
Week 2
Week 3
Meetings and
Activities
Resource allocation
Outputs
Participants
None
Meetings and
Activities
Resource allocation
Description or Topics
Outputs
None
Document network
connectivity to IaaS
over and above POC
requirements
Project resources
engaged
None
IBM Architect
IBM Security Operations
Manager
IBM Technical SMEs
WAN connectivity
documentation completed
Week 4
Description or Topics
Oracle infrastructure
configuration Starts
Security and Network
Designs for EQC to
IaaS for WAN
connectivity completed
Week 5
Wan access
implemented
WAN connectivity
established
Week 6
Interim environments
293286988
Private and Confidential
Page 37 of 44
Week
Week 1
Meetings and
Activities
Resource allocation
Description or Topics
Outputs
Participants
None
documents
Completion and availability of Interim
environments
Development Environment
available for EQC/GTS
application development
Final Approvals
Interim Environment
build completes
Week 7
Week 8
Week 9
Oracle infrastructure
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
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
Private and Confidential
Page 38 of 44
Review Period
3 Day
Acceptance Method
Verification by
operational
demonstration
5 Day
Verification by visual
inspection
Physical Hardware
configured for use
3 Day
Verification by visual
inspection
Development Environment
Built
3 Day
3 Day
3 Day
3 Day
3 Day
DR Environment Built
3 Day
Production Environment
Built
3 Day
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
Verification by visual
293286988
Private and Confidential
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
EQC Project
Manager
EQC Project
Manager
EQC Project
Manager
EQC Project
Manager
EQC Project
Manager
EQC Project
Manager
EQC Project
Required by
EQC Project
Manager
EQC Project
Manager
EQC Project
Manager
Page 39 of 44
IBM Deliverable
Review Period
Acceptance Method
inspection
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
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.
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
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
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
DV05
DV06
DV07
DV09
Infrastructure Solution
Design
CMS v8 on IaaS
293286988
Private and Confidential
13/07/2015
13/07/2015
13/07/2015
24/07/2015
Page 40 of 44
Ref
Deliverable
Estimated
Date
Development
Environment
DV10
DV11
24/07/2015
07/08/2015
Acceptance Criteria
IBM has notified the EQC Project Manager that the environment is available for project
activities.
IBM has notified the EQC Project Manager that the environment is available for project
activities.
IBM has notified the EQC Project Manager that the environment is available for project
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:
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:
293286988
Private and Confidential
Page 41 of 44
Server IP allocation
Server Base configuration including Operating system configuration
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.
Delivery: IBM will deliver one electronic copies of each 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.
Security Design
Purpose: This Design will provide Firewall Configuration
Content: The Security Design will contain the following:
293286988
Private and Confidential
Page 42 of 44
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.
293286988
Private and Confidential
Page 43 of 44
Schedule: (this version to be updatedGantt chart is truncated to the right. Original MSP is available separately)
293286988
Private and Confidential
Page 44 of 44