University Project: CRM System Implementation Project Plan
VerifiedAdded on 2021/06/18
|11
|1378
|57
Project
AI Summary
This project plan details the implementation of a CRM system for TOSIG, an insurance company. It outlines the project's scope, which includes system design, development, and deployment, alongside project management principles. The business case highlights the need for improved information processing to stay competitive. The project follows a six-step agile methodology, encompassing initialization, planning, designing, executing, testing, and closing phases. A milestone schedule with acceptance criteria is provided, covering various project aspects such as data incompatibility, system failure, and cost overruns. The plan also identifies key stakeholders, including the client, project manager, and project team members. The project charter document supports stakeholder information transfer and project alignment.

Running head: SYSTEM IMPLEMENTATION PROJECT PLAN
System Implementation Project Plan
Name of the Student:
Student ID:
Name of the University:
Author’s note:
System Implementation Project Plan
Name of the Student:
Student ID:
Name of the University:
Author’s note:
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

1SYSTEM IMPLEMENTATION PROJECT PLAN
Table of Contents
Introduction......................................................................................................................................2
1. Title..............................................................................................................................................2
2. Scope overview............................................................................................................................2
3. Business case...............................................................................................................................3
4. Project Background.....................................................................................................................3
5. Milestone schedule with acceptance criteria...............................................................................4
6. Risks, assumptions and constraints..............................................................................................6
7. Stakeholder list............................................................................................................................7
Conclusion.......................................................................................................................................7
Bibliography....................................................................................................................................9
Table of Contents
Introduction......................................................................................................................................2
1. Title..............................................................................................................................................2
2. Scope overview............................................................................................................................2
3. Business case...............................................................................................................................3
4. Project Background.....................................................................................................................3
5. Milestone schedule with acceptance criteria...............................................................................4
6. Risks, assumptions and constraints..............................................................................................6
7. Stakeholder list............................................................................................................................7
Conclusion.......................................................................................................................................7
Bibliography....................................................................................................................................9

2SYSTEM IMPLEMENTATION PROJECT PLAN
Introduction
The project charter is an initiation document for the project that is helpful for the
alignment of the initial transfer of the information to the stakeholders. The project charter
document would be helpful for the transfer of the information to the stakeholders and alignment
of the operations favouring the utilization of the project management principles. The charter
document is developed for the implication of the activities for forming the utilization of the
activities favouring the utilization of the operations succeeding the deployment of the operations.
The following assignment had been made on the project of Implementation of CRM system in
TOSIG.
1. Title
The title of the project is ‘Implementation of CRM system in TOSIG’.
2. Scope overview
The project of Implementation of CRM System in TOSIG is deployed for the
development of the management information for the organization. The project is deployed for the
implementation of the effective implication of the activities favouring the utilization of the
activities forming the implementation of the operations. The development of the CRM system
would be aligned for the implication of the effective deployment of the operations and forming
the customer data management. The deployment of the CRM system in TOSIG would be helpful
for forming the implication of the effective data management for TOSIG. The scope of the
project includes proper project initiation and closure documentation, design development for the
CRM system, development of the CRM system, and deployment of the system. The project
Introduction
The project charter is an initiation document for the project that is helpful for the
alignment of the initial transfer of the information to the stakeholders. The project charter
document would be helpful for the transfer of the information to the stakeholders and alignment
of the operations favouring the utilization of the project management principles. The charter
document is developed for the implication of the activities for forming the utilization of the
activities favouring the utilization of the operations succeeding the deployment of the operations.
The following assignment had been made on the project of Implementation of CRM system in
TOSIG.
1. Title
The title of the project is ‘Implementation of CRM system in TOSIG’.
2. Scope overview
The project of Implementation of CRM System in TOSIG is deployed for the
development of the management information for the organization. The project is deployed for the
implementation of the effective implication of the activities favouring the utilization of the
activities forming the implementation of the operations. The development of the CRM system
would be aligned for the implication of the effective deployment of the operations and forming
the customer data management. The deployment of the CRM system in TOSIG would be helpful
for forming the implication of the effective data management for TOSIG. The scope of the
project includes proper project initiation and closure documentation, design development for the
CRM system, development of the CRM system, and deployment of the system. The project
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

