Showing posts with label hr management. Show all posts
Showing posts with label hr management. Show all posts

Friday, December 16, 2011

Chapter 22: Human Resource Management as part of Project Execution


Aim: To understand the following Human Resource Management related processes
• Acquire project team
• Develop project team
• Manage project team

Acquire Project Team:

No project can be completed without people. During Project Execution, the Project Manager actually acquires the project team by using the procedures defined during planning. Note, however, that the project manager might not have direct control over what resources are assigned to the project. The following aspects will be considered when the Manager is staffing for his project:
• Availability - Does the person’s schedule allow them to work in our project?
• Ability - Does the person have the proper skill set required for our project?
• Experience - Will the project require an individual with significant experience?
• Interest - Will the person want to work on the project?
• Cost - How much will the person cost? This is applicable while hiring Contractors and even when hiring internal resources.

The table shows the inputs, tools and techniques, and outputs for the acquire project team process.

Acquire Project Team
Inputs Tools & Techniques Outputs

Project management plan
Enterprise environmental factors
Organizational process assets

Pre-assignment
Negotiation Acquisition
Virtual teams

Project staff assignments
Resource calendars
Project management plan updates
A number of tools can be used in acquiring human resources. They are:

1. Pre-Assignment - Assignments made prior to beginning of execution. They might be named in the proposal, contract, or charter; or assigned because of a specific skill.
2. Negotiation - The project manager/team negotiates with functional managers or other managers for the resources they want. Organizational politics might be a factor in obtaining the desired resources.
3. Acquisition - Outside resources, such as consultants or contractors, are brought in through the acquisition process.
4. Virtual Teams - A team that is not located in the same place and relies on electronic tools (email, conference calls, and so forth) for communication. With decreasing communications costs and improved reliability, virtual teams have become more prevalent. This can also include off-shoring, where some of the project work is done in a separate country.

Exam Watch:
The use of virtual teams requires additional work during the communication planning process to ensure all the communication needs of the virtual team are met.

To know more about the Acquire Project Team process Click Here

Develop Project Team

Acquiring a team does not get the project completed. You need to develop them in order to be successful in your quest for project completion. Team development has two facets; increasing the competency of the team and improving the interaction among team members. Although team development should occur throughout the project, it is most effective when conducted early on in the project life cycle.

Exam Watch:
Teamwork is a critical factor for project success, and developing effective project teams is one of the primary responsibilities of the project manager

The table below shows the inputs, tools and techniques, and outputs for the develop project team process.

Develop Project Team
Inputs Tools & Techniques Outputs

Project staff assignments
Project management plan
Resource calendars

Interpersonal skills
Training
Team-building activities
Ground rules
Co-location
Recognition and rewards

Team performance assessments
Enterprise environmental factors updates
PMI lists a number of tools for team development, including general management skills, training, teambuilding activities, ground rules, co-location, and recognition and rewards:
• Interpersonal skills - These skills are sometimes referred to as soft skills and include empathy, creativity, influence, and group facilitation skills.
• Training - This is used for increasing competency. It might be formal or informal and can include classroom training, computer-based training, and coaching/mentoring.
• Team-building activities - This is any activity used to improve team cohesiveness. Teambuilding can encompass anything from a short activity at the beginning of a meeting to an offsite event. Even team participation in a project activity such as risk identification can serve to build team cohesiveness. Most teams progress through five stages of development:
o Forming - This is the phase in which the team meets and first learns about the project and their roles. Team members are still independent and not yet team oriented.
o Storming - The team begins to consider the project work and make decisions. Collaboration is important in this phase.
o Norming - Team members begin to adjust to one another, work together more closely and build trust.
o Performing - The team is well formed and works together well.
o Adjourning - The team completes project work and migrates to post-project work.
• Ground rules - These dictate the expected behavior of the team. Having the team develop the ground rules can serve as a teambuilding activity.
• Co-location - This is the opposite of virtual teams. PMI uses the team war room to describe a room where the team activities take place. Critical projects might use co-location to improve communication among team members.
• Recognition and rewards - These are used to motivate the team and reinforce positive behavior. The approach should be developed during planning and take into account the culture of team members, the type of behavior to be rewarded, and the budget.

Power is an important concept within the team environment. Although the project manager is in charge, he might not have legitimate power over all team members. Other team members must also rely on some power in order to accomplish their tasks.

The different types of Power available for the Project Manager are:
1. Legitimate – Power based on position/title
2. Referent – Power transferred from someone with legitimate power
3. Expert – Power based on knowledge
4. Reward – Power based on the ability to give rewards
5. Coercive – Power based on force or intimidation (Punishment)

Referent power is important for project managers. Often their authority does not equal their responsibilities on the project. This is especially true in a matrix environment when they don’t have direct authority over team members. A project manager should be able to integrate and apply a specific power as situations demand.

To know more about the Develop Project Team process Click Here

Manage Project Team

Once the project team members have been assembled and developed, they are ready for action. As the team begins the actual work of the project the focus shifts to the day-to-day management of the team. PMI addresses the task of managing the project team in the manage project team process. This is where you supervise your team and help them be a cohesive unit.

The table below shows the inputs, tools and techniques, and outputs for the manage project team process.

Manage Project Team
Inputs Tools & Techniques Outputs

Project staff assignments
Project management plan
Team performance assessments
Performance reports
Organizational process assets

Observation and conversation
Project performance appraisals
Conflict management
Issue log
Interpersonal skills

Enterprise environmental factors updates
Organizational process assets updates
Change requests
Project management plan updates
As mentioned previously, recognition and rewards are used to motivate the team. Motivation also occurs in managing the project team in the areas of interpersonal skills and conflict management. Knowledge of motivation theories is often tested in the PMP exam.

There are a lot of Motivational Theories about what motivates our team and how as a manager we can utilize them to effectively manage them.

Some of the Key Theories are:

1. Maslow’s Hierarchy of Needs - People have a hierarchy of needs, described as a pyramid. When one level is satisfied, they move onto the higher level needs. The base is physical needs (food, shelter), and then progress through safety and security, social needs (love, friendship), esteem, and finally self-actualization. On a project team, a worker would very likely be motivated by esteem, which can be self-esteem for mastery of a task or the esteem that comes from recognition by others for accomplishments.
2. Herzberg’s Motivation-Hygiene Theory - There are motivators and hygiene factors. Hygiene factors (pay, adequate supplies) prevent dissatisfaction but otherwise don’t motivate. Motivation comes from factors such as learning new skills or being promoted. A project manager must ensure hygiene factors are present and create the motivators as part of the assignment.
3. Expectancy Theory - People are motivated by the expectation of being rewarded for their work. In addition, if a team is told they are high performing, they will act that way, with the corollary for low performance also being true.
4. McClelland’s Achievement Theory - The three motivators for people are power, affiliation, and achievement. A person might not have one of these factors, and therefore is not motivated in his job.
5. McGregor’s X & Y Theory - Theory X states people are lazy and need autocratic leadership. Theory Y states people are generally hard workers and do not require constant supervision.

Team Formation

The theories outlined above focus primarily on development of individuals. PMI also discusses how the team forms as a cohesive unit. A leading theory in team development was developed by Bruce Tuckman. His theory states that teams go through stages: forming, storming, norming, and performing. He later added a fifth stage, adjourning.

The 5 stages are:
1. Forming - Initial stage when team is first brought together. Team goals and individual roles are unclear. High dependence on the project manager for direction.
2. Storming - Team members attempt to establish themselves within the team. Cliques might form. Still some uncertainty in goals.
3. Norming - Roles are accepted. Consensus exists. There might be social interactions outside the project.
4. Performing - Very clear focus. Little direction is needed from the project manager.
5. Adjourning - Break up of the team after completion of the project. Feelings of insecurity might exist.

To know more about the Manage Team process Click Here

Prev: Chapter 21

Next: Chapter 23

Friday, November 4, 2011

Chapter 16: Human Resource Management


Aim: To understand the process “Develop Human Resource Plan”

The project manager must fulfill the role of manager and leader of the project team. The project manager has the following responsibilities:
• Determine the HR needs of the project
• Negotiate with line managers for internal resources
• Acquire external resources through the procurement process
• Determine training needs
• Identify/plan team-building activities
• Determine the performance review approach for a project’s human resources
• Determine the reward and recognition approach for motivational purposes
• Document the team structure and each team’s responsibilities
• Create a project organization chart
• Develop a staffing management plan

Exam Watch:
PMI puts a high value on the project manager’s responsibilities to the team. Make sure you are comfortable with applying PMBOK content to hypothetical situations.
Key Human Resource Principles

Human resource management is the set of processes used to organize and manage the project team, also referred to as the project staff. A subset of the project team is the project management team, composed of the project manager, project sponsor, and others responsible for project management activities such as planning, controlling, and closing the project.

Project human resource management is composed of human resource planning, acquiring, developing, and managing the team. HR planning has a number of key deliverables, including project organization charts, the staffing management plan, and determining the roles and responsibilities of each human resource.

The table below shows the inputs, tools and techniques, and outputs for the develop human resource plan process.

Develop Human Resource Plan
Inputs Tools & Techniques Outputs

Activity resource requirements
Enterprise environmental factors
Organizational process assets

Organization charts and position descriptions
Networking
Organizational theory

Human resource plan
It is important to understand the various methods organizations use to depict and describe human resources and their attributes. They are:
1. Organizational breakdown structure (OBS) – The OBS Graphically displays work packages according to departments. It can be used to identify the work assigned to each department
2. Resource breakdown structure – The RBS Graphically displays resources by type. It is very effective in tracking costs. Also, it groups resources even if they are working on different deliverables
3. Responsibility assignment matrix (RAM) – The RAM is a chart displaying resources and for which assignments they are responsible. It allows easy identification of all responsibilities for a given resource
4. RACI matrix – The RACI Matrix is a specific type of RAM that shows the resources that are responsible, accountable, consulted, and informed in project activities. It provides more detail than RAM
5. Position description – It is a text-based description of responsibilities. Provides a high level of detail for a given position

Note
An organizational breakdown structure (OBS) is a graphical representation of the project team arranged according to an organization’s existing structure. A resource breakdown structure is also a graphical representation but is organized according to resource type. A resource breakdown structure can contain resources other than human resources, such as equipment, and can be used to track costs as well.

In addition to graphical representations, resources might be documented in matrix-based documents such as a responsibility assignment (RACI) matrix.
These documents are effective communication tools to ensure team members understand for which assignments they are responsible.

Note: RACI stands for responsible, accountable, consult, inform.

The Staffing Management Plan

The staffing management plan is used to document the type of resources needed and the timing for those resources. The plan includes how the resources will be acquired, start and end dates, training requirements, policies and procedures for the team, and the team recognition approach and budget.

Exam Watch:
Resource leveling is a schedule network analysis that results in schedule changes, start and finish dates, based on resource constraints. That is, resource leveling might cause start and finish dates to change if multiple activities rely on over-committed resources.

You can learn more about the “Develop Human Resource Plan” process by Clicking Here

Prev: Chapter 15

Next: Chapter 17

Monday, July 4, 2011

Chapter 63: Big Picture of Human Resource Management

As mentioned in the previous chapter, managing the resources in our project team is an art and not all project managers are efficient in doing that.

Trivia:
If you have at least a few years of work experience, you would have seen that the managers with whom you worked were variedly capable when it comes to managing your team. Some were very capable and motivated the team to perform at their highest level whereas some were a disaster which made the team scramble for cover the moment the manager walked into the room. So, as you can see, the abilities of the manager can make or break the team and hence we must ensure that we take care of our team in the best possible way.

Human resource management as part of project management means developing the human resource plan, acquiring the project team, developing the project team, and managing the project team. This includes:
Acquire Project Team - This is the process of filling the roles determined during human resource planning with actual staff assignments.
Develop Project Team - This is the process of developing an optimal team by improving the individual competencies, improving the interaction among the individual team members, and thereby improving the team environment.
Manage Project Team - This is the process of tracking performance of and providing feedback to the individual team members, managing changes related to the team, and resolving issues.

The whole thing can be explained as a picture as below:


The project team has two dimensions: independence and interdependence. Each member has an independent assignment in the sense that the member owns that part of the work, is responsible for completing it, and must have the skills and competency to complete it. However, all these individual assignments may have dependencies among them, requiring the team members to interact with one another.

To summarize, you hire or recruit individual members for your team, but for the projects success, all of these individual recruits work as a team and work towards the common goal which is “Success of the Project”

To accomplish this, the team needs to be developed from the individuals and managed. Don't worry; we will be learning this aspect in the subsequent chapters.

Prev: Introduction to HR Management

Next: Acquiring a Project Team

Chapter 62:Introduction to Human Resource Management

We have begun the execution phase of the project. To execute a project you need resources and the success of the project heavily depends on the performance of these resources and the optimal utilization of available resources by the project manager. Therefore, coordinating and managing resources, including human resources, is an integral part of project execution. During project planning, you define roles and assign responsibilities to those roles. Individuals who play these roles perform the responsibilities of the roles to execute the project work.

The process of obtaining the individuals to fill these roles and therefore become the members of the project team is called acquiring the project team.

A team is a group of individuals who perform individual responsibilities to work inter-dependently on their independent assignments. From a scientific viewpoint, a team is a dynamic entity, and its dynamics are determined by the interaction among its members. Therefore, for the team to be successful, it has to be effective in both dimensions:

1. Its members must be competent in performing their individual assignments and
2. The interaction among them must be overall constructive.

To ensure that you need to continually develop and manage the project team.

To obtain the right individuals for the project team and to develop and manage the team is an art, whereas the effective team taking the project to success is a science that will unfold itself automatically if you do the art part right.

In the subsequent few chapters, we will learn the tips and tricks to master the art part (which is our responsibility as the project manager)

Prev: Important Terms - Managing Project Work

Next: Big Picture of HR Management

Wednesday, May 4, 2011

Chapter 7: Project Management Knowledge Areas

In the previous chapter, we saw the project lifecycle in detail. In this chapter, we are going to take a look at the Project Management Knowledge Areas.

So, lets get started!!!

Project Management Knowledge Areas

Managing projects requires applying knowledge, skills, and tools and techniques to project activities in order to meet the project objectives. You do this by performing some processes at various stages of the project, as discussed in the previous chapter. That means processes are part of the knowledge required to manage projects. Each aspect of a project is managed by using the corresponding knowledge area. For example, each project has a scope that needs to be managed, and the knowledge required to manage scope is in the knowledge area called project scope management. To perform the project work within the project scope, you need human resources, which need to be managed; the knowledge used to manage human resources is called human resource management.

I guess, by now you have a fair idea of where we are getting to.

Each process belongs to one of the nine knowledge areas:


  1. Scope Management
  2. Time Management
  3. Cost Management
  4. Human Resource Management
  5. Procurement Management
  6. Risk Management
  7. Quality Management
  8. Integration Management
  9. Communications Management
  10. Stakeholder Management (This Knowledge Area was introduced in PMBOK 5th Edition)


Each knowledge area has its own place in the project lifecycle and they are all equally important from a project managers point of view. In practical experience you might fine one or more areas to have a greater impact on the outcome of the project, but nonetheless they are all important and play a vital role in the success or failure of a project.

Let us now look at each of these knowledge areas in detail…

Project scope management

The primary purpose of project scope management is to ensure that all the required work and only the required work is performed to complete the project successfully. This is accomplished by defining and controlling what is included in the project and what is not.

Obviously, these activities are performed by using the corresponding processes. So, project scope management, in part, defines the work required to complete the project. It’s a finite amount of work and will require a finite amount of time and resources. These need to be managed as well. The other knowledge areas cover them.

Project time management

The primary purpose of project time management is to develop and control the project schedule. Any project has a timeline by which it is expected to be completed and a well managed project is expected to complete by the set timelines.


Trivia:
Even though project time management takes care of all requisite parameters to manage the timelines of a project effectively, in reality you might find that the project managers are running around like headless chickens trying to get the project completed on time. This usually happens almost always. As an efficient manager, we should ensure that we don't become one of those headless chickens.

Project cost management

The primary goal of project cost management is to estimate the cost and to complete the project within the approved budget. This is one of the important activities because our bosses wouldn't approve if we exceed our approved budgets and it might have severe repercussions. Not to mention, finishing a project within budget with money to spare will always help you during your own appraisal!


The resources needed to complete the project activities include human resources, which need to be managed as well.

Project human resource management

The primary purpose of project human resource management is to obtain, develop, and manage the project team that will perform the actual project work.


There will be situations in which your organization does not have the expertise to perform certain schedule activities in-house. For this or for several other reasons, you might want to acquire some items or services from a vendor Ex: Servers from IBM. This kind of acquisition is called procurement, which also needs to be managed.

Project procurement management

The primary purpose of procurement management is to manage acquiring products (that is, products, services, or results) from outside the project team in order to complete the project. The external vendor who offers the service is called the seller.

Project Risk Management:

Any work, that is done will always have some uncertainties that give rise to project risks, which need to be managed. A project risk is an event that, if it occurs, has a positive or negative effect on meeting the project objectives. The primary purpose of project risk management is to identify the risks and respond to them should they occur.

The goal of risk management is to help meet the project objectives and to help avoid/handle situations that might compromise the project schedule or outcome.

Project quality management

Project quality is defined as the degree to which a project satisfies its objectives and requirements. For example, a high-quality project is a project that is completed on time and with all the work in the project scope completed within the planned budget.

Project integration management

The project is initiated, planned, and executed in pieces, and all those pieces are related to each other and need to come together. That is where integration management comes in. For example, integrating different subsidiary plans into the project management plan needs to be managed. Project integration management includes developing the project charter, developing the project management plan, directing and managing project execution, monitoring and controlling project work, performing integrated change control, and closing the project or a phase of a project.

While managing all the aspects of the project, you as the project manager, will need to coordinate different activities and groups, and for that you need to communicate.

Project communication management

It is absolutely mandatory for the success of the project that the project information is generated and distributed in a timely fashion and to all the stakeholders involved. Experienced managers would say communication is the most important aspect of a project and the most important skill a project manager must have. Without any doubt, communication management is certainly a critical component of project management and a common thread that runs through the project lifecycle.

Project Stakeholders Management

As of the PMBOK 4th Edition there was no such knowledge area. In fact, processes related to stakeholders were actually part of Communications Management. Considering how critical managing stakeholders is, to the success of a project, PMBOK 5th edition included a separate knowledge area for the same. Anyone who is involved with or impacted by a project is a stakeholder and this knowledge area deals with how the project manager is supposed to manage them.

As you can see, managing a project involves performing a set of processes at the various stages of the project. Accordingly, processes are grouped corresponding to these stages and the groups are called process groups.

Processes are part of the knowledge required to manage projects. Each of these processes belongs to one of the nine knowledge areas identified in the PMBOK Guide. So a process has a dual membership—one in a process group, indicating at what stage of the project the process is performed, and the other in a knowledge area, indicating what aspect of the project is managed by using the process.

Below is a table that relates these two aspects:



Now that we know all the processes involved in project management, we will next take a look at the Project Stakeholders.

Previous: Project Lifecycle

Next: Project Stakeholders
© 2013 by www.getpmpcertified.blogspot.com. All rights reserved. No part of this blog or its contents may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of the Author.

Followers

Popular Posts