Update HRM System for Macquarie Group

The project plan aims to update the existing HRM system of Macquarie Group, moving from mainframe to client server application for better access to employee information.

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

12INFORMATION SYSTEM PROJECT MANAGEMENT
risks with combination of consequence, likelihood. The
risk ratings are done in the project risk register.
Risk Treatment The project manager assesses highest rank risks and set a
risk treatment plan to modify the risks for risk acceptance.
It is done by creating risk improvement strategies
(Peppard and Ward 2016).
Risk Monitoring and Review The project risk register is taken and used to monitor it by
tracking the affect and influence of each risk known in the
first risk administration process.
7.2 Risk Management Tools
Tool Name Tool Description
Interview It is conducted with the participants and stakeholders to
identify and review the risks.
Risk Status Report Weekly project report is being produced to give teams
with daily updates on the issues and prevention events
taken.
Brainstorming It is performed with group of the team members to
recognize the risks and discuss risk management solutions
(Arvidsson, Holmström and Lyytinen 2014).
Risk Register It is a document updated regular risks with list of
responses, root causes and rationalized risk classes.
7.3 Data Sources
Data Source Name Data Source Description
Risk Management Guide The guide provides guidelines to the project team
members regarding how to recognize and direct the risks.
Lessons Learned Database The PMO should maintain a lessons learned document
with the risks identified from previous project works.
Risk Management Plan A detailed risk plan is developed based on risk
identification, risk assessment and risk strategies to avoid
the identified risks (Galliers and Leidner 2014).

13INFORMATION SYSTEM PROJECT MANAGEMENT
7.4 Risk Categories
The table shows the list of the risks which are occurred in updating the HRM system in
Macquarie Group.
Categories Description
Market related The company faces competitive risks in the market due to
implementation of same HRM system in the financial
industry.
Budget There is escalation over the project cost because of poor
estimation of entire prices requisite to end the project plan.
Schedule The project activities are taken longer time as compared to
its expected time.
Resource The organizational employees have lack of technical
knowledge and skills to handle the HRM system.
7.5 Risk Probability and Impact
The table shows the list of risks, and then assign those risks with probability and impact to
determine total risk score for each individual risks.
Item Probability
(P)
Impact
(I)
Total Risk
Score
Risk mitigation
Poor scheduling of
the project
0.9 7 6.3 Proper project time
management plan is
prepared.
Lack of project
budget
0.4 5 2 Proper project budget
plan is prepared based
on all project expenses.
Lack of resources
hired based on
technical skills
0.7 4 2.8 More project resources
ate hired based on the
system implementation
requirements.
Lack of project fund 0.5 5 2.5 Collection of enough
funds for the project
based on planned project
cost.

14INFORMATION SYSTEM PROJECT MANAGEMENT
Poor quality and
accuracy of project
equipments
0.5 4 2 Quality management
plan is prepared.
Failure of the system
due to poor
maintenance
0.4 4 1.6 The proposed system is
tested and maintained on
weekly basis.
8 HR management plan
8.1 Project Organization
8.1.1 Project Team
Name Role Phone Number Email Address
Frank White Project Manager [phone] [e-mail]
John Smith Project Sponsor [phone] smith@ organization.org
Alchemy Jace System Developer [phone] [e-mail]
Abby Jaden Technical Manager [phone] [e-mail]
Miller James System Analyst [phone] miller@ organization.org
Robert King System Developer [phone] robert@ organization.org
Laura Collins System Tester [phone] laura@ organization.org
Jeff Allen Financial Manager [phone] jeff@ organization.org
Mark Martin Project Designer [phone] mark@ organization.org

15INFORMATION SYSTEM PROJECT MANAGEMENT
Figure 2: Project Team Structure
(Source: Created by author)
8.1.2 Key Stakeholders
Key Stakeholders
John
Smith
Frank
White
Abby
Jaden
Jeff Allen Miller
James
Robert
King
Laura
Collins
Mark
Martin
Role on
Project
Project
Sponsor
Project
Manag
er
Techni
cal
Manag
er
Financial
Manager
System
Analyst
System
Developer
System
Tester
Project
Designer
Organization VP of IT Direct
or of
Huma
n
Resour
ce
Project
Leader
Payroll
Manager
Internal
Audit
Internal
Audit
Internal
Audit
Internal
Audit
Phone
Number(s)
+61-
4803804
+61-
49067
+61-
49028
+61-
4903438
+61-
49068939
+61-
49068939
+61-
4906893
+61-
4903903
ProjectSponsorTechnicalManagerSystemAnalystSystemDeveloperSystemTesterFinancialManagerProjectManagerProjectDesigner

16INFORMATION SYSTEM PROJECT MANAGEMENT
79 9289 0483 9 0 0 90 85
Email
Address
smith@
organiza
tion.org
white
@orga
nizatio
n.org
abby
@orga
nizatio
n.org
jeff@
organizat
ion.org
miller@
organizati
on.org
miller@
organizati
on.org
miller@
organizat
ion.org
mark@
organizat
ion.org
Unique Facts Using
email
for
financial
docume
nts
Using
email
the
project
docum
ents
Techni
cal
details
are
provid
ed
Using
email for
financial
document
s
Analyze
the
features of
the system
through
presentati
on
Develop
the system
Test the
system
based on
needs
Design
the
system
based on
system
functions
Suggestions
for managing
communicati
ons
Project
progress
informe
d
Project
progre
ss
inform
ed
Techni
cal
plan is
provid
ed.
Project
progress
informed
System
functions
are
analyzed.
System
functions
are
developed
and
update the
status.
Project
progress
informed
Project
progress
informed
8.2 Resource Requirements
Figure 3: Resource Histogram
(Source: Created by author)
Project Manager
Executive Sponsor
Project Advisory Team
Technical Manager
Functional Manager
System Analyst
Designer
System Developer
Tester
Financial Manager0 hrs
200 hrs
400 hrs
600 hrs
800 hrs
1,000 hrs
1,200 hrs
Actual Work Remaining Work Baseline Work

17INFORMATION SYSTEM PROJECT MANAGEMENT
8.3 Resource Assignment
The resource assignment matrix is shown in following table:
R- Responsible; A- Accountable; C- Consulted; I- Informed
Task_ID Task Project
Sponso
r
Project
Manage
r
Tech
nical
Mana
ger
Financ
ial
Manag
er
Syste
m
Analys
t
Syste
m
Devel
oper
Syste
m
Teste
r
Proje
ct
Desig
ner
1 Project start up R R A C I
2 Document the
current business
processes
R A C I
3 Re-design and re-
engineering
processes
I I R A I R
4 Design and build
system prototype
A I R R R
5 Finalize the
project scope
R I I I I
6 Development of
data conversion
strategies
I R R C C
7 Update the
system
I I C R R R
8 Production and
support base
A I R A I
9 Support the
system based on
needs
I I R R A I
10 Final project
review
R R I I A I
The assumptions which are taken in case of project
resources are:
I. All the project resources will provide training on
the technical handling of machines and

18INFORMATION SYSTEM PROJECT MANAGEMENT
equipments.
II. Alternative resources should hire in case of
sudden absence of the project team members.
9 Communication plan
9.1 Stakeholder Analysis
Key Stakeholders
John
Smith
Frank
White
Abby
Jaden
Jeff Allen Miller
James
Robert
King
Laura
Collins
Mark
Martin
Role on
Project
Project
Sponsor
Project
Manag
er
Techni
cal
Manag
er
Financial
Manager
System
Analyst
System
Developer
System
Tester
Project
Designer
Organization VP of IT Direct
or of
Huma
n
Resour
ce
Project
Leader
Payroll
Manager
Internal
Audit
Internal
Audit
Internal
Audit
Internal
Audit
Contact
Information
+61-
4803804
79
+61-
49067
9289
+61-
49028
0483
+61-
4903438
9
+61-
49068939
0
+61-
49068939
0
+61-
4906893
90
+61-
4903903
85
Unique Facts Using
email
for
financial
docume
nts
Using
email
the
project
docum
ents
Techni
cal
details
are
provid
ed
Using
email for
financial
document
s
Analyze
the
features of
the system
through
presentati
on
Develop
the system
Test the
system
based on
needs
Design
the
system
based on
system
functions
Level of
interest
High High High Low High High Low High
Level of
influence
High High Low High High Low High Low
Suggestions
for managing
relationships
Project
progress
informe
d
Project
progre
ss
inform
ed
Techni
cal
plan is
provid
ed.
Project
progress
informed
System
functions
are
analyzed.
System
functions
are
developed
and
update the
Project
progress
informed
Project
progress
informed

19INFORMATION SYSTEM PROJECT MANAGEMENT
status.
9.2 Project Reports
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 Frank White Status
Form
Frank White
Project risk
report
Tracking the
project risks
Weekly Frank White Risk form Frank White
Project report Reviewing
all the project
documents
Regular
basis
Frank White Project
form
Frank White
Budget status Tracking
Gantt Chart
Bi-Weekly Jeff Allen Status
Form
Jeff Allen
Project lessons
learned
Tracking the
final project
report
At the
project
closure
hase
Frank White Lessons
learned
form
Frank White
9.3 Project Meetings
Purpose Frequency Attendees Reporting
Requirements
Status Review
Meeting
Update on project
status
Weekly Project team
members
Meeting Minutes
Budget
estimation
meeting
Update the total
project budget
Weekly Project team
members
Meeting Minutes
Project progress
meeting
Update the project
progress
Bi-weekly Project team
members
Final project
report

20INFORMATION SYSTEM PROJECT MANAGEMENT
9.4 Project Information Accessibility
A. The project related information is stored into the central database system of the
organization.
B. The project website is provided with central location to accumulate project templates and
documents.
9.5 Communications Summary
Stakeholder Type Communication
Medium
Frequency Responsible
Party
Jeff Allen Budget Report Presentation Weekly Frank White
John Smith Status Report Email Every Monday Frank White
Alchemy Jace Development
report of the
system
Email Weekly Frank White
Mark Martin Design report Email and
presentation
Weekly Frank White

21INFORMATION SYSTEM PROJECT MANAGEMENT
10 References
Arvidsson, V., Holmström, J. and Lyytinen, K., 2014. Information systems use as strategy
practice: A multi-dimensional view of strategic information system implementation and
use. The Journal of Strategic Information Systems, 23(1), pp.45-61.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.
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.
Galliers, R.D. and Leidner, D.E. eds., 2014. Strategic information management: challenges
and strategies in managing information systems. Routledge.
Gido, J., Clements, J. and Clements, J., 2014. Successful project management. Nelson
Education.
Hornstein, H.A., 2015. The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2),
pp.291-298.
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology
and project success in different project governance contexts. International Journal of Project
Management, 33(6), pp.1377-1392.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education
India.
Lientz, B. and Rea, K., 2016. Breakthrough technology project management. Routledge.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Routledge.
Peppard, J. and Ward, J., 2016. The strategic management of information systems: Building a
digital strategy. John Wiley & Sons.
Svejvig, P. and Andersen, P., 2015. Rethinking project management: A structured literature
review with a critical look at the brave new world. International Journal of Project
Management, 33(2), pp.278-290.

22INFORMATION SYSTEM PROJECT MANAGEMENT
11 Bibliography
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach.
Routledge.
Heldman, K., 2018. Project management jumpstart. John Wiley & Sons.
Kerzner, H., 2017. Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Larson, E.W. and Gray, C.F., 2015. A Guide to the Project Management Body of Knowledge:
PMBOK (®) Guide. Project Management Institute.
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.
Ramazani, J. and Jergeas, G., 2015. Project managers and the journey from good to great: The
benefits of investment in project management training and education. International Journal of
Project Management, 33(1), pp.41-52.
Todorović, M.L., Petrović, D.Č., Mihić, M.M., Obradović, V.L. and Bushuyev, S.D., 2015.
Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), pp.772-783.
Too, E.G. and Weaver, P., 2014. The management of project management: A conceptual
framework for project governance. International Journal of Project Management, 32(8),
pp.1382-1394.
Turner, J.R., 2014. Handbook of project-based management(Vol. 92). New York, NY: McGraw-
hill.
12

