Request for Proposal (RFP) GCOM Project 2022
Added on 2022-09-15
27 Pages4194 Words31 Views
|
|
|
GCOM Project
19
Request for
Proposal (RFP)
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
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
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
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
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
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
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents