System Implementation Project Plan Assignment

Verified

Added on  2021/06/17

|12
|2229
|44
AI Summary

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
Running head: SYSTEM IMPLEMENTATION PROJECT PLAN
System Implementation Project Plan
Name of the Student:
Student ID:
Name of the University:
Author’s note:

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
1SYSTEM IMPLEMENTATION PROJECT PLAN
Table of Contents
Introduction......................................................................................................................................2
1. Title..............................................................................................................................................2
2. Scope overview............................................................................................................................2
3. Business case...............................................................................................................................2
4. Project Background.....................................................................................................................3
5. Milestone schedule with acceptance criteria...............................................................................3
6. Risks, assumptions and constraints..............................................................................................6
7. Stakeholder list............................................................................................................................7
Conclusion.......................................................................................................................................8
Bibliography..................................................................................................................................10
Document Page
2SYSTEM IMPLEMENTATION PROJECT PLAN
Introduction
The project charter is an important document that comprise of the various information
like scope overview, business case, background, milestone schedule with acceptance criteria,
risks, assumptions, and constraints. The following project charter is made on the project of
Customer Information System Development for TOSIG. It would help in achieving the final
project deliverable by using the implication of the project management principles and activities.
1. Title
The title of the project is ‘Customer Information System Development for TOSIG.
2. Scope overview
The project in scopes the development of the initiation documents, designing of the
system, planning for the implementation, developing the system, testing the system, and final
closure of the project for the Tier One Suppliers Insurance Group so that they can implement the
customer information system for their operations.
3. Business case
The organization of Tier One Suppliers Insurance Group (TOSIG) requires the
implication of the effective alignment of the activities favouring the utilization of the improved
operation development. The successive alignment of the operations in TOSIG has resulted in
developing the needs of implementing the effective alignment of the activities. The need of the
customer information system for the organization had been resulted due to the implication of the
technology based operation.
Document Page
3SYSTEM IMPLEMENTATION PROJECT PLAN
4. Project Background
The Customer Information System Development for TOSIG project follows the iterative
agile methodology and it has 6 phases namely initial phase, plan phase, design phase, execution
phase, test phase, and closing phase. The completion of these phases would result in forming the
final project deliverable of the customer information system. The 1st phase of the project is initial
phase comprising of the activities of analysis of the requirements, project initiation document is
made, project charter document is made, documents are submitted, and project kick off. The 2nd
phase of the project is plan phase comprising of the activities of plan outline is developed, plan
outline is reviewed, complete plan is made, and plan is approved. The 3rd phase of the project is
design phase comprising of the activities of design outline is made, design outline is reviewed,
complete design is made, and design is approved. The 4th phase of the project is execution phase
comprising of the activities of database for system is developed, data is migrated, development
of UI, programming the functions, development of complete system, and system development is
completed. The 5th phase of the project is test phase comprising of the activities of alpha testing,
beta testing, function testing, documenting the test results, analysis of the test results, and test
phase is completed. The 6th and final phase of the project is closing phase comprising of the
activities of training of the employees, final reports are made, final reports are submitted, sign
off, and project is closed.
5. Milestone schedule with acceptance criteria
The following is the time schedule with the milestones of the project of Customer
Information System Development for TOSIG,
WBS Task Name Duration Start Finish

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4SYSTEM IMPLEMENTATION PROJECT PLAN
0 Customer Information System Development for
TOSIG 82 days Mon
6/11/18 Tue 10/2/18
1 Initial Phase 12 days Mon
6/11/18 Tue 6/26/18
1.1 Analysis of the requirements 4 days Mon
6/11/18 Thu 6/14/18
1.2 Project Initiation Document is made 3 days Fri 6/15/18 Tue 6/19/18
1.3 Project Charter Document is made 3 days Wed
6/20/18 Fri 6/22/18
1.4 Documents are submitted 2 days Mon
6/25/18 Tue 6/26/18
M1 Project Kick off 0 days Tue 6/26/18 Tue 6/26/18
2 Plan Phase 13 days Wed
6/27/18 Fri 7/13/18
2.1 Plan outline is developed 4 days Wed
6/27/18 Mon 7/2/18
2.2 Plan outline is reviewed 3 days Tue 7/3/18 Thu 7/5/18
2.3 Complete Plan is made 6 days Fri 7/6/18 Fri 7/13/18
M2 Plan is approved 0 days Fri 7/13/18 Fri 7/13/18
3 Design Phase 13 days Mon
7/16/18 Wed 8/1/18
3.1 Design Outline is made 4 days Mon
7/16/18 Thu 7/19/18
3.2 Design Outline is reviewed 3 days Fri 7/20/18 Tue 7/24/18
3.3 Complete Design is made 6 days Wed
7/25/18 Wed 8/1/18
M3 Design is approved 0 days Wed 8/1/18 Wed 8/1/18
4 Execution Phase 29 days Thu 8/2/18 Tue 9/11/18
4.1 Database for system is developed 7 days Thu 8/2/18 Fri 8/10/18
Document Page
5SYSTEM IMPLEMENTATION PROJECT PLAN
4.2 Data is Migrated 2 days Mon
8/13/18 Tue 8/14/18
4.3 Development of UI 6 days Thu 8/2/18 Thu 8/9/18
4.4 Programming the functions 9 days Wed
8/15/18
Mon
8/27/18
4.5 Development of Complete System 11 days Tue 8/28/18 Tue 9/11/18
M4 System Development is completed 0 days Tue 9/11/18 Tue 9/11/18
5 Test Phase 10 days Wed
9/12/18 Tue 9/25/18
5.1 Alpha Testing 2 days Wed
9/12/18 Thu 9/13/18
5.2 Beta Testing 2 days Fri 9/14/18 Mon
9/17/18
5.3 Function Testing 2 days Tue 9/18/18 Wed
9/19/18
5.4 Documenting the test results 2 days Thu 9/20/18 Fri 9/21/18
5.5 Analysis of the test results 2 days Mon
9/24/18 Tue 9/25/18
M5 Test Phase is completed 0 days Tue 9/25/18 Tue 9/25/18
6 Closing Phase 5 days Wed
9/26/18 Tue 10/2/18
6.1 Training of the Employees 5 days Wed
9/26/18 Tue 10/2/18
6.2 Final reports are made 2 days Wed
9/26/18 Thu 9/27/18
6.3 Final reports are submitted 1 day Fri 9/28/18 Fri 9/28/18
6.4 Sign off 1 day Fri 9/28/18 Fri 9/28/18
M6 Project is Closed 0 days Fri 9/28/18 Fri 9/28/18
Table 1: Project Schedule with highlighted milestones
Document Page
6SYSTEM IMPLEMENTATION PROJECT PLAN
The six phase of the project namely initial phase, plan phase, design phase, execution
phase, test phase, and closing phase has six milestones of project kick off, plan is approved,
design is approved, system development is completed, test phase is completed, and project is
closed respectively. The achievement of these milestones would require attenuation of some
criteria of,
a. Complete documentation of the initial documents and signed off the project
manager for approval
b. Approval of the project plan from the project manager by the help of feasibility
study
c. Achievement of the sustainable design as tested by the help of simulation test
results done in the project
d. System developed would be compatible for the operations that are being done in
TOSIG organization
e. Test results have shown that the customer information system would be integrated
successfully for the organization
f. Sign off the developed final reports that would help in shaping future projects and
activities for the organization
6. Risks, assumptions and constraints
The project risks are the factors that have direct impact on the operations of the Customer
Information System Development for TOSIG project and it would hinder the implication of the

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7SYSTEM IMPLEMENTATION PROJECT PLAN
successive development and alignment. The various risks of the project have been shown in the
following table,
Risk Classification
Loss of data Technical
Failure of the system Technical
Exhaustion of the resources Financial
Time delay of operations Operational
Conflict among project team Human
The assumptions of the project of Customer Information System Development for
TOSIG are given below,
a. All resources required for the project would be enough for the completion of the
project
b. The project has a feasible plan and it would be completed in that estimated budget
and expected schedule duration
c. Human resources included in the project would work together and complete the
effective activities required for the achievement of the final project deliverable
The constraints of the project of Customer Information System Development for TOSIG
are time, resources, system development knowledge, and operational capability of the system
developed with the operations of the TOSIG.
7. Stakeholder list
Document Page
8SYSTEM IMPLEMENTATION PROJECT PLAN
The project of Customer Information System Development for TOSIG is an IT project
and the stakeholders of the project can be divided into three classifications of governance,
managerial, and operational. The list of the stakeholders are given below,
Classification Stakeholders Function
Governance Sponsor, Client, Steering
Committee,
In charge of the decision making in the
project
Managerial Project Manager and Contractor Manage all the activities and ensure that
the final deliverable is achieved
Operational Complete project team, suppliers,
and some external workers
Work all the activities and tasks that are
required for the completion of the project
Conclusion
It can be concluded that the proper project charter document for the project of Customer
Information System Development for TOSIG had been helpful for the conveyance of the
information and the alignment of the effective documentation process. The project charter
document comprised of the following information,
a. Scope Overview
b. Business Case
c. Background
d. Milestone Schedule with acceptance Criteria
e. Risk Assumptions and Constraints
f. Stakeholder List
Document Page
9SYSTEM IMPLEMENTATION PROJECT PLAN
This information had been helpful for the development of the final project deliverable
and the alignment of the activities that had been favourable for the achievement of the effective
project plan development.

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10SYSTEM IMPLEMENTATION PROJECT PLAN
Bibliography
Binder, J. 2016. Global project management: communication, collaboration and management
across borders. Routledge.
Brooks, J., and King, N. 2014. Doing template analysis: evaluating an end of life care service.
Sage Research Methods Cases.
Cascante, I. L., Martin, F. M., Zubizarreta, J. P. O., and Aranburu, M. S. 2016, June. Three
Historic Stages in the Graphic Confection of Project Documentation. BIM: Meetings in the Third
Phase of the XXI Century. In Congreso Internacional de Expresión Gráfica Arquitectónica (pp.
1089-1097). Springer, Cham.
Chaves, M. S., Araújo, C. D., Teixeira, L., Rosa, D., Júnior, I., and Nogueira, C. 2016. A new
approach to managing Lessons Learned in PMBoK process groups: the Ballistic 2.0 Model.
International Journal of Information Systems and Project Management, 4(1), 27-45.
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).
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.
Lientz, B., and Rea, K. 2016. Breakthrough technology project management. Routledge.
Document Page
11SYSTEM IMPLEMENTATION PROJECT PLAN
Rybka, I., Bondar-Nowakowska, E., and Połoński, M. 2015. Management of Alterations to
Project Documentation–a Case Study of Water Supply and Sewerage Works. International
Journal of Contemporary Management, 2015Numer 14 ((3)), 41-57.
Schwalbe, K. 2015. Information technology project management. Cengage Learning.
Snyder, C., and Dionisio, C. S. 2017. A project manager's book of forms: A companion to the
PMBOK guide. John Wiley & Sons.
Spikol, D., Ehrenberg, N., Cuartielles, D., and Zbick, J. 2015. Design Strategies for developing a
Visual Platform for Physical Computing with Mobile Tools for Project Documentation and
Reflection.
1 out of 12
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]