3SYSTEM IMPLEMENTATION PROJECT PLAN
would include the accumulation and analysis of various documents that would be favourable for
the development and implementation of the CRM system. The analysis would also result in
forming the improved utilization of the operations so that the activities might result in forming
the feasible design development for the CRM system. The utilization of the project management
principles and techniques is also in scope items of the project.
3. Business case
The organization of TOSIG is an insurance company that has been offering insurance to
the suppliers of One Suppliers. The business case analysis has provided an overview of the
activities forming the need of effective implication of the information processing. The analysis
would be helpful for realizing the extent of the business development. The development of the
project is based on the deployment of the effective information processing for the organization.
The implementation of the CRM system is required for ensuring that the effective management
of the activities can be achieved. The growth of the competition had made it necessary for using
the effective management of the operations and deployment of the vast information processing. It
would help the organization for achieving faster and more effective results for their processes.
4. Project Background
The CRM implementation has been developed using the 6 step agile development
methodology and it would comprise of initializing, planning, designing, executing, testing, and
closing. The use of the agile methodology had made it easy for the organization to utilize the
improved operation development. The initializing involves requirement analysis, initiation
documentation, charter documentation, submitting the documents, and kick off. The planning
involves outline of plan, review of the plan, complete plan, and plan approval. The designing
would include the accumulation and analysis of various documents that would be favourable for
the development and implementation of the CRM system. The analysis would also result in
forming the improved utilization of the operations so that the activities might result in forming
the feasible design development for the CRM system. The utilization of the project management
principles and techniques is also in scope items of the project.
3. Business case
The organization of TOSIG is an insurance company that has been offering insurance to
the suppliers of One Suppliers. The business case analysis has provided an overview of the
activities forming the need of effective implication of the information processing. The analysis
would be helpful for realizing the extent of the business development. The development of the
project is based on the deployment of the effective information processing for the organization.
The implementation of the CRM system is required for ensuring that the effective management
of the activities can be achieved. The growth of the competition had made it necessary for using
the effective management of the operations and deployment of the vast information processing. It
would help the organization for achieving faster and more effective results for their processes.
4. Project Background
The CRM implementation has been developed using the 6 step agile development
methodology and it would comprise of initializing, planning, designing, executing, testing, and
closing. The use of the agile methodology had made it easy for the organization to utilize the
improved operation development. The initializing involves requirement analysis, initiation
documentation, charter documentation, submitting the documents, and kick off. The planning
involves outline of plan, review of the plan, complete plan, and plan approval. The designing
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

4SYSTEM IMPLEMENTATION PROJECT PLAN
involves outline of design, design simulation, complete design is made, and design approval. The
executing involves database development, migration of data, functions are programmed, user
interface is developed, complete system is developed, and system is developed. The testing
involves black box testing, white box testing, prototyping, test results are documented, review of
test results, and test case completed. The closing involves development of final reports, training
of employees, submitting the reports, and project closed.
5. Milestone schedule with acceptance criteria
The timeline schedule for the project of Implementation of CRM System in TOSIG is
given below,
WBS Task Name Duration Start Finish
0 Implementation of CRM system in TOSIG 93 days Mon 5/21/18 Wed 9/26/18
1 Initializing 8 days Mon 5/21/18 Wed 5/30/18
1.1 Requirement Analysis 3 days Mon 5/21/18 Wed 5/23/18
1.2 Initiation Documentation 2 days Thu 5/24/18 Fri 5/25/18
1.3 Charter Documentation 2 days Mon 5/28/18 Tue 5/29/18
1.4 Submitting the documents 1 day Wed 5/30/18 Wed 5/30/18
M1 Kick off 0 days Wed 5/30/18 Wed 5/30/18
2 Planning 10 days Thu 5/31/18 Wed 6/13/18
2.1 Outline of plan 3 days Thu 5/31/18 Mon 6/4/18
2.2 Review of the plan 2 days Tue 6/5/18 Wed 6/6/18
2.3 Complete Plan 5 days Thu 6/7/18 Wed 6/13/18
M2 Plan Approval 0 days Wed 6/13/18 Wed 6/13/18
3 Designing 10 days Thu 6/14/18 Wed 6/27/18
involves outline of design, design simulation, complete design is made, and design approval. The
executing involves database development, migration of data, functions are programmed, user
interface is developed, complete system is developed, and system is developed. The testing
involves black box testing, white box testing, prototyping, test results are documented, review of
test results, and test case completed. The closing involves development of final reports, training
of employees, submitting the reports, and project closed.
5. Milestone schedule with acceptance criteria
The timeline schedule for the project of Implementation of CRM System in TOSIG is
given below,
WBS Task Name Duration Start Finish
0 Implementation of CRM system in TOSIG 93 days Mon 5/21/18 Wed 9/26/18
1 Initializing 8 days Mon 5/21/18 Wed 5/30/18
1.1 Requirement Analysis 3 days Mon 5/21/18 Wed 5/23/18
1.2 Initiation Documentation 2 days Thu 5/24/18 Fri 5/25/18
1.3 Charter Documentation 2 days Mon 5/28/18 Tue 5/29/18
1.4 Submitting the documents 1 day Wed 5/30/18 Wed 5/30/18
M1 Kick off 0 days Wed 5/30/18 Wed 5/30/18
2 Planning 10 days Thu 5/31/18 Wed 6/13/18
2.1 Outline of plan 3 days Thu 5/31/18 Mon 6/4/18
2.2 Review of the plan 2 days Tue 6/5/18 Wed 6/6/18
2.3 Complete Plan 5 days Thu 6/7/18 Wed 6/13/18
M2 Plan Approval 0 days Wed 6/13/18 Wed 6/13/18
3 Designing 10 days Thu 6/14/18 Wed 6/27/18

