Final Project Plan: ERP Implementation at ADP (INF30019)

This document presents a comprehensive project plan for the implementation of an Enterprise Resource Planning (ERP) system at Automatic Data Processing Inc. (ADP), a company providing cloud-based solutions and business process outsourcing services. The plan outlines the project's objectives, which include identifying ERP requirements, understanding the implementation process, and designing the ERP system. An Agile project methodology is chosen, and the project charter details project information, roles, responsibilities, constraints, assumptions, and preliminary schedules and budget estimates. The plan includes a detailed Work Breakdown Structure (WBS), a project schedule with milestones, a Gantt chart, and a scope management plan. The project aims to enhance ADP's business management, improve decision-making, and increase customer satisfaction through the ERP system. The project is scheduled to start in October 2018 and finish in March 2020, with a total estimated cost of $403,600.00. The plan also includes change management processes and plan modification rules. This project plan is a critical component of the INF30019 Information Systems Project Management course at Swinburne University of Technology.

Swinburne University of Technology
Faculty of Information and Communication Technologies
INF30019 Information Systems Project Management

FINAL PROJECT PLAN
1 Introduction and Objectives of the Project Plan
1.1 Overview of the Organization
Automatic Data processing Inc. is a provider of cloud based solutions to the clients along with the
business process outsourcing services. The Company ADP offers a number of services to the clients that
include the human capital management, payroll services along with benefit administration. The
company is a fairly large size company operation across 110 countries.
The top management of the company ensures customer satisfaction with the services it provides. The
goal of the company is to improve its customers’ base by providing valued services to the customer.
1.2 Current Situation and Problem/Opportunity Statement
In order to help the company achieve its goals, development and implementation of an enterprise
resource planning system for the organization is proposed.
With the increase in the client base, it becomes essential to for the organization to enhance its
performance by reducing the service delivery time. Since the company is operating in a number of
locations, it becomes essential to integrate the different processes of business that are running within
the organization. For that, implementation of enterprise resource planning system is recommended for
the organization.
This system will help in better business management by automatic report generation and enhancing the
decision making process. The organization is in need of an ERP system for better management of the
clients’ needs and enhancing the customers’ satisfaction. Although the business has been delivering
premium services to its clients over the years, it becomes mandatory to keep up to the expectations of
the clients. With the implementation of ERP, the decision making ability with the staffs and the
managers of the organization will increase as well.
2 Project Charter
2.1 Project Information
Project Start Date: Thu 04-10-18
Project End Date: Mon 09-03-20

Project Manager: Please Insert
Project Sponsor: Please Insert
2.2 Project objectives
The Project ERP Implementation in ADP has the following objectives-
1. To identify the requirements of ERP in ADP
2. To understand the implementation process of ERP system
3. TO design and implement the ERP
2.3 Project approach
An Agile project methodology approach is chosen for the project. For accurate project implementation,
a project plan is needed to be prepared. The implementation plan will be followed throughout the
project implementation phase for better project management.
2.4 Roles and Responsibilities
The roles and the responsibilities of different stakeholders of the ERP implementation project in ADP is
represented in the following table-
Name Role Position Contact Information
Please Insert Resource manager Resource
manager
[e-mail]
Frank White Project Manager Project Manager [e-mail]
Please Insert Functional
Manager
Functional
Manager
[e-mail]
2.5 Project Constraints
There are certain project constraints that have been identified in the project planning phase. The
constraints associated with the project are as follows-
1. Schedule Constrains: The project implementation plan estimates the schedule of
implementation of ERP project in ADP. However, it is seen that the project is needed to be
implemented is a constricted schedule which is one significant constraint.
2. Time: The project has a time constraint as well.
3. Scope: The project is needed to be implemented according to the identified project scope,
which is a major project constraint as well.

