Project Plan Document: IT Integration (base) - University Project

This project plan document outlines an IT integration project, detailing the business case, project scope, and objectives. It includes key performance indicators (KPIs) for project delivery, a comprehensive risk analysis identifying and categorizing potential risks, and a risk management plan. Th...Read More

Running head: PROJECT PLAN DOCUMENT
Project Plan Document
“IT Integration (base)”
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1PROJECT PLAN DOCUMENT
Table of Contents
1. Introduction..................................................................................................................................3
2. Business Case..............................................................................................................................3
3. Project Scope, Objectives............................................................................................................3
4. KPI – Project Delivery.................................................................................................................5
5. Risk Analysis...............................................................................................................................5
5.1 Risk identification..................................................................................................................5
5.2 Risk categorization and analysis............................................................................................7
5.3 Risk management and mitigation plan..................................................................................8
6. Resource Plan..............................................................................................................................9
7. Estimation Plan............................................................................................................................9
8. Communication Plan.................................................................................................................10
9. Project Schedule........................................................................................................................10
9.1 Task List..............................................................................................................................10
9.2 Summary tasks.....................................................................................................................11
9.3 WBS.....................................................................................................................................11
9.4 Predecessor linking..............................................................................................................11
9.5 Resource allocation..............................................................................................................12
9.6 Gantt Chart...........................................................................................................................13
9.7 Network analysis diagrams..................................................................................................13

2PROJECT PLAN DOCUMENT
10. Monitoring and controlling strategy........................................................................................14
10.1 Mile Stone..........................................................................................................................14
10.2 Base line.............................................................................................................................14
10.3 Critical Path,......................................................................................................................15
10.4 Float/Slack.........................................................................................................................15
11. Reflection & Conclusion.........................................................................................................16
Bibliography..................................................................................................................................17

3PROJECT PLAN DOCUMENT
1. Introduction
The project management holds an integral role for forming the implication management
and aligning the utilization management. The completion of the works would be aligned with the
management activity and management of the successive work completion. The integration has
been managed with the consideration of the factors and managing the implication development.
The following assignment would be implied with the integration of the improved work
development. The business case analysis would be developed for listing the analysis of the
factors for integration and alignment of the specific work completion. The assignment would
include the analysis of project scope, objectives, KPI–project delivery, risk analysis, resource
plan, estimation plan, communication plan, project schedule, monitoring and controlling
strategy, changes applied on project schedule / cost, project status report, and change
management details. The completion of the report would result in forming the final
documentation development for the stakeholders.
2. Business Case
The business case is the analysis of the project background for the development of the
effective and smart management processing. The implication of the works had been aligned with
the utilization of the works and taking care of the project activities. The project plan would be
developed for considering the specific alignment tools. The project would form the reduction of
the OPEX/CAPEX in the organization by the installing the use of the ICT infrastructure,
services, and resources. The project is also responsible for the utilization of the works and
integrating the alignment of the factors for development of IT operations and enhancing the work
alignment.

4PROJECT PLAN DOCUMENT
3. Project Scope, Objectives
The project has been developed for utilizing the implication management operations and
forming the successful integration of the activities. The project scope is an improved work
proposition aligning the specific work execution and management of the activities. The project
scope development has been largely implied with the factors for integrating the alignment of the
specific work development. The scope of the project is given as,
a. Critical Factor Project Execution: The obtaining of the final decision has been
developed for aligning the management of the works and the implication of the smart
management development. The domain renaming was also a part of the project
management processing.
b. Activity Scheduling Dependency: The development of the architecture would be
supported by the development of effective documentation and processing. The project
would include the scope development for the architectural design development.
c. Preparation of OGC Vertical Branding: The new branding for the OGC would be
prepared with the alignment of the works for the continuation of the effective
implication management.
The objectives of the project would be identified with the analysis of the completed
analysis development model. The specific work would be developed considering the
management of the factors and forming the management of the improved work development.
The identified objectives of the project are,
 To reduce the OPEX/CAPEX with the installation of the ICT infrastructure