5SYSTEM IMPLEMENTATION PROJECT PLAN
3.1 Outline of design 3 days Thu 6/14/18 Mon 6/18/18
3.2 Design Simulation 2 days Tue 6/19/18 Wed 6/20/18
3.3 Complete Design is made 5 days Thu 6/21/18 Wed 6/27/18
M3 Design Approval 0 days Wed 6/27/18 Wed 6/27/18
4 Executing 40 days Thu 6/28/18 Wed 8/22/18
4.1 Database Development 8 days Thu 6/28/18 Mon 7/9/18
4.2 Migration of data 3 days Tue 7/10/18 Thu 7/12/18
4.3 Functions are programmed 10 days Fri 7/13/18 Thu 7/26/18
4.4 User Interface is developed 7 days Fri 7/27/18 Mon 8/6/18
4.5 Complete system is developed 12 days Tue 8/7/18 Wed 8/22/18
M4 System developed 0 days Wed 8/22/18 Wed 8/22/18
5 Testing 14 days Thu 8/23/18 Tue 9/11/18
5.1 Black box testing 3 days Thu 8/23/18 Mon 8/27/18
5.2 White box testing 3 days Tue 8/28/18 Thu 8/30/18
5.3 Prototyping 3 days Fri 8/31/18 Tue 9/4/18
5.4 Test results are documented 3 days Wed 9/5/18 Fri 9/7/18
5.5 Review of test results 2 days Mon 9/10/18 Tue 9/11/18
M5 Test case completed 0 days Tue 9/11/18 Tue 9/11/18
6 Closing 11 days Wed 9/12/18 Wed 9/26/18
6.1 Development of final reports 3 days Fri 9/21/18 Tue 9/25/18
6.2 Training of employees 7 days Wed 9/12/18 Thu 9/20/18
6.3 Submitting the reports 1 day Wed 9/26/18 Wed 9/26/18
M7 Project Closed 0 days Wed 9/26/18 Wed 9/26/18
Table 1: Project Schedule showing the milestones (denoted by M1....M7)
3.1 Outline of design 3 days Thu 6/14/18 Mon 6/18/18
3.2 Design Simulation 2 days Tue 6/19/18 Wed 6/20/18
3.3 Complete Design is made 5 days Thu 6/21/18 Wed 6/27/18
M3 Design Approval 0 days Wed 6/27/18 Wed 6/27/18
4 Executing 40 days Thu 6/28/18 Wed 8/22/18
4.1 Database Development 8 days Thu 6/28/18 Mon 7/9/18
4.2 Migration of data 3 days Tue 7/10/18 Thu 7/12/18
4.3 Functions are programmed 10 days Fri 7/13/18 Thu 7/26/18
4.4 User Interface is developed 7 days Fri 7/27/18 Mon 8/6/18
4.5 Complete system is developed 12 days Tue 8/7/18 Wed 8/22/18
M4 System developed 0 days Wed 8/22/18 Wed 8/22/18
5 Testing 14 days Thu 8/23/18 Tue 9/11/18
5.1 Black box testing 3 days Thu 8/23/18 Mon 8/27/18
5.2 White box testing 3 days Tue 8/28/18 Thu 8/30/18
5.3 Prototyping 3 days Fri 8/31/18 Tue 9/4/18
5.4 Test results are documented 3 days Wed 9/5/18 Fri 9/7/18
5.5 Review of test results 2 days Mon 9/10/18 Tue 9/11/18
M5 Test case completed 0 days Tue 9/11/18 Tue 9/11/18
6 Closing 11 days Wed 9/12/18 Wed 9/26/18
6.1 Development of final reports 3 days Fri 9/21/18 Tue 9/25/18
6.2 Training of employees 7 days Wed 9/12/18 Thu 9/20/18
6.3 Submitting the reports 1 day Wed 9/26/18 Wed 9/26/18
M7 Project Closed 0 days Wed 9/26/18 Wed 9/26/18
Table 1: Project Schedule showing the milestones (denoted by M1....M7)
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

