MGMT 6056 Project Cost Management

Running head: PROJECT MANAGEMENT
Human resource management system
Name of the Student
Name of the University
Author’s Note

PROJECT MANAGEMENT1
Table of Contents
Introduction................................................................................................................................2
1. Schedule management plan....................................................................................................2
1.1 Schedule model development..........................................................................................2
1.2 Project schedule model maintenance...............................................................................3
1.3 Control thresholds............................................................................................................3
1.4 Rules for performance measurement...............................................................................3
1.5 Reporting formats.............................................................................................................3
2. Work breakdown structure.....................................................................................................4
3. Activity precedence table.......................................................................................................6
4. Activity duration table............................................................................................................7
5.Network diagram view............................................................................................................9
6. Excel Gantt chart sheet...........................................................................................................9
7. Resource usage views and screenshots................................................................................11
8. Tracking Gantt chart view....................................................................................................15
Conclusion................................................................................................................................15
Bibliography.............................................................................................................................16

PROJECT MANAGEMENT2
Introduction
The paper mainly reflects on the development of the supply chain ERP module for
one of the Australian organizations. It is found that with the help of supply chain ERP
module, the organization will be able to improve efficiency as well as customer service. In
addition to this, the organization will be able to automate the workflow that further assists in
reducing the operational costs of the organization. The entire project will be completed
within 90 days by utilizing budget of around $100K.
The paper mainly focuses on schedule management plan, work breakdown structure,
resource allocation, activity precedence table. In addition to this, the paper also showcases the
resource usage within the project.
1. Schedule management plan
1.1 Schedule model development
AON diagram for the supply chain ERP module is provided below:
8 18
10 0 18
10
Team members appointment
10 10
0 0 10
0
Feasibility check
8 26
18 0 26
18
Scheduling of tasks
9 25
26 0 25
26
Time estimation
8 33
25 0 33
25
Hiring
9 41
330 41
33
Task allocation
8 49
41 0 49
41
Estimation of resources
9 58
49 0 58
49
Allocation of tasks to human resources
10 68
58 0 68
58
Team meeting
9 77
68 0 77
68
Project status report
9 86
77 0 86
77
Device deployment
10 96
86 10 96
86
Project prototype
8 104
96 8 104
96
Evaluating existing systems
10 114
104 0 114
104
Connecting data with SCM system
9 123
114 0 123
114
Software testing
9 132
1230 132
123
Database testing
8 140
132 0 140
132
Reviewing project
9 149
140 0 149
140
Holding meetings
7 156
149 0 156
149
Stakeholder sign off
6 162
156 0 162
156
Documentation
0 0
0 0 0
0
Initiation phase
0 162
162 0 162
162
Closure
Figure 1: AON diagram
(Source: Created by Author)

PROJECT MANAGEMENT3
1.2 Project schedule model maintenance
Project schedule model maintenance
Frequency of updates Who
Monthly Project manager, human resource manager,
IT manager
1.3 Control thresholds
Variances measurement When Control threshold limit
Project time During project progress 20%
Project cost Monthly basis 15%
Cost for resources During the project progress 12%
1.4 Rules for performance measurement
Rules for EVM measurement Frequency Who
Analyzing EVM requirements When needed Project manager
Identifying EVM calculation
concepts
When needed Project manager
Variance analysis When needed Project manager
Calculation of performance indexes When needed Project manager
1.5 Reporting formats
Content of the
report
To whom Who Frequency
Project timeline
management
Team leaders Team staffs When necessary
Project status
management
Team leaders Project manager When needed
Monthly progress
report
Project manager Team leader Monthly
2. Work breakdown structure
The work breakdown structure for supply chain ERP module development is given
below:
WBS Task Name
1 Development of supply chain ERP module
1.1 Project initiation and planning
1.1.1 Initiation phase
1.1.2 Project charter development
1.1.2.1 Feasibility check
1.1.2.2 Team members appointment
1.1.3 Project planning
1.1.3.1 Scheduling of tasks

PROJECT MANAGEMENT4
1.1.3.2 Time estimation
1.1.4 Appointment of team members
1.1.4.1 Hiring
1.1.4.2 Task allocation
1.1.5 Resource planning
1.1.5.1 Estimation of resources
1.1.5.2 Allocation of tasks to human resources
1.1.6 Communication plan
1.1.6.1 Team meeting
1.1.6.2 Project status report
1.1.6.3 Milestone 1: Completion of initiation an planning phase
1.2 Project execution and closure
1.2.1 Project execution
1.2.1.1 Device deployment
1.2.1.2 Project prototype
1.2.1.3 Milestone 2: Completion of execution phase
1.2.2 Development of database
1.2.2.1 Evaluating existing systems
1.2.2.2 Connecting database with SCM system
1.2.3 Testing
1.2.3.1 Software testing
1.2.3.2 Database testing
1.2.4 Project review
1.2.4.1 Reviewing project
1.2.4.2 Holding meetings
1.2.5 Project closure
1.2.5.1 Stakeholder's sign off
1.2.5.2 Documentation
M3 Milestone 3: Completion of closure phase
1.2.6.1 Project closure

PROJECT MANAGEMENT5
3. Activity precedence table
The activity precedence table is given below:
WBS Task Name Type Predecessors Lag/lead Rationale
1.1.1.2
Team members
appointment
Activities
4FF+1 day
Lead This work of
the activity
will be
completed 1
day earlier.
1.1.2.2 Time estimation
Activities
7SS-2 days
Lag This work of
the activity
will be
completed 2
days late.
1.1.3.2 Task allocation
Activities
10FF+1 day
Lead This work of
the activity
will be
completed 1
day earlier.
1.1.4.2
Allocation of
tasks to human
resources
Activities
13SS-1 day
Lag This work of
the activity
will be
completed 1
day late.
1.1.5.2 Project status
report
Activities 16FF+2 days Lead This work of
the activity
will be