resources and services

5PROJECT PLAN DOCUMENT
 To enhance of the maintainability for standardization and efficiency improvement
development
 To unify ICT policies, standards, and operations for reorganizing and specializing
the IT departmental function enhancement
4. KPI – Project Delivery
The key performance indicators of the project would be dependent on the key benefits for
the project. The successful completion of the project would be dependent on the alignment of the
works and the management of the activities would be effectively done for integrating the
alignment for the successful management of the works. The ICT infrastructure development
would be effectively implied with the continuation of the factors for the listing model. The
shared services for multiple activities would be implied with the continuation of the improved
management process. The key performance indicators for the project would be implied with the
formation of the improved functional development. The listing of the key performance indicators
would be implied with the formation of the successful listing management works. The key
performance management activities would be implied with the listing of the activities and
formation of the activities management.
5. Risk Analysis
5.1 Risk identification
The project requires the use of the effective ICT technology development and implication
for improving the services of the organization. The identified risk factors for the project are,

6PROJECT PLAN DOCUMENT
Excessive scope deviation: The deviation of the project from the scope is another major
factor resulting in the formation of the issues for the users and problems for the developer. The
change in requirements would result in causing the major setback for the project team to finish
the project.
Project information and boundaries: The lack of the information related to the
development of the effective and improved management process can result in forming the major
implication issues. The major issues in technology information implementation is that it requires
considerable amount of information for listing the management works.
Branding package timeliness: The delays in completion of the works would be highly
cognitive in forming the alignment of the proper development. The activity would result in
consumption of the time and if more amount of time is required for the activity to be completed
then the final deliverable for the project would be delayed.
Resources for ICT Project Management: The shortage of resources is another major
factor for causing the problem in completion of the works and the alignment of the improved
management works. The lack of the resources would result in forming the issues in development
of the smart work development.
Budget Availability: The lack of resources would result in minimizing the project
budget resulting in major issues for the completion of the work. The lack of budget would tend to
cause the major issues in forming the effective project budgeting.
Communication, Decision making and Authorities: The lack of communication would
tend to form the impact in taking crucial decisions of the project and it would form the issues in

7PROJECT PLAN DOCUMENT
forming the limitation management. The authorities of the project users would be formed for
listing the development of the effective management processing.
Change Management issues: The change management issues would be dealt with the
consideration of the factors for improved analysis and development. The change management
would be impactful in forming the listing of the management processes.
Level of engagement and cooperation from stakeholders: The level of the engagement
and co-operations among the stakeholders would be tarnished due to the fact that the project
leaders would be limited to the formation of the improved management.
Standardization and compliances: The standardization of the works related to the
project activities would align with the considered for the formation of development. The
compliance and standard operation would be aligned with the formation of the works aligned
with the limitation of the activities and operations.
5.2 Risk categorization and analysis
Risk Name Risk
Type
Risk Description
Excessive scope
deviation
External The change in requirements would result in causing
the major setback for the project team to finish the
project.
Project information and
boundaries
Internal The major issues in technology information
implementation is that it requires considerable amount
of information for listing the management works.
Branding package
timeliness
Internal The delays in completion of the works would be
highly cognitive in forming the alignment of the
proper development.
Resources for ICT
Project Management
Internal The lack of the resources would result in forming the
issues in development of the smart work development.
Budget Availability Internal The lack of budget would tend to cause the major
issues in forming the effective project budgeting.