6SYSTEM IMPLEMENTATION PROJECT PLAN
The 7 milestones of the project are kick off, plan approval, design approval, system
developed, test case completed, and project closed. The successful completion of these
milestones depends upon the following criteria,
a) All initial documents are being signed and approved by the project manager after
reviewing
b) Feasibility analysis of the plan have brought about positive results and hence the
manager have approved the project plan
c) Simulation of the design had shown that the design would be sustainable for the
development of the CRM system
d) Compatible system is developed resulting in integration of the operations of
TOSIG with the new CRM system
e) Expected test results have been achieved for developing the CRM with the
operations of TOSIG
f) All required documents have been signed and approved by the project manager
for closure of the project
6. Risks, assumptions and constraints
The project of Implementation of CRM System in TOSIG is and IT based project and
hence it would have to face several factors of risk related to technological implementation. The
various risks of the project are based on technology, operations, human, and finance. Some of the
probable risk factors that TOSIG might face for their project are design issues, data
The 7 milestones of the project are kick off, plan approval, design approval, system
developed, test case completed, and project closed. The successful completion of these
milestones depends upon the following criteria,
a) All initial documents are being signed and approved by the project manager after
reviewing
b) Feasibility analysis of the plan have brought about positive results and hence the
manager have approved the project plan
c) Simulation of the design had shown that the design would be sustainable for the
development of the CRM system
d) Compatible system is developed resulting in integration of the operations of
TOSIG with the new CRM system
e) Expected test results have been achieved for developing the CRM with the
operations of TOSIG
f) All required documents have been signed and approved by the project manager
for closure of the project
6. Risks, assumptions and constraints
The project of Implementation of CRM System in TOSIG is and IT based project and
hence it would have to face several factors of risk related to technological implementation. The
various risks of the project are based on technology, operations, human, and finance. Some of the
probable risk factors that TOSIG might face for their project are design issues, data
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

7SYSTEM IMPLEMENTATION PROJECT PLAN
incompatibility, system failure, cost overrun, delay in completion, and lack of skills. The
assumptions of the project are based on the availability of the resources, overall performance,
and project team work. The constraints of the project are time, budget, quality, and technological
dependence.
Risk Factors Assumptions Constraints
Data Incompatibility
System Failure
Cost Overrun
Delay in Completion
Lack of Skills
Expected availability of the
resources
Good overall performance
Excellent project team work
Time
Budget
Quality
Technological Dependence
7. Stakeholder list
Stakeholder
Classification
Stakeholders
Governance Client, Sponsor, Steering Committee, End User
Management Project Manager, Contractor
Operation Project Team comprising of Engineer, Software Developer, Designer,
Tester, Planner, Documenter, Budgeter, Analyst, Trainer, and Workers
Conclusion
It can be concluded that the use of the project management tools had helped in the
development of the project charter document. The document had provided the information
related to project scope, business case, project background, milestone schedule with acceptance
criteria, risks, assumptions and constraints, and stakeholder list. The project charter document
incompatibility, system failure, cost overrun, delay in completion, and lack of skills. The
assumptions of the project are based on the availability of the resources, overall performance,
and project team work. The constraints of the project are time, budget, quality, and technological
dependence.
Risk Factors Assumptions Constraints
Data Incompatibility
System Failure
Cost Overrun
Delay in Completion
Lack of Skills
Expected availability of the
resources
Good overall performance
Excellent project team work
Time
Budget
Quality
Technological Dependence
7. Stakeholder list
Stakeholder
Classification
Stakeholders
Governance Client, Sponsor, Steering Committee, End User
Management Project Manager, Contractor
Operation Project Team comprising of Engineer, Software Developer, Designer,
Tester, Planner, Documenter, Budgeter, Analyst, Trainer, and Workers
Conclusion
It can be concluded that the use of the project management tools had helped in the
development of the project charter document. The document had provided the information
related to project scope, business case, project background, milestone schedule with acceptance
criteria, risks, assumptions and constraints, and stakeholder list. The project charter document