23INFORMATION SYSTEM PROJECT MANAGEMENT
12 Appendix
1. Gantt chart

24INFORMATION SYSTEM PROJECT MANAGEMENT
Figure 11.1: Gantt chart
(Source: Created by author using Ms Project)
2. Project cost baseline
WBS Task Name Duration Resource Names Cost
0
Human Resource
Management System for
Macquarie Group
160 days $374,880.00
1 Project initiation phase 16 days $22,240.00
1.1 Project start up 2 days Executive Sponsor, Project
Manager $3,040.00
1.2 Selection and training of
the project team 4 days Executive Sponsor, Project
Manager $6,080.00
1.3 Documentation of current
business processes 7 days Project Manager, System
Analyst $9,520.00
1.4 Kick off the project
meeting 3 days Functional Manager,
Project Advisory Team $3,600.00
1.5 Completion of project
initiation phase 0 days Project Advisory Team,
Project Manager $0.00
2 Analysis, design and
planning phase 20 days $32,800.00
2.1 Conduct the meetings 4 days Financial Manager,
Functional Manager $4,480.00
2.2 Re-design and re-
engineering procedures 7 days Project Advisory Team,
Project Manager $10,080.00
2.3 Designing and building
prototype 4 days
System Developer,
Technical Manager,
Designer
$6,720.00
2.4 Resolve the business
issues 6 days Project Manager, System
Analyst, Designer $11,520.00

25INFORMATION SYSTEM PROJECT MANAGEMENT
2.5 Completion of analysis,
design and planning phase 0 days Tester, System Developer $0.00
3 Design, planning and
scope phase 84 days $125,600.00
3.1 Building detailed project
plan 19 days Project Advisory Team,
Project Manager $27,360.00
3.2 Finalizing the project
scope 20 days Functional Manager,
Project Advisory Team $12,000.00
3.3 Inventory of the user
interfaces 25 days System Developer,
Technical Manager $20,160.00
3.4 Listing and prioritizing
the reports required 12 days Financial Manager,
Functional Manager $13,440.00
3.5 Development of data
conversion strategies 25 days Tester, System Developer,
Technical Manager $16,800.00
3.6 Development of security
plan 17 days Tester, System Developer $19,040.00
3.7 Recommendation of
project modifications 15 days Tester, System Developer $16,800.00
3.8 Completion of design,
planning and scope phase 0 days Project Advisory Team,
Project Manager $0.00
4 System implementation
and development phase 82 days $122,880.00
4.1 Update the system based
on project needs 13 days Project Advisory Team,
Project Manager $18,720.00
4.2 Identify the project
requirements 82 days $28,000.00
4.2.1 Functional
requirements 10 days Tester, System Developer $11,200.00
4.2.2 Non-functional 15 days Tester, System Developer $16,800.00

26INFORMATION SYSTEM PROJECT MANAGEMENT
requirements
4.3 Develop the system 12 days System Analyst, Tester,
System Developer $20,160.00
4.4 Production and support
phase 14 days Functional Manager,
Project Advisory Team $16,800.00
4.5 Produce the system 16 days Tester, System Developer $17,920.00
4.6 Support the system based
on needs 19 days System Developer,
Technical Manager $21,280.00
4.7
Completion of system
implementation and
development phase
0 days Project Manager, System
Developer $0.00
5 Project closure phase 88 days $71,360.00
5.1 Draft of the project plan 19 days Project Advisory Team,
Project Manager $27,360.00
5.2 Releasing of the
stakeholders 20 days Project Manager, System
Analyst $27,200.00
5.3 Final project review 21 days Project Manager $16,800.00
5.4 Completion of project
closure phase 0 days Project Manager $0.00