Unit5-1

26 May Unit5-1

Introduction

This section explains the purpose and importance of having a human resources management plan. It should provide a general description of what the plan includes and explain how the project manager and project team can use the plan to help them manage the project effectively.

Roles and Responsibilities

Roles and responsibilities of team members and stakeholders must be clearly defined in any project. Depending on the organizational structure, project team members may represent many different groups/departments and act in the interest of different functional managers. Additionally, team members may have varying degrees of authority and responsibility. When listing roles and responsibilities the following should be included:

· Role – description of the portion of the project for which the member is accountable

· Authority – the level at which the member may make decisions, apply project resources, or make approvals

· Responsibility – the work a team member must perform to complete assigned work activities

· Competency – the skill(s) required to complete assigned project activities

Project Manager (PM), (1 position): responsible for the overall success of the Software Upgrade Project. The PM must authorize and approve all project expenditures. The PM is also responsible for approving that work activities meet established acceptability criteria and fall within acceptable variances. The PM will be responsible for reporting project status in accordance with the communications management plan. The PM will evaluate the performance of all project team members and communicate their performance to functional managers. The PM is also responsible for acquiring human resources for the project through coordination with functional managers. The PM must possess the following skills: leadership/management, budgeting, scheduling, and effective communication.

Project Organizational Charts

This section provides a graphic display of the project tasks and team members. The purpose of this is to illustrate the responsibilities of team members as they relate to the project tasks. Tools such as responsible, accountable, consult, inform (RACI) or responsibility assignment matrix (RAM) may be used to aid in communicating roles and responsibilities for the project team. Additionally, organizational or resource breakdown structures may be used to show how responsibilities are assigned by department or by type of resource respectively. It should be noted that the level of detail may vary depending on project complexity.

The following RACI chart shows the relationship between project tasks and team members. Any proposed changes to project responsibilities must be reviewed and approved by the project manager. Changes will be proposed in accordance with the project’s change control process. As changes are made all project documents will be updated and redistributed accordingly.

	Project Manager	Design Engineers	Implementation Manager	Training Leads	Functional Managers	Department Managers
Requirements Gathering	A	R	R	C	C	I
Coding Design	A	R	C		C	I
Coding Input	A	R
Software Testing	A	R	C		I	I
Network Preparation	A	C	R		I	I
Implementation	A	C	R	C	C	C
Conduct Training	A			R	C	C

Key:

R – Responsible for completing the work

A – Accountable for ensuring task completion/sign off

C – Consulted before any decisions are made

I – Informed of when an action/decision has been made

Staffing Management

This section contains information on several areas including: when and how human resource requirements will be acquired, the timeline for when resources are needed and may be released, training for any resources with identified gaps in skills required, how performance reviews will be performed, and the rewards and recognition system to be used. It is important to note that depending on the scope of the project there may be other items included in staffing management (government and/or regulatory compliance, organizational health and safety, etc).

Software Project Upgrade Resource Histogram

0

10

20

30

40

50

60

70

80

90

Week 1Week 2Week 3Week 4Week 5

Timeline

Work Hours per Week

Design Engineers (2 employees)

Implementation Manager (1 employee)

Training Lead (1 employee)

Training:

Performance Reviews:

Recognition and Rewards:

Sponsor Acceptance

Approved by the Project Sponsor:

Date:

<Project Sponsor>

<Project Sponsor Title>