8PROJECT PLAN DOCUMENT
Communication,
Decision making and
Authorities
External The lack of communication would tend to form the
impact in taking crucial decisions of the project and it
would form the issues in forming the limitation
management.
Change Management
issues
Internal The change management issues would be dealt with
the consideration of the factors for improved analysis
and development.
Level of engagement and
cooperation from
stakeholders
External The level of the engagement and co-operations among
the stakeholders would be tarnished due to the fact
that the project leaders would be limited to the
formation of the improved management.
Standardization and
compliances
Internal The standardization of the works related to the project
activities would align with the considered for the
formation of development.
5.3 Risk management and mitigation plan
Risk Name Risk Management
Strategy
Risk Mitigation Plan
Excessive scope deviation Avoid Scope Management Plan should be
used
Project information and
boundaries
Exploit Information Collection from various
authentic resources
Branding package timeliness Mitigate Time Management Plan should be
used
Resources for ICT Project
Management
Transfer Resource Management Plan should
be used
Budget Availability Avoid Budget Management Plan should be
used
Communication, Decision
making and Authorities
Mitigate Communication Plan should be used
Change Management issues Avoid Change Management Plan should be
used

9PROJECT PLAN DOCUMENT
Level of engagement and
cooperation from stakeholders
Share Engagement and Motivation among
the project stakeholders should be
used
Standardization and
compliances
Accept Government and ACS standards
should be followed
6. Resource Plan
The resources required for the project include many human resources for taking care of
the work and implying the listing of the works. It would be helpful for the alignment of the
works and deploying the listing of the works and forming better and improved management
operations.
Role Name Responsibilities
Project Sponsor(s) Abdulaziz Al-Mujaibi Providing the specific alignment of
the works and integrating the listing
of the cohesive work development
Steering
Committee
The steering committee would be
responsible for analyzing the final
output and aligning the implication
of the listing works
Project Manager Hakeem Al-Tauqi Management of the works would be
aligned with the management works
listing the completion of the
formation works.
Team Members Ashraf Al-Jafari Leading Project team members for
the analysis of the works and
forming the development of the
activities
Kamran Ilyas Telecom\Network Lead
Faisal Qureishi cybersecurity\Mobility Lead
7. Estimation Plan
The project estimation plan would be developed with the compilation and development.
The cost estimation and the time calculation is done for ensuring the smart work development

10PROJECT PLAN DOCUMENT
works. The alignment would be implied for the management works and forming the successful
management of the works. The estimation plan would be developed for integrating the listing of
the alignment of works. The estimation plan is deployed with the continuation of the smart
analysis and formation of the successive work alignment.
8. Communication Plan
The communication plan for the project would be developed for ensuring the deployment
of the effective work integration and listing of the works. The deployment of the smart work
ethics would be employed for aligning the communication protocols and methods for transferring
information from one source to other or many. The information sharing has also some probable
frequencies for being executed. The following is the communication protocol/plan for the
project,
Communication
Mean
Information Sender Receiver Frequency
Reports/Documents Project Progress Project
Manager /
Project Team
Client/ Project
Manager
Weekly
Emails Change
Implication
Client Project Manager Once
Meetings Project
Requirements/
Project
Manager /Client
Project Team/
Project Manager
Once
Telephone/SMS Scope
Development
Quality Analyst Project Manager Monthly
9. Project Schedule
9.1 Task List
WBS Task Name
0 IT Integration (base)

11PROJECT PLAN DOCUMENT
1 Activity 1
2 Activity 2
3 Activity 3
4 Activity 4
5 Activity 5
6 Activity 6
7 Activity 7
8 Activity 8
9 Activity 9
10 Activity 10
11 Activity 11
12 Activity 12
13 Activity 13
14 Activity 14
9.2 Summary tasks
The project summary tasks would be developed with the implication of the agile
methodology for integrating the work development. The project summary tasks include the
project initiation, project planning, project designing, project executing, project monitoring, and
project closing.
9.3 WBS