2.6 Assumptions
The assumptions considered in the planning process of ERP implementation
project in ADP are as follows-
1. One of the assumptions associated with the project is that it can be
completed in the estimated schedule
2. It is assumed that continuous resource availability can be maintained in
the project implementation phase.
2.7 Preliminary Schedule and Budget Estimates
The Preliminary Project schedule for development and implementation of the ERP project is
represented in the table below-
WBS Task Name Duration Start Finish
0 ERP Implementation 373 days Thu 04-10-18 Mon 09-03-20
1 Project Starts 0 days Thu 04-10-18 Thu 04-10-18
2 Project Initiation 29 days Thu 04-10-18 Tue 13-11-18
2.1 Identification of the
Requirements 7 days Thu 04-10-18 Fri 12-10-18
2.2 Requirements Gathering 5 days Mon 15-10-18 Fri 19-10-18
2.3 Development of Project Charter 7 days Mon 22-10-18 Tue 30-10-18
2.4 M1: Approval of Project
Charter 10 days Wed 31-10-18 Tue 13-11-18
3 Project Planning 29 days Wed 14-11-18 Mon 24-12-18
3.1 Project Scheduling 5 days Wed 14-11-18 Tue 20-11-18
3.2 Estimation of the budget of the
Project 7 days Wed 14-11-18 Thu 22-11-18
3.3 Development of Project
Implementation Plan 12 days Fri 23-11-18 Mon 10-12-18
3.4 M2: Approval of Project
Implementation Plan 10 days Tue 11-12-18 Mon 24-12-18
4 Execution Phase 135 days Tue 25-12-18 Mon 01-07-19
4.1 Project Designing 30 days Tue 25-12-18 Mon 04-02-19
4.2 Coding the ERP 60 days Tue 05-02-19 Mon 29-04-19
4.3 Testing each Modules 45 days Tue 30-04-19 Mon 01-07-19
4.4 M3: Completion of ERP
Development 0 days Mon 01-07-19 Mon 01-07-19
5 Testing 95 days Tue 02-07-19 Mon 11-11-19
5.1 Unit testing 15 days Tue 02-07-19 Mon 22-07-19
5.2 System Testing 30 days Tue 23-07-19 Mon 02-09-19
5.3 Integration testing 20 days Tue 03-09-19 Mon 30-09-19

5.4 Bug Fixing 30 days Tue 01-10-19 Mon 11-11-19
5.5 M4: Completion of Testing and
Bug Fixing 0 days Mon 11-11-19 Mon 11-11-19
6 Project Release 47 days Tue 12-11-19 Wed 15-01-20
6.1 ERP software launch 2 days Tue 12-11-19 Wed 13-11-19
6.2 Training 15 days Thu 14-11-19 Wed 04-12-19
6.3 Bug Fixing (if any) 30 days Thu 05-12-19 Wed 15-01-20
6.4 M5: Delivery of Functional
ERP software 0 days Wed 15-01-20 Wed 15-01-20
7 Project Closure 38 days Thu 16-01-20 Mon 09-03-20
7.1 Collection of Users' Feedback 15 days Thu 16-01-20 Wed 05-02-20
7.2 Project Evaluation 30 days Thu 16-01-20 Wed 26-02-20
7.3 Documentation 5 days Thu 27-02-20 Wed 04-03-20
7.4 Payment Completion 1 day Thu 05-03-20 Thu 05-03-20
7.5 Resource Release 1 day Fri 06-03-20 Fri 06-03-20
7.6 Client Sign Off 1 day Mon 09-03-20 Mon 09-03-20
8 M6: Project Ends 0 days Mon 09-03-20 Mon 09-03-20
The Gantt chart of the project is represented in the following picture-
Figure 1: Representing the Gantt Chart of the project
(Source: Generated by Author using MS project)

The work activities marked in red in the Gantt chart above depict the critical path of the project
The estimated budget for the project is as follows-
Task Name Duration Cost
ERP Implementation 373 days $403,600.00
Project Starts 0 days $0.00
Project Initiation 29 days $12,000.00
Identification of the Requirements 7 days $6,440.00
Requirements Gathering 5 days $2,200.00
Development of Project Charter 7 days $3,360.00
M1: Approval of Project Charter 10 days $0.00
Project Planning 29 days $15,680.00
Project Scheduling 5 days $2,400.00
Estimation of the budget of the Project 7 days $2,240.00
Development of Project Implementation
Plan 12 days $11,040.00
M2: Approval of Project
Implementation Plan 10 days $0.00
Execution Phase 135 days $282,400.00
Project Designing 30 days $257,200.00
Coding the ERP 60 days $14,400.00
Testing each Modules 45 days $10,800.00
M3: Completion of ERP Development 0 days $0.00
Testing 95 days $30,000.00
Unit testing 15 days $3,600.00
System Testing 30 days $7,200.00
Integration testing 20 days $4,800.00
Bug Fixing 30 days $14,400.00
M4: Completion of Testing and Bug
Fixing 0 days $0.00
Project Release 47 days $43,480.00
ERP software launch 2 days $880.00
Training 15 days $6,600.00
Bug Fixing (if any) 30 days $36,000.00
M5: Delivery of Functional ERP
software 0 days $0.00
Project Closure 38 days $20,040.00
Collection of Users' Feedback 15 days $10,800.00
Project Evaluation 30 days $7,200.00
Documentation 5 days $600.00
Payment Completion 1 day $480.00
Resource Release 1 day $480.00
Client Sign Off 1 day $480.00

M6: Project Ends 0 days $0.00
2.8 Plan Modification Rules
There are certain rules related to the modification of the project, plan which is as follows-
1. Modifications are only permitted in unavoidable circumstances such as resource unavailability.
2. No one apart from the Project Manager has the authority to modify the project plan document.
2.9 Approval Signatures
Project Manager:
As project manager on ERP Implementation in ADP, I have reviewed the information contained
in the Project Charter and agree to its content.
Name Position Signature Date
Please Insert Project Sponsor Please Insert Please Insert
Project Manager
ADP
The signatures above represent stakeholders’ agreement and acknowledgement of the
information contained in this document.
3 Project Scope Management plan
3.1 Product description
The project aims in improving the process of business management in ADP. The automatic report
generation with the help of the ERP system to be implemented will further help in accurate decision
making. Improved decision making helps in enhancing the services offered to the customers and thus it
will increase the customers’ satisfaction as well.
3.2 Project Deliverables
The Major Deliverables of the Project are listed below-
Task Name Duration Start Finish
Project Initiation 29 days Thu 04-10-18 Tue 13-11-18
Project Planning 29 days Wed 14-11-18 Mon 24-12-18
Execution Phase 135 days Tue 25-12-18 Mon 01-07-19
Testing 95 days Tue 02-07-19 Mon 11-11-19

Project Release 47 days Tue 12-11-19 Wed 15-01-20
Project Closure 38 days Thu 16-01-20 Mon 09-03-20
3.3 Scope Statement
In Scope
1. The system can be implemented within the set schedule and budget
2. Training to the employees will be provided
Out Scope
1. Change in the requirements of the project
2. Project Maintenance
3.4 Work Breakdown Structure Development
The Work breakdown structure of the project is represented below-
WBS Task Name
0 ERP Implementation
1 Project Starts
2 Project Initiation
2.1 Identification of the Requirements
2.2 Requirements Gathering
2.3 Development of Project Charter
2.4 M1: Approval of Project Charter
3 Project Planning
3.1 Project Scheduling
3.2 Estimation of the budget of the Project
3.3 Development of Project Implementation Plan
3.4 M2: Approval of Project Implementation Plan
4 Execution Phase
4.1 Project Designing
4.2 Coding the ERP
4.3 Testing each Modules
4.4 M3: Completion of ERP Development
5 Testing
5.1 Unit testing
5.2 System Testing
5.3 Integration testing
5.4 Bug Fixing
5.5 M4: Completion of Testing and Bug Fixing

6 Project Release
6.1 ERP software launch
6.2 Training
6.3 Bug Fixing (if any)
6.4 M5: Delivery of Functional ERP software
7 Project Closure
7.1 Collection of Users' Feedback
7.2 Project Evaluation
7.3 Documentation
7.4 Payment Completion
7.5 Resource Release
7.6 Client Sign Off
8 M6: Project Ends
The Work breakdown structure of the is represented in the following picture-
ERP Implementation
Project Starts Project Initiation
Identification of the
Requirements
Requirements Gathering
Development of Project
Charter
M1: Approval of Project
Charter
Project Planning
Project Scheduling
Estimation of the budget
of the Project
Development of Project
Implementation Plan
M2: Approval of Project
Implementation Plan
Execution Phase
Project Designing
Coding the ERP
Testing each Modules
M3: Completion of ERP
Development
Testing
Unit testing
System Testing
Integration testing
Bug Fixing
M4: Completion of Testing
and Bug Fixing
Project Release
ERP software launch
Training
Bug Fixing (if
any)M5: Delivery of
Functional ERP software
Project Closure
Collection of Users'
Feedback
Project Evaluation
Documentation
Payment Completion
Resource Release
Client Sign Off
M6: Project Ends
Figure 2: Representing the work breakdown structure of the Project
(Source: Created by author using MS Project and MS schedule Pro)
3.5 Scope Change Management Process
The change in scope of the project is needed to be avoided in the project implementation process. The
changes in scope will be identified by the project implementation team by evaluation the project
requirements and the project evaluation process. With regular project monitoring, controlling the
changes in the project will be possible. The change control board of ADP will be responsible for
managing the scope change in the project.
3.6 Plan Modification Rules
The project implementation plan can be modified only in certain circumstances which are as follows-
1. Project Implementation plan can be modified only during the change in scope of the project
2. Only the project owner and the project manager will be allowed to modify the project plan.

4 Schedule management plan
4.1 Project Schedule
Milestone Completion Date
M1: Approval of Project Charter Tue 13-11-18
M2: Approval of Project Implementation
Plan
Mon 24-12-18
M3: Completion of ERP Development Mon 01-07-19
M4: Completion of Testing and Bug Fixing Mon 11-11-19
M5: Delivery of Functional ERP software Wed 15-01-20
M6: Project Ends Mon 09-03-20
The detailed Gantt Chart is provided in Appendix 1
The assumptions that has been taken into consideration for schedule estimation are as follows-
1. It is assumed that the project resources estimated will be continuously available
2. It is assumed that the project can be completed within this estimated schedule.
5 Cost management plan
5.1 Project Budget
The budget estimated for the project is represented in the following table-
Task Name Duration Cost
ERP Implementation 373 days $403,600.00
Project Starts 0 days $0.00
Project Initiation 29 days $12,000.00
Identification of the Requirements 7 days $6,440.00
Requirements Gathering 5 days $2,200.00
Development of Project Charter 7 days $3,360.00
M1: Approval of Project Charter 10 days $0.00
Project Planning 29 days $15,680.00
Project Scheduling 5 days $2,400.00
Estimation of the budget of the Project 7 days $2,240.00
Development of Project Implementation
Plan 12 days $11,040.00
M2: Approval of Project
Implementation Plan 10 days $0.00

Execution Phase 135 days $282,400.00
Project Designing 30 days $257,200.00
Coding the ERP 60 days $14,400.00
Testing each Modules 45 days $10,800.00
M3: Completion of ERP Development 0 days $0.00
Testing 95 days $30,000.00
Unit testing 15 days $3,600.00
System Testing 30 days $7,200.00
Integration testing 20 days $4,800.00
Bug Fixing 30 days $14,400.00
M4: Completion of Testing and Bug
Fixing 0 days $0.00
Project Release 47 days $43,480.00
ERP software launch 2 days $880.00
Training 15 days $6,600.00
Bug Fixing (if any) 30 days $36,000.00
M5: Delivery of Functional ERP
software 0 days $0.00
Project Closure 38 days $20,040.00
Collection of Users' Feedback 15 days $10,800.00
Project Evaluation 30 days $7,200.00
Documentation 5 days $600.00
Payment Completion 1 day $480.00
Resource Release 1 day $480.00
Client Sign Off 1 day $480.00
M6: Project Ends 0 days $0.00
5.2 Budget Constraints
The constrains related to the budget estimation of the project is represented as follows-
1. A rough order to magnitude estimate is considered for budget estimation and therefore, there are
chances of budget revision.
2. The Budget is estimation in the project initiation phase.
6 Quality management plan
6.1 Quality Standards
The Quality standards that are applied to the ERP implementation project in ADP is represented
in the following table-
Project Processes/Reports Quality Standards
Reporting the Resource Flow The resource manager will closely monitor the resource flow and

the resource requirement
Status Reporting The project manager will be monitoring the various process of
collecting information from the project status reports.
Risk Reports The project manager will be responsible for risk identification and
management
6.2 Quality Metrics
The different quality standard applied to the ERP implementation project in ADP is represented
in the following table-
Project Deliverables Quality Metrics
Improved Management The employees of the organization should be asked to give
feedback on the implementation of information system. The
positive ratings should be a 4 or more in an average.
Customer Satisfaction The customers associated with the project will be given a customer
satisfaction form and the average rating should range from 3.0 or
better on a scale of 5
6.3 Quality Management Approach
Quality Management is an essential need for project management. For
assuring delivery of project of accurate quality, a quality control manager is
hired for the project. The customers’ feedback will be considered as an
important tool for management of the project. The quality manager will be
responsible for regular monitoring of the work processes for better project
delivery.
6.4 Quality Assurance
In order to ensure accurate quality of the project, the performance of the
project is needed to be evaluated. In order to ensure whether the accurate
quality of product is delivered, feedback from both the employees and the
clients of the organization will be taken. Majority of the positive feedback will
ensure accurate quality of the project is delivered.
6.5 Quality Control
Quality Control is an essential aspect of project management as well. For accurate quality control,
certain information will be collected that will help in deciding whether an accurate quality of project or

product is achieved. There are certain metrics that will help in easier quality control and quality
management. These metrics are as follows-
1. The project should be executed according to the project implementation plan that is developed
2. The Quality Manager should do regular quality check up on each of the modules of project that is
being developed.
7 Risk management plan
7.1 Risk Management Strategies
The management strategies of the risk associated with the implementation of ERP in ADP is
represented in the following table.
Process Name Process Description
Risk Identification The primary stage of risk management is identification of the
risks associated with the project
Risk Assessment After risk identification the risks in the project is needed to be
assessed.
Risk Mitigation The Risks with high severity is needed to be mitigated first
followed by the risks with low priority
7.2 Risk Management Tools
There are certain tools that can help in easier risk management. Description of the tools that can be
used in this project is represented in the following table-
Tool Name Tool Description
Risk Register The use of risk register by the project team will help in easier
risk assessment
Risk Status Report These reports will be generated on a weekly basis. Sharing of
these reports will keep the stakeholders informed about the
risks
Risk management Plan This plan will keep the stakeholders informed about the
different risk mitigation approaches, that will be followed in
this project.
7.3 Data Sources
Data Source Name Data Source Description

Weekly Portfolios Maintained by Project team
Lesson learnt Database PMO maintained database
Weekly status Reports Database maintained by project team.
7.4 Risk Categories
The risks associated with the ERP implementation project in ADP are as follows-
Categories Description
Schedule Risk The project could not be completed within the set
schedule
Budget Risk The project is not completed within the set budget
Risk of Scope creep There have been significant changes in the project
scope
Resource Risk Shortage of resources
7.5 Risk Probability and Impact
Item Probability (P) Impact (I) Total Risk Score
Schedule Risk .8 9 7.2
Budget Risk .7 10 7.0
Risk of Scope creep .6 8 4.8
Resource Risk .7 6 4.2
Risk Mitigation
As a mitigation approach to the major risks identified, the project will be implemented strictly
following the project plan so that no delays in the project are observed. For mitigation of the
budget risk, the budget is prepared by considering various requirements. The resource risk and
risk of scope creep can be mitigated by strictly sticking to the requirements while project
implementation.

8 HR management plan
8.1 Project Organization
8.1.1 Project Team
The project team members associated with the project are as follows-
Name Role Phone Number Email Address
Resource Manager 111-111-1112 [e-mail]
Frank White Project Manager 111-111-1111 [e-mail]
Functional Manager 111-111-1113 [e-mail]
Quality Manager 111-111-1114 [e-mail]
The representation of project team-
Figure 3: Representing the team structure
(Source: Created by author)
8.1.2 Key Stakeholders
Key Stakeholders
Project Manager Sponsor ADP
ProjectSponsorResourceManagerFunctionalManagerQualityManagerProjectManager

Role on Project Project Manager Project Sponsor Project Owner
Organization ADP ADP ADP
Phone Number(s) Please Insert Please Insert Please Insert
Email Address Please Insert Please Insert Please Insert
Unique Facts Prefers to make use
of email for status
reporting
Prefers to make
use of email for
communication
Prefers to make
use of email for
communication
Suggestions for managing
communications
Keep informed about
the project progress
Should be kept
informed of the
project progress
Should be kept
informed of the
project status
8.2 Resource Requirements
The resource overview of the project is represented in the following picture –
Project Manager
Business Analyst
Resource Manager
Programmer
Testing Team
Technical writer
Functional Manager
Project Evaluation Team
Quality Manager
0 hrs
200 hrs
400 hrs
600 hrs
800 hrs
1,000 hrs
1,200 hrs
Actual Work Remaining Work Baseline Work
Figure 4: Representing Project Resource
(Source: generated by Author using MS project)
8.3 Resource Assignment
The resource assignments of the project are represented in the following table-
Task ID Task Name Duration Resource Names
0 ERP Implementation 373 days

1 Project Starts 0 days Project Manager
2 Project Initiation 29 days
2.1 Identification of the
Requirements 7 days Functional
Manager ,Project Manager
2.2 Requirements Gathering 5 days Functional Manager
2.3 Development of Project
Charter 7 days Project Manager
2.4 M1: Approval of Project
Charter 10 days
3 Project Planning 29 days
3.1 Project Scheduling 5 days Project Manager
3.2 Estimation of the budget of
the Project 7 days Resource Manager
3.3 Development of Project
Implementation Plan 12 days Functional
Manager ,Project Manager
3.4 M2: Approval of Project
Implementation Plan 10 days
4 Execution Phase 135 days
4.1 Project Designing 30 days
Hardware
[1],Programmer ,Software
[1]
4.2 Coding the ERP 60 days Programmer
4.3 Testing each Modules 45 days Testing Team
4.4 M3: Completion of ERP
Development 0 days
5 Testing 95 days
5.1 Unit testing 15 days Testing Team
5.2 System Testing 30 days Testing Team
5.3 Integration testing 20 days Testing Team
5.4 Bug Fixing 30 days Testing Team ,Programmer
5.5 M4: Completion of Testing
and Bug Fixing 0 days
6 Project Release 47 days

6.1 ERP software launch 2 days Functional Manager
6.2 Training 15 days Functional Manager
6.3 Bug Fixing (if any) 30 days
Functional
Manager ,Project
Manager ,Quality Manager
6.4 M5: Delivery of Functional
ERP software 0 days
7 Project Closure 38 days
7.1 Collection of Users' Feedback 15 days Functional
Manager ,Quality Manager
7.2 Project Evaluation 30 days Project Evaluation Team
7.3 Documentation 5 days Technical writer
7.4 Payment Completion 1 day Project Manager
7.5 Resource Release 1 day Project Manager
7.6 Client Sign Off 1 day Project Manager
8 M6: Project Ends 0 days
The assumptions associated with the resource allocation are as follows-
1. It is assumed that the project resources will be continuously available
2. it is assumed that the resources will agree on being paid on a selected rate.

9 Communication plan
9.1 Stakeholder Analysis
The list of stakeholders and their roles in the project is represented in the following table-
Project Manager Resource Manager Sponsor
Role on Project Project Manager Resource Sponsor Project Sponsor
Organization ADP ADP ADP
Contact Information
Unique Facts Makes use of email
for status reporting
Prefers use of
email for project
documents
Makes use of email for
communication
Level of Interest High High High
Level of Influence Medium Low High
Suggestions for
managing
relationships
Keep informed about
the project
Keep informed
about the project
progress
Keep informed about the
project progress
9.2 Project Reports
The report to be generated for ERP implementation project ADP is represented in the
following table-
Data Needed Frequency
of
Collection
Responsible
Party for Data
Collection &
Analysis
Report
Media &
Format
Responsible
Party for
Distributing
Report
Schedule Status Tracking
Gantt Chart
Bi-Weekly Project Manager Status Form Functional
manager
Budget Status Tracking
investments
Monthly Project Manager Status Form Functional
manager
Resource Status Tracking
Resource
Requirements
Weekly Resource
Manager
Status Form Functional
manager
9.3 Project Meetings
The details of the meetings to be help on ERP implementation project ADP is represented
in the following table-

Purpose Frequency Attendees Reporting
Requirements
Status Review
Meeting
Update on project
status
Weekly Stakeholders Meeting Minutes
Project progress
Meeting
Update on project
progress
Bi-Weekly Project owner
and
stakeholders
Meeting Minutes
9.4 Project Information Accessibility
The information about the project would be stored in the company database for easier
management and accessibility.
9.5 Communications Summary
Stakeholder Type Communication
Medium
Frequency
Project manager Status Report Email and face to face Weekly
Resource Manager Resource Needs Email Bi-Weekly
Project Owner Project Progress Email Monthly

Bibliography
Agyei, W., 2015. Project planning and scheduling using PERT and CPM techniques with linear
programming: case study. International Journal of Scientific & Technology Research, 4(8), pp.222-227.
Bryde, D., Broquetas, M. and Volm, J.M., 2013. The project benefits of building information modelling
(BIM). International journal of project management, 31(7), pp.971-980.
Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.
Carvalho, M.M.D. and Rabechini Junior, R., 2015. Impact of risk management on project performance:
the importance of soft skills. International Journal of Production Research, 53(2), pp.321-340.
Creemers, S., De Reyck, B. and Leus, R., 2015. Project planning with alternative technologies in uncertain
environments. European Journal of Operational Research, 242(2), pp.465-476.
Drucker, P., 2012. Management challenges for the 21st century. Routledge.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management. Project
Management Institute.
Haimes, Y.Y., 2015. Risk modeling, assessment, and management. John Wiley & Sons.
Harris, E., 2017. Strategic project risk appraisal and management. Routledge.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach. Routledge.
Heagney, J., 2016. Fundamentals of project management. Amacom.
Heldman, K., 2018. PMP: project management professional exam study guide. John Wiley & Sons.
Herroelen, W., 2014. A risk integrated methodology for project planning under uncertainty. In Essays in
Production, Project Planning and Scheduling (pp. 203-217). Springer, Boston, MA.
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.
Kaiser, M.G., El Arbi, F. and Ahlemann, F., 2015. Successful project portfolio management beyond
project selection techniques: Understanding the role of structural alignment. International Journal of
Project Management, 33(1), pp.126-139.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning, scheduling,
and controlling. John Wiley & Sons.
Kerzner, H., 2017. Project management metrics, KPIs, and dashboards: a guide to measuring and
monitoring project performance. John Wiley & Sons.

Kerzner, H., 2018. Project management best practices: Achieving global excellence. John Wiley & Sons.
Leach, L.P., 2014. Critical chain project management. Artech House.
Loosemore, M., Raftery, J., Reilly, C. and Higgon, D., 2012. Risk management in projects. Routledge.
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.
Mirza, M.N., Pourzolfaghar, Z. and Shahnazari, M., 2013. Significance of scope in project
success. Procedia Technology, 9, pp.722-729.
Morris, P.W., 2013. Reconstructing project management. John Wiley & Sons.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and technology.
Routledge.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Teller, J. and Kock, A., 2013. An empirical investigation on how portfolio risk management influences
project portfolio success. International Journal of Project Management, 31(6), pp.817-829.
Yang, L.R., Chen, J.H. and Wang, H.W., 2012. Assessing impacts of information technology on project
success through knowledge management practice. Automation in construction, 22, pp.182-191.

Appendix 1: Gantt Chart
The Gantt chart of the project is represented in the following picture-
Figure 5: Representing the Gantt Chart of the project
(Source: Generated by Author using MS project)
The work activities marked in red in the Gantt chart above depict the critical path of the project
The estimated budget for the project is as follows-
Appendix 2: Cost Flow
The cost flow of the project is represented in the following picture-

412341234123412341234123412341234123412341
$0.00
$50,000.00
$100,000.00
$150,000.00
$200,000.00
$250,000.00
$0.00
$50,000.00
$100,000.00
$150,000.00
$200,000.00
$250,000.00
$300,000.00
$350,000.00
$400,000.00
$450,000.00
Cost Cumulative Cost
Figure 6: Representing the cost flow
(Source: generated by author using MS project)
Appendix 3: MS Project File