8SYSTEM IMPLEMENTATION PROJECT PLAN
had been helpful for the transfer of the information to the stakeholders and alignment of the
operations favouring the utilization of the project management principles. The project of
Implementation of CRM system in TOSIG had been considered for the development of the
project charter document.
had been helpful for the transfer of the information to the stakeholders and alignment of the
operations favouring the utilization of the project management principles. The project of
Implementation of CRM system in TOSIG had been considered for the development of the
project charter document.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

9SYSTEM IMPLEMENTATION PROJECT PLAN
Bibliography
Brioso, X. 2015. Integrating ISO 21500 guidance on project management, lean construction and
PMBOK. Procedia Engineering, 123, 76-84.
Brooks, J., and King, N. 2014. Doing template analysis: evaluating an end of life care service.
Sage Research Methods Cases.
Coppola, D., D'Ambrogio, A., and Gianni, D. 2016. Bringing Model-based Systems Engineering
Capabilities to Project Management: an Application to PRINCE2. In CIISE (pp. 6-15).
Drouart, G., De Breuck, C., Vernet, J., Seymour, N., Lehnert, M., Barthel, P., ... and Hatch, N.
2014. Rapidly growing black holes and host galaxies in the distant Universe from the Herschel
Radio Galaxy Evolution Project. Astronomy & Astrophysics, 566, A53.
Jamali, G., and Oveisi, M. 2016. A Study on Project Management Based on PMBOK and
PRINCE2. Modern Applied Science, 10(6), 142.
Karaman, E., and Kurt, M. 2015. Comparison of project management methodologies: prince 2
versus PMBOK for it projects. Int. Journal of Applied Sciences and Engineering Research, 4(5),
657-664.
Kerzner, H., and Kerzner, H. R. 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Schwalbe, K. 2015. Information technology project management. Cengage Learning.
Snyder, C. S. 2014. A guide to the project management body of knowledge: PMBOK (®) guide.
Project Management Institute: Newtown Square, PA, USA.
Bibliography
Brioso, X. 2015. Integrating ISO 21500 guidance on project management, lean construction and
PMBOK. Procedia Engineering, 123, 76-84.
Brooks, J., and King, N. 2014. Doing template analysis: evaluating an end of life care service.
Sage Research Methods Cases.
Coppola, D., D'Ambrogio, A., and Gianni, D. 2016. Bringing Model-based Systems Engineering
Capabilities to Project Management: an Application to PRINCE2. In CIISE (pp. 6-15).
Drouart, G., De Breuck, C., Vernet, J., Seymour, N., Lehnert, M., Barthel, P., ... and Hatch, N.
2014. Rapidly growing black holes and host galaxies in the distant Universe from the Herschel
Radio Galaxy Evolution Project. Astronomy & Astrophysics, 566, A53.
Jamali, G., and Oveisi, M. 2016. A Study on Project Management Based on PMBOK and
PRINCE2. Modern Applied Science, 10(6), 142.
Karaman, E., and Kurt, M. 2015. Comparison of project management methodologies: prince 2
versus PMBOK for it projects. Int. Journal of Applied Sciences and Engineering Research, 4(5),
657-664.
Kerzner, H., and Kerzner, H. R. 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Schwalbe, K. 2015. Information technology project management. Cengage Learning.
Snyder, C. S. 2014. A guide to the project management body of knowledge: PMBOK (®) guide.
Project Management Institute: Newtown Square, PA, USA.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

10SYSTEM IMPLEMENTATION PROJECT PLAN
Snyder, C., and Dionisio, C. S. 2017. A project manager's book of forms: A companion to the
PMBOK guide. John Wiley & Sons.
Tomanek, M., and Juricek, J. 2015. Project risk management model based on PRINCE2 and
SCRUM frameworks. arXiv preprint arXiv:1502.03595.
Wong, C. R., Wang, A., Buechler, C., Flores, L., Dorri, M., Updegraff, M., ... and Olson, M.
2017. Civil Engineering Senior Design Capstone Project: Design Documentation for the
Widening of Broadway Boulevard.
Snyder, C., and Dionisio, C. S. 2017. A project manager's book of forms: A companion to the
PMBOK guide. John Wiley & Sons.
Tomanek, M., and Juricek, J. 2015. Project risk management model based on PRINCE2 and
SCRUM frameworks. arXiv preprint arXiv:1502.03595.
Wong, C. R., Wang, A., Buechler, C., Flores, L., Dorri, M., Updegraff, M., ... and Olson, M.
2017. Civil Engineering Senior Design Capstone Project: Design Documentation for the
Widening of Broadway Boulevard.
1 out of 11
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.