12PROJECT PLAN DOCUMENT
IT Integration (base)
Activity 1 Activity 2 Activity 3 Activity 4 Activity 5 Activity 6 Activity 7 Activity 8 Activity 9 Activity 10 Activity 11 Activity 12 Activity 13 Activity 14
9.4 Predecessor linking
WBS Task Name Predecessors
0 IT Integration (base)
1 Activity 1
2 Activity 2
3 Activity 3
4 Activity 4 1
5 Activity 5 1
6 Activity 6 1
7 Activity 7 1
8 Activity 8 7SS
9 Activity 9 7SS
10 Activity 10 9SS+65 days
11 Activity 11 9SS+65 days
12 Activity 12 9SS+65 days
13 Activity 13 12SS+66 days
14 Activity 14 12SS+66 days
9.5 Resource allocation
Role Responsibilities
Project Providing the specific alignment of the works and integrating the listing of the

13PROJECT PLAN DOCUMENT
Sponsor(s) cohesive work development
Steering
Committee
The steering committee would be responsible for analyzing the final output
and aligning the implication of the listing works
Project
Manager
Management of the works would be aligned with the management works
listing the completion of the formation works.
Team
Members
Leading Project team members for the analysis of the works and forming the
development of the activities
Telecom\Network Lead
cybersecurity\Mobility Lead
9.6 Gantt Chart
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 IT Integration (base)325 days Mon 4/2/18 Fri 6/28/19
1 1 Activity 1 65 days Mon 4/2/18 Fri 6/29/18
2 2 Activity 2 65 days Mon 4/2/18 Fri 6/29/18
3 3 Activity 3 65 days Mon 4/2/18 Fri 6/29/18
4 4 Activity 4 130 days Mon 7/2/18 Fri 12/28/18
5 5 Activity 5 130 days Mon 7/2/18 Fri 12/28/18
6 6 Activity 6 130 days Mon 7/2/18 Fri 12/28/18
7 7 Activity 7 130 days Mon 7/2/18 Fri 12/28/18
8 8 Activity 8 260 days Mon 7/2/18 Fri 6/28/19
9 9 Activity 9 260 days Mon 7/2/18 Fri 6/28/19
10 10 Activity 10 195 days Mon 10/1/18 Fri 6/28/19
11 11 Activity 11 195 days Mon 10/1/18 Fri 6/28/19
12 12 Activity 12 195 days Mon 10/1/18 Fri 6/28/19
13 13 Activity 13 129 days Tue 1/1/19 Fri 6/28/19
14 14 Activity 14 129 days Tue 1/1/19 Fri 6/28/19
1/14 5/6 8/26 12/16 4/7 7/28 11/17
November 11 July 1 February 21 October 11
9.7 Network analysis diagrams

14PROJECT PLAN DOCUMENT
10. Monitoring and controlling strategy
10.1 Mile Stone
The milestone for the project plan involves Kick off meeting, Plan approval, Design
Completion, Development Completion, Testing Documentation, and Project Closure.
10.2 Base line
The status date for the baseline schedule is 11/18/18 and it has been given below,
% Complete WBS Task Name Duration Start Finish
43% 0 IT Integration (base)_baseline 325 days Mon 4/2/18 Fri 6/28/19
100% 1 Activity 1 65 days Mon 4/2/18 Fri 6/29/18

15PROJECT PLAN DOCUMENT
100% 2 Activity 2 65 days Mon 4/2/18 Fri 6/29/18
100% 3 Activity 3 65 days Mon 4/2/18 Fri 6/29/18
77% 4 Activity 4 130 days Mon 7/2/18 Fri 12/28/18
77% 5 Activity 5 130 days Mon 7/2/18 Fri 12/28/18
77% 6 Activity 6 130 days Mon 7/2/18 Fri 12/28/18
77% 7 Activity 7 130 days Mon 7/2/18 Fri 12/28/18
38% 8 Activity 8 260 days Mon 7/2/18 Fri 6/28/19
38% 9 Activity 9 260 days Mon 7/2/18 Fri 6/28/19
18% 10 Activity 10 195 days Mon
10/1/18 Fri 6/28/19
18% 11 Activity 11 195 days Mon
10/1/18 Fri 6/28/19
18% 12 Activity 12 195 days Mon
10/1/18 Fri 6/28/19
0% 13 Activity 13 129 days Tue 1/1/19 Fri 6/28/19
0% 14 Activity 14 129 days Tue 1/1/19 Fri 6/28/19
10.3 Critical Path,
ID Task
Mode
WBS Task Name Duration Start Finish
1 1 Activity 1 65 days Mon 4/2/18 Fri 6/29/18
7 7 Activity 7 130 days Mon 7/2/18 Fri 12/28/18
8 8 Activity 8 260 days Mon 7/2/18 Fri 6/28/19
9 9 Activity 9 260 days Mon 7/2/18 Fri 6/28/19
10 10 Activity 10 195 days Mon 10/1/18 Fri 6/28/19
11 11 Activity 11 195 days Mon 10/1/18 Fri 6/28/19
12 12 Activity 12 195 days Mon 10/1/18 Fri 6/28/19
13 13 Activity 13 129 days Tue 1/1/19 Fri 6/28/19
14 14 Activity 14 129 days Tue 1/1/19 Fri 6/28/19
2/25 4/8 5/20 7/1 8/12 9/23 11/4 12/16 1/27 3/10 4/21 6/2 7/14
January 1 April 1 July 1 October 1 January 1 April 1 July 1
10.4 Float/Slack

16PROJECT PLAN DOCUMENT
WBS Task Name Early Start Early Finish Late Start Late Finish Total Slack
0 IT Integration (base) Mon 4/2/18 Fri 6/28/19 Mon 4/2/18 Fri 6/28/19 0 days
1 Activity 1 Mon 4/2/18 Fri 6/29/18 Mon 4/2/18 Fri 6/29/18 0 days
2 Activity 2 Mon 4/2/18 Fri 6/29/18 Mon 4/1/19 Fri 6/28/19 260 days
3 Activity 3 Mon 4/2/18 Fri 6/29/18 Mon 4/1/19 Fri 6/28/19 260 days
4 Activity 4 Mon 7/2/18 Fri 12/28/18 Mon 12/31/18 Fri 6/28/19 130 days
5 Activity 5 Mon 7/2/18 Fri 12/28/18 Mon 12/31/18 Fri 6/28/19 130 days
6 Activity 6 Mon 7/2/18 Fri 12/28/18 Mon 12/31/18 Fri 6/28/19 130 days
7 Activity 7 Mon 7/2/18 Fri 12/28/18 Mon 7/2/18 Fri 12/28/18 0 days
8 Activity 8 Mon 7/2/18 Fri 6/28/19 Mon 7/2/18 Fri 6/28/19 0 days
9 Activity 9 Mon 7/2/18 Fri 6/28/19 Mon 7/2/18 Fri 6/28/19 0 days
10 Activity 10 Mon 10/1/18 Fri 6/28/19 Mon 10/1/18 Fri 6/28/19 0 days
11 Activity 11 Mon 10/1/18 Fri 6/28/19 Mon 10/1/18 Fri 6/28/19 0 days
12 Activity 12 Mon 10/1/18 Fri 6/28/19 Mon 10/1/18 Fri 6/28/19 0 days
13 Activity 13 Tue 1/1/19 Fri 6/28/19 Tue 1/1/19 Fri 6/28/19 0 days
14 Activity 14 Tue 1/1/19 Fri 6/28/19 Tue 1/1/19 Fri 6/28/19 0 days
11. Reflection & Conclusion
I have been playing the role of the project manager for the project and it had been a very
wonderful experience managing an IT project. The implication of the works would be implied
with the continuation of the specific development management. It was not easy for managing an
IT project as per my experience due to its ever-changing scope. The performance factor also
plays a significance role for taking care of the work development.
The integration had been managed with the consideration of the factors and managing the
implication development. The following assignment had been implied with the integration of the

17PROJECT PLAN DOCUMENT
improved work development. The business case analysis had be developed for listing the
analysis of the factors for integration and alignment of the specific work completion. The
assignment had include the analysis of project scope, objectives, KPI–project delivery, risk
analysis, resource plan, estimation plan, communication plan, project schedule, monitoring and
controlling strategy, changes applied on project schedule / cost, project status report, and change
management details.

18PROJECT PLAN DOCUMENT
Bibliography
Beringer, C., Jonas, D. and Kock, A., 2013. Behavior of internal stakeholders in project portfolio
management and its impact on success. International Journal of Project Management, 31(6),
pp.830-846.
Bozic, K.J., Ward, L., Vail, T.P. and Maze, M., 2014. Bundled payments in total joint
arthroplasty: targeting opportunities for quality improvement and cost reduction. Clinical
Orthopaedics and Related Research®, 472(1), pp.188-193.
Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.
Carver, C.L. and Klein, C.S., 2013. Action research: A tool for promoting faculty development
and continuous improvement in leadership preparation.
Clark, D.M., Silvester, K. and Knowles, S., 2013. Lean management systems: creating a culture
of continuous quality improvement. Journal of clinical pathology, pp.jclinpath-2013.
Dale, B.G. and Plunkett, J.J., 2017. Quality costing. Routledge.
Dessinger, J.C. and Moseley, J.L., 2015. Confirmative evaluation: Practical strategies for
valuing continuous improvement. John Wiley & Sons.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.
Fryer, K., Ogden, S. and Anthony, J., 2013. Bessant's continuous improvement model: revisiting
and revising. International Journal of Public Sector Management, 26(6), pp.481-494.

19PROJECT PLAN DOCUMENT
Fuller, M.A., Valacich, J.S., George, J.F. and Schneider, C., 2017. Information Systems Project
Management: A Process and Team Approach, Edition 1.1. Prospect Press.
Goetsch, D.L. and Davis, S.B., 2014. Quality management for organizational excellence. Upper
Saddle River, NJ: pearson.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach.
Routledge.
Heagney, J., 2016. Fundamentals of project management. Amacom.
Holtskog, H., 2013. Continuous Improvement beyond the Lean understanding. Procedia
CIRP, 7, pp.575-579.
Hwang, B.G. and Ng, W.J., 2013. Project management knowledge and skills for green
construction: Overcoming challenges. International Journal of Project Management, 31(2),
pp.272-284.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Kerzner, H., 2018. Project management best practices: Achieving global excellence. John Wiley
& Sons.
Lam, M., O'Donnell, M. and Robertson, D., 2015. Achieving employee commitment for
continuous improvement initiatives. International Journal of Operations & Production
Management, 35(2), pp.201-215.
Larson, E.W., Gray, C.F., Danlin, U., Honig, B. and Bacarini, D., 2014. Project management:
The managerial process (Vol. 6). Grandview Heights, OH: McGraw-Hill Education.

20PROJECT PLAN DOCUMENT
Leach, L.P., 2014. Critical chain project management. Artech House.
Lemire, M., Demers-Payette, O. and Jefferson-Falardeau, J., 2013. Dissemination of
performance information and continuous improvement: a narrative systematic review. Journal of
health organization and management, 27(4), pp.449-478.
Magar, V.M. and Shinde, V.B., 2014. Application of 7 quality control (7 QC) tools for
continuous improvement of manufacturing processes. International Journal of Engineering
Research and General Science, 2(4), pp.364-371.
Marchewka, J.T., 2014. Information technology project management. John Wiley & Sons.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking
project management performance and project success. International journal of project
management, 32(2), pp.202-217.
Mitra, A., 2016. Fundamentals of quality control and improvement. John Wiley & Sons.
Nadeem, E., Olin, S.S., Hill, L.C., Hoagwood, K.E. and Horwitz, S.M., 2013. Understanding the
components of quality improvement collaboratives: a systematic literature review. The Milbank
Quarterly, 91(2), pp.354-394.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Routledge.
Oakland, J.S., 2014. Total quality management and operational excellence: text with cases.
Routledge.