INF30019: Human Resource Management System Project Plan Report

This report presents a comprehensive project implementation plan for updating the Human Resource Management (HRM) system at Macquarie Group. The project aims to modernize the existing system, transitioning from a mainframe to a client-server application to enhance efficiency and accessibility of employee information. The report includes a detailed executive summary, project charter outlining project objectives, approach, roles, responsibilities, constraints, and preliminary budget. It further elaborates on scope management, schedule management, cost management, quality management, and risk management plans. The HR management plan and stakeholder management plan are discussed to identify roles and responsibilities. The plan includes a work breakdown structure, schedule, budget, quality standards, risk management strategies, and communication strategies, providing a complete framework for the project's execution and management. The project's appendices include a Gantt chart and project cost baseline.

Running head: INFORMATION SYSTEM PROJECT MANAGEMENT
INF30019 Information Systems Project Management

1INFORMATION SYSTEM PROJECT MANAGEMENT
Executive Summary
The report is based on update a Human Resource Management (HRM) system so that the
organization can perform its business activities in Macquarie Group. In this project plan, there is
justification of the project needs and customer needs so that the purpose of this project is clear to
the reader. The project plan is based on objectives to update the existing HRM system so that the
organization is moving from the mainframe towards client server application. It provides
consistency of the functional areas of the Macquarie Group for better as well as easier access to
the employee information. A project charter is provided so that the start and end date of the
project is identified such that it helps to complete the plan in scheduled date. The project report
includes scope management plan, schedule and cost management plan to identify the needs of
the HRM system in the organization. Quality and risk management plan is provided to check
quality of the materials and identify the project risks. HR management plan and stakeholder
management plan is discussed to identify roles and responsibilities of the project resources.

2INFORMATION SYSTEM PROJECT MANAGEMENT
Table of Contents
1 Introduction and Objectives of the Project Plan......................................................................4
1.1 Overview of the Organization...........................................................................................4
1.2 Current Situation and Problem/Opportunity Statement....................................................4
1.3 Customer needs and organization goals............................................................................4
2 Project Charter.........................................................................................................................4
2.1 Project Information...........................................................................................................4
2.2 Project objectives..............................................................................................................5
2.3 Project approach................................................................................................................5
2.4 Roles and Responsibilities................................................................................................5
2.5 Project Constraints............................................................................................................5
2.6 Assumptions......................................................................................................................6
2.7 Preliminary Schedule and Budget Estimates....................................................................6
2.8 Plan Modification Rules....................................................................................................6
2.9 Approval Signatures..........................................................................................................6
3 Project Scope Management plan.............................................................................................6
3.1 Product description...........................................................................................................6
3.2 Project Deliverables..........................................................................................................7
3.3 Scope Statement................................................................................................................7
3.4 Work Breakdown Structure Development........................................................................7
3.5 Scope Change Management Process.................................................................................8
3.6 Plan Modification Rules....................................................................................................8
4 Schedule management plan.....................................................................................................8
4.1 Project Schedule................................................................................................................8
5 Cost management plan.............................................................................................................9
5.1 Project Budget...................................................................................................................9
5.2 Budget Constraints............................................................................................................9
6 Quality management plan......................................................................................................10
6.1 Quality Standards............................................................................................................10
6.2 Quality Metrics...............................................................................................................10

3INFORMATION SYSTEM PROJECT MANAGEMENT
6.3 Quality Management Approach......................................................................................10
6.4 Quality Assurance...........................................................................................................11
6.5 Quality Control...............................................................................................................11
7 Risk management plan...........................................................................................................11
7.1 Risk Management Strategies...........................................................................................11
7.2 Risk Management Tools.................................................................................................12
7.3 Data Sources...................................................................................................................12
7.4 Risk Categories...............................................................................................................13
7.5 Risk Probability and Impact............................................................................................13
8 HR management plan............................................................................................................14
8.1 Project Organization.......................................................................................................14
8.1.1 Project Team............................................................................................................14
8.1.2 Key Stakeholders.....................................................................................................15
8.2 Resource Requirements...................................................................................................16
8.3 Resource Assignment......................................................................................................17
9 Communication plan..............................................................................................................18
9.1 Stakeholder Analysis.......................................................................................................18
9.2 Project Reports................................................................................................................19
9.3 Project Meetings.............................................................................................................19
9.4 Project Information Accessibility...................................................................................20
9.5 Communications Summary.............................................................................................20
10 References..............................................................................................................................21
11 Bibliography..........................................................................................................................22
12 Appendix...................................................................................................................................23
1. Gantt chart.............................................................................................................................23
2. Project cost baseline.............................................................................................................24

4INFORMATION SYSTEM PROJECT MANAGEMENT
1 Introduction and Objectives of the Project Plan
1.1 Overview of the Organization
Macquarie Group is provided financial services such as banking, investment, advisory, as
well as management of fund services. It is an Australian multinational independent
investment bank with it’s headquarter is in Australia. The company was founded in the
year 1969. The company is managing under the group of “Macquarie Asset Management
as well as Macquarie Capital”. The strategic goal of the business organization is to update
its existing HRM system so that it can implement a human resource application and payroll
modules. The core applications of this system are providing functionality and HRM
processes such as payroll processes, compensation activities and benefits enrollment.
1.2 Current Situation and Problem/Opportunity Statement
The current Human Resource Management (HRM) system is required to update and there
should be replacement of its functionality that the current HRM system is provided to
manage as well as deliver payroll and base benefits of employee data. The current system
is useful as it will only record the employee data. The project plan is based on update the
existing HRM system of Macquarie Group so that there is enhancement of its functionality
such as web enabled self-services applications in addition to position management. In the
scope of this project plan, there should be incorporation of functionality into the project
plan as well as deliver the extra HRM modules (Gido, Clements and Clements 2014). In
this project plan, there is analysis of gap between the existing business situation as well as
stated objectives of the project.
1.3 Customer needs and organization goals
The goal of this project plan is to update the current HRM system and provide the project
client with a client server application for data enhancement as well as improvement over
the business processes of Macquarie Group with functions of human resources. The
customer is required such a system which helps to process payroll, compensation activities
and benefits enrollment.
2 Project Charter
2.1 Project Information
Project Start Date: 4th April, 2019
Project End Date: 13th November, 2019
Project Manager: Frank White

5INFORMATION SYSTEM PROJECT MANAGEMENT
Project Sponsor: John Smith
2.2 Project objectives
Following are the project objectives such as:
 To update the existing HRM system of Macquarie Group
 To move from the mainframe towards client server application
 To improve existing functions of HRM applications
 To provide consistency of the functional areas of the Macquarie Group
 To provide better as well as easier access to the information
2.3 Project approach
Following are list of the project approaches such as:
 Identification of the problems in the business organization
 Determine project desired outcomes
 Determine the timeline for each of the project phases
 Identification of the project stakeholders
2.4 Roles and Responsibilities
Name Role Position Contact Information
Frank White Project Manager Project Manager [e-mail]
John Smith Project Sponsor Project Sponsor smith@ organization.org
Alchemy Jace System Developer System Developer alchemy@
organization.org
Abby Jaden Technical Manager Technical Manager abby@ organization.org
2.5 Project Constraints
 There are lacks of availability of the development resources lead to boost in project
delivery instance. It would increase the project cost as alternative resources are
hired.
 There is project scope creep will lead to increase time, cost as well as resources. It
would reduce the project superiority and increase risk on project delivery time.
 The project quality team finds that superiority of development deliverables is bad;
therefore more project possessions are compulsory. It increases both time as well as
cost of the project plan.

6INFORMATION SYSTEM PROJECT MANAGEMENT
2.6 Assumptions
 The business process of Macquarie Group will change as well as customization is
done for the HRM system. The executive sponsor and the project team members
will interact with each other during the project lifecycle.
 There is proper financial support to the project throughout entire implementation
plan.
 There should be time commitment of the project groups will hold on to the project
duration. The system modifications as well as customization will need for the HR
system approval.
2.7 Preliminary Schedule and Budget Estimates
The total duration of the project is 160 days with start date is 4th April, 2019 and end date
is 13th November, 2019. The total budget of the project plan is $374,880.
2.8 Plan Modification Rules
Following are the list of the project modifications rules such as:
 Only the project manager has authority to do modifications into the plan related
documents.
 The plan success is acceptance of new HRM system by the users into the central
departments (Kerzner and Kerzner 2017).
 The risk management plan should be approved by the manager and sponsor.
 The budget is only be approved by the financial manager.
2.9 Approval Signatures
Project Manager:
Name Position Signature Date
Frank White Project Manager Frank White 13th November, 2019
John Smith Project Sponsor John Smith 13th November, 2019
Alchemy Jace System Developer Alchemy Jace 13th November, 2019
Abby Jaden Technical Manager Abby Jaden 13th November, 2019
3 Project Scope Management plan
3.1 Product description
The project is based on updating of the current HRM system and provided client server
applications. It will improve as well as rationalize the data plus business processes into the

7INFORMATION SYSTEM PROJECT MANAGEMENT
functions of human resources. The project manager and project team members have
reviewed the current system plus manual system support the functions of human resource.
3.2 Project Deliverables
 User interfaces
 Project design reports
 Implementation reports
 Web based development
 Maintenance of the client server application
 Setting of security of HRM system and its maintenance
 Conversions of the recent past information from the existing HRM system
3.3 Scope Statement
Following are the in-scope items of the project plan such as:
 Interface of the HRM system will require to develop
 Provide a client server based application
 Manpower planning, deliver payroll and base benefits of employee data
Following are the out-scope items of the project plan such as:
 Training to the project groups those have lack of technical knowledge
 Recruitment and selection of the employees based on the system
3.4 Work Breakdown Structure Development
It is developed based on each of the project phases those are required to update the HRM
system in the organization. Each of the project phases have sub-phases which are shown
as:

8INFORMATION SYSTEM PROJECT MANAGEMENT
Figure 1: Work Breakdown Structure
(Source: Created by author)
3.5 Scope Change Management Process
 Board members: Provide directions to the teams regarding changes and support the
team
 Evaluator: Give constructive as well as encourage feedback which will improve
confidence of the members (Lientz and Rea 2016).
 Verifier: Verify and inspect the changes made to the existing HRM system to meet
with organizational goals
 Project Manager: The project changes are documented into the project documents.
3.6 Plan Modification Rules
 Handling and regulating the plan baselines
 Align with the project guidelines for accomplishment of the project objectives
(Svejvig and Andersen 2015)
 Only the manager can approve the plan change documents
4 Schedule management plan
4.1 Project Schedule
Milestone Completion Date
Completion of project initiation phase Thu 4/25/19
Completion of analysis, design and planning phase Fri 4/26/19

9INFORMATION SYSTEM PROJECT MANAGEMENT
Completion of design, planning and scope phase Tue 8/27/19
Completion of system implementation and development phase Thu 9/19/19
Completion of project closure phase Fri 7/12/19
The assumptions which are taken into account for the schedule development are:
 The project phases should complete within the estimated time.
 All the project milestones should complete in scheduled completion time.
 The project phases are scheduled based on the project goals and objectives so that it can
meet with the organizations goals.
The Gantt chart of this project is shown in Appendix-1.
5 Cost management plan
5.1 Project Budget
The total project budget of the project “Update the human resource management system
for Macquarie Group” is $374,880.
WB
S Task Name Duration Cost
0 Human Resource Management
System for Macquarie Group 160 days $374,880.00
1 Project initiation phase 16 days $22,240.00
2 Analysis, design and planning phase 20 days $32,800.00
3 Design, planning and scope phase 84 days $125,600.00
4 System implementation and development
phase 82 days $122,880.00
5 Project closure phase 88 days $71,360.00
The estimated project cost baseline is shown in the Appendix-2.
5.2 Budget Constraints
In this particular project plan, budgetary estimation is done. Following are the project constraints
regarding the project budget such as:

10INFORMATION SYSTEM PROJECT MANAGEMENT
I. Lack of project resources involved in the project phases
II. Delay into one of the completion time of project phases
III. Increase in the project cost due to addition of extra resources
6 Quality management plan
6.1 Quality Standards
The standards which are applied to the various areas of the project regarding update of
HRM system are specified in below table:
Project Processes/Reports Quality Standards
Quality reporting The quality manager can determine quality of the system functions if
they meet with the project requirements. It provides report on the
services meet with the system requirements.
Status Reporting The project manager can check and control the project processes to
collect information of the project for status report (Fleming and
Koppelman 2016).
Response quality report The quality manager is focused on type of services that the agent is
provided based on metrics of the balance scorecards.
Effectiveness report The project manager checks the report to reveal how the project
agent can improve as result of the quality assurance program
(Hornstein 2015).
6.2 Quality Metrics
Project Deliverables Quality Metrics
Budget control The budget should be in +/- 10% to determine the percentage of
cost variances.
Customer Satisfaction The customers are provided with the feedback form to measure
level of the satisfaction. It is rating of 3-5 scale.
Schedule control The scheduled project time should be +/- 10 days to determine the
percentage of the schedule variances.
Product defect rate In order to reduce the cost and reduce waste, the organization has
established metrics to measure and control the product defects.
6.3 Quality Management Approach
Following are the list of the quality management tools and its respective details such as:

11INFORMATION SYSTEM PROJECT MANAGEMENT
a. Check sheet: This quality tool can be structured as well as prepared form to collect
and analyze project related data. The manager is responsible to supervise and
prepare the check sheet.
b. Control chart: This tool provides graphs to review how the process changes are
occurred on time. There is comparison of existing data to the past control limits
leads to conclusion that the process variation is reliable (Nicholas and Steyn 2017).
The quality manager is responsible to manage this quality tool.
c. Histogram: This tool can use the graph to show various value in sett of the data
occurred and project manager, quality manager is accountable for managing it.
6.4 Quality Assurance
a) Determine whether the product and service can meet with the system requirements
b) Communication plan is necessary to interact with the project team members in
addition to document the meeting minutes
c) Use ISO 9000 quality standard to make sure that quality of the system products are
meet (Fuller et al. 2017).
d) Understand and implement the improvement cycle
e) User acceptance testing of the proposed system is performed
6.5 Quality Control
i. Process control is focused on procedures in the company while the acceptance
testing is done to create inspection plan
ii. Product quality control is done to ensure that the organization makes quality system
products
iii. Inspection of each items required to update the HRIM system to ensure that it is
efficiently put together (Laudon and Laudon 2016).
iv. The machines are operated accurately and making the system products without any
flaws
7 Risk management plan
7.1 Risk Management Strategies
Process Name Process Description
Risk Identification The project risk teams will perform suggesting sessions at
the initiation phase. A project form is provided on the
company’s website to submit the risk factors occurred.
Risk Analysis The project manager determines consequences and
likelihood of each identified risks by using risk matrix
which is filled based on the scenery of risk in addition to
its affect on objectives (Joslin and Müller 2015).
Risk Evaluation The project is evaluated by determining the magnitude of