Gothaer Insurance Group GCOM Project 19: Request for Proposal (RFP)

This document is a Request for Proposal (RFP) for the GCOM Project 19, undertaken for Gothaer Insurance Group. The project aims to develop a digital policy system utilizing an agile SCRUM methodology to allow customers to create customized insurance contracts. The RFP outlines the project description, scope of services, and detailed timeline with associated constraints. It includes a comprehensive budget breakdown, resource and technology requirements, and evaluation criteria. The document also addresses potential risks and provides references. The project is divided into pre-planning, detailed planning, agile setup, agile sprints, and deployment/closure phases. The sprints involve the development of various contract types, including individual, group, and family contracts, as well as the policy and distribution systems. The project's success hinges on adhering to the specified timeline and budget, with a focus on delivering a robust and adaptable insurance policy system.

GCOM Project
19
Request for Proposal (RFP)

Request for Proposal (RFP)
Table of Contents
Introduction...........................................................................................................................................2
Background.......................................................................................................................................2
Purpose..............................................................................................................................................2
Project Description................................................................................................................................2
Scope of Services..................................................................................................................................3
Project Methodology.............................................................................................................................3
Timeline – Constraints..........................................................................................................................4
Budget Constraints..............................................................................................................................11
Resource Requirements.......................................................................................................................15
Technology Requirements...................................................................................................................23
Evaluation Criteria...............................................................................................................................24
Possible Risks......................................................................................................................................24
References...........................................................................................................................................25
1

Request for Proposal (RFP)
Introduction
Background
The project is being carried out for Gothaer Insurance Group and it includes the development
of a policy system that does not require an agent to process the insurance policies and
contracts for the customers. It will be a digital system that will allow the customers to create
customized contracts as per the requirements and the applicable rules (Gotz et al., 2018).
The organization has decided to adopt agile methodology as the preferred approach and the
SCRUM development process will be used for the project development. The organization
does not have the resources and skills for the agile processes and it will be cost-effective to
outsource the process rather than carrying out the in-house development.
Purpose
The document is the Request for Proposal (RFP) document that comprises of the resource and
technology requirements for the project as per the applicable time & cost constraints.
Project Description
The project includes the modelling of the insurance system for the GoSMART program that
will comprise of the tariffs and underwriting rules. The component that will be primarily
modelled is GCOM and it will include the policy system and distributed system for the
process. The user will be able to develop the customized contracts in accordance with the
rules and standards (Rajasekaran, 2015). The approval and review cycle will be integrated
and the exception handling processes will be created as well.
The basic structure of the product machine has been shown in the image below.
2

Request for Proposal (RFP)
GCOM Process (Gotz et al., 2018)
Scope of Services
The project team will carry out the processes and services as per the agile SCRUM
methodology. The team will not be essentially carrying out the user interface design and set-
up. The basic design will be developed to carry out the coding and algorithm writing
accordingly (Kalyani & Mehta, 2019).
The scope will include the requirement assessment as per the project information, setting up
of the environment, and execution of the sprints. These sprints will include the programming
activities for the development of the backend that will comprise of the tariffs and contract
rules and guidelines. The exception handling, approval, and review scenarios will be
accordingly developed (Ashbacher, 2010).
Project Methodology
The methodology that has been decided to be used for the project is agile SCRUM
methodology. The basic flow of the methodology has been shown in the figure below.
Agile SCRUM process
The methodology has been preferred over the Waterfall model as there will be numerous
changes that may appear during the integration of GCOM in the GoSMART program.
Waterfall follows a traditional approach wherein the incorporation of the changes may not be
3

Request for Proposal (RFP)
readily possible (Carvalho & Mello, 2011). The SCRUM methodology will allow the
development and project processes to be conducted in sprints. This will make sure that any of
the modifications and improvements are correctly implemented.
Timeline – Constraints
The resources carrying out the project will be required to adhere with the following schedule.
The pre-planning and detailed planning will be done by the internal team. The Business
Advisor, Data Scientist, and Joe Freya (Scrum Master) will be the internal resources that will
remain involved in the subsequent phases as well (Tkachenko & Sivokoz, 2017).
WBS Task Name Duration Start Finish Successors Predecessors
1 GCOM Project 342 days
Tue
04-12-
18
Wed
25-03-
20
1.1 Pre-Planning Processes 39 days
Tue
04-12-
18
Fri 25-
01-19
1.1.1 GoSMART Program -
Business Case Analysis 11 days
Tue
04-12-
18
Tue 18-
12-18 4,5,24
1.1.2
Determination of the role
of GCOM in GoSMART
project
7 days
Wed
19-12-
18
Thu 27-
12-18 8 3
1.1.3 Current status analysis 9 days
Wed
19-12-
18
Mon 31-
12-18 6 3
1.1.4
Evaluation of
methodologies -
Agile/Waterfall
11 days
Tue
01-01-
19
Tue 15-
01-19 7,8 5
1.1.5 Milestone 1: Project
methodology 0 days
Tue
15-01-
19
Tue 15-
01-19 6
1.1.6 Staffing Requirements 8 days Wed Fri 25- 9 4,6
4

Request for Proposal (RFP)
16-01-
19 01-19
1.1.7 Milestone 2: Staffing
Needs 0 days Fri 25-
01-19
Fri 25-
01-19 11 8
1.2 Detailed Planning Process 43 days
Mon
28-01-
19
Wed
27-03-
19
1.2.1 Analysis of project stages
- 1 and 2 12 days
Mon
28-01-
19
Tue 12-
02-19 12,14,15,16 9
1.2.2 Scope Statement 9 days
Wed
13-02-
19
Mon 25-
02-19 14,15,16 11
1.2.3 Project Estimates 9 days
Tue
26-02-
19
Fri 08-
03-19 17
1.2.3.1 Project schedule 9 days
Tue
26-02-
19
Fri 08-
03-19 17 11,12
1.2.3.2 Project budget 9 days
Tue
26-02-
19
Fri 08-
03-19 17 11,12
1.2.3.3 Project scope 9 days
Tue
26-02-
19
Fri 08-
03-19 11,12
1.2.4 Milestone 3: Project
Estimates 0 days Fri 08-
03-19
Fri 08-
03-19 18,19,20 13,14,15
1.2.5 Planning of Project
Areas 13 days
Mon
11-03-
19
Wed
27-03-
19
17
1.2.5.1 Risk Management &
Handling
6 days Mon
11-03-
Mon 18-
03-19
21 17
5

Request for Proposal (RFP)
19
1.2.5.2 Stakeholders and
Communications 7 days
Mon
11-03-
19
Tue 19-
03-19 21 17
1.2.5.3 Quality & Integration 6 days
Wed
20-03-
19
Wed 27-
03-19 22 19,20
1.2.6 Milestone 4: Project Plan 0 days
Wed
27-03-
19
Wed 27-
03-19 24 21
1.3 Agile Set-up 39 days
Thu
28-03-
19
Tue 21-
05-19
1.3.1
Determination of the
project requirements - Product
Backlog
13 days
Thu
28-03-
19
Mon 15-
04-19 25,26 22,3
1.3.2
Procurement of tools and
configurations - Workstation
Set-up
17 days
Tue
16-04-
19
Wed 08-
05-19 26 24
1.3.3 Development of meeting
and communication schedule 9 days
Thu
09-05-
19
Tue 21-
05-19 27 24,25
1.3.4 Milestone 5: Agile Set-up 0 days
Tue
21-05-
19
Tue 21-
05-19 30 26
1.4 Agile Sprints 167 days
Wed
22-05-
19
Thu 09-
01-20
1.4.1 Sprint 1 16 days
Wed
22-05-
19
Wed
12-06-
19
1.4.1.1 Product Machine - Basic
Design
5 days Wed
22-05-
Tue 28- 31 27
6

Request for Proposal (RFP)
19 05-19
1.4.1.2 Development of Rules 7 days
Wed
29-05-
19
Thu 06-
06-19 32 30
1.4.1.3 Test & Review 4 days Fri 07-
06-19
Wed 12-
06-19 33,35 31
1.4.1.4 Milestone 6: Basic
Design 0 days
Wed
12-06-
19
Wed 12-
06-19 36 32
1.4.2 Sprint 2 19 days
Thu
13-06-
19
Tue 09-
07-19
1.4.2.1 Refinements in Design 4 days
Thu
13-06-
19
Tue 18-
06-19 32
1.4.2.2 Insurance Contracts -
Individual 16 days
Thu
13-06-
19
Thu 04-
07-19 37 33
1.4.2.3 Test & Review 3 days Fri 05-
07-19
Tue 09-
07-19 38 36
1.4.2.4 Milestone 7: Individual
Contracts 0 days
Tue
09-07-
19
Tue 09-
07-19 40 37
1.4.3 Sprint 3 23 days
Wed
10-07-
19
Fri 09-
08-19
1.4.3.1 Refinements in
Individual Contracts 4 days
Wed
10-07-
19
Mon 15-
07-19 41 38
1.4.3.2 Insurance Contracts -
Groups & Family 16 days
Tue
16-07-
19
Tue 06-
08-19 42 40
1.4.3.3 Test & Review 3 days Wed Fri 09- 43 41
7

Request for Proposal (RFP)
07-08-
19 08-19
1.4.3.4 Milestone 8:
Group/Family Contracts 0 days Fri 09-
08-19
Fri 09-
08-19 45 42
1.4.4 Sprint 4 21 days
Mon
12-08-
19
Mon
09-09-
19
1.4.4.1 Modifications &
Changes 4 days
Mon
12-08-
19
Thu 15-
08-19 46 43
1.4.4.2 Policy System - Filters
& Algorithms 14 days Fri 16-
08-19
Wed 04-
09-19 47 45
1.4.4.3 Test & Review 3 days
Thu
05-09-
19
Mon 09-
09-19 48,50 46
1.4.4.4 Milestone 9: Policy
System 0 days
Mon
09-09-
19
Mon 09-
09-19 47
1.4.5 Sprint 5 21 days
Tue
10-09-
19
Tue 08-
10-19
1.4.5.1 Modifications &
Changes 4 days
Tue
10-09-
19
Fri 13-
09-19 51 47
1.4.5.2 Distribution System -
Filters & Algorithms 14 days
Mon
16-09-
19
Thu 03-
10-19 52 50
1.4.5.3 Test & Review 3 days Fri 04-
10-19
Tue 08-
10-19 53 51
1.4.5.4 Milestone 10:
Distribution System 0 days
Tue
08-10-
19
Tue 08-
10-19 55 52
8

Request for Proposal (RFP)
1.4.6 Sprint 6 26 days
Wed
09-10-
19
Wed
13-11-
19
1.4.6.1 Modifications &
Changes 5 days
Wed
09-10-
19
Tue 15-
10-19 56 53
1.4.6.2 Customized Contracts 8 days
Wed
16-10-
19
Fri 25-
10-19 57 55
1.4.6.3 Contract Review &
Approval Cycle 10 days
Mon
28-10-
19
Fri 08-
11-19 58 56
1.4.6.4 Test & Review 3 days
Mon
11-11-
19
Wed 13-
11-19 59 57
1.4.6.5 Milestone 11: Review &
Approval Cycle 0 days
Wed
13-11-
19
Wed 13-
11-19 61 58
1.4.7 Sprint 7 22 days
Thu
14-11-
19
Fri 13-
12-19
1.4.7.1 Modifications &
Changes 3 days
Thu
14-11-
19
Mon 18-
11-19 62 59
1.4.7.2 Exception Handling
Rules - Contract Building 8 days
Tue
19-11-
19
Thu 28-
11-19 63 61
1.4.7.3 Exception Handling
Rules - Tariffs 8 days Fri 29-
11-19
Tue 10-
12-19 64 62
1.4.7.4 Test & Review 3 days
Wed
11-12-
19
Fri 13-
12-19 65 63
1.4.7.5 Milestone 12: Rules 0 days Fri 13- Fri 13- 67 64
9

Request for Proposal (RFP)
12-19 12-19
1.4.8 Sprint 8 19 days
Mon
16-12-
19
Thu 09-
01-20
1.4.8.1 Integration of the rules
and back-end processes 11 days
Mon
16-12-
19
Mon 30-
12-19 68 65
1.4.8.2 Final verifications &
Validations 8 days
Tue
31-12-
19
Thu 09-
01-20 69 67
1.4.8.3 Milestone 13: Integrated
product machine 0 days
Thu
09-01-
20
Thu 09-
01-20 71 68
1.5 Deployment & Closure 54 days Fri 10-
01-20
Wed
25-03-
20
1.5.1 Deployment with Alpha &
Beta Systems 21 days Fri 10-
01-20
Fri 07-
02-20 72 69
1.5.2 Reflection & Performance
measurement 12 days
Mon
10-02-
20
Tue 25-
02-20 73 71
1.5.3 Closure documentation 21 days
Wed
26-02-
20
Wed 25-
03-20 74 72
1.5.4 Milestone 14: Project
Closure 0 days
Wed
25-03-
20
Wed 25-
03-20 73
Budget Constraints
It will be required that the strict budget constraints are followed throughout the project. The
estimation of these costs has been done keeping the probable changes in the GCOM
integration and the associated risks in to consideration (Sharma & Bali, 2018).
10

Request for Proposal (RFP)
WBS Task Name Duration Start Finish Cost
11