© 2008 prentice hall3-1 introduction to project management chapter 3 managing project teams...

54
© 2008 Prentice Hall 3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George

Upload: harvey-morris

Post on 17-Dec-2015

239 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-1

Introduction to Project Management

Chapter 3Managing Project Teams

Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George

Page 2: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-2

Facts

• Most important and expensive component of a project are those involved directly or indirectly with the project

• Quality and time estimates depend on the effectiveness of the project team

• Good IT people are in short supply

Page 3: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-3

What is a Project Team?• Two or more people who share the same

goals, are interdependent, have complementary skills, and are mutually accountable to the organization and to each member of the team

http://www.wisegeek.com/what-is-the-difference-between-a-team-and-a-group.htm

Page 4: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-4

Project Team Development Stages

• Form

• Storm

• Norm

• Perform

• Adjourn

http://www.mindtools.com/pages/article/newLDR_86.htm

Page 5: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-5

Forming

• Become familiar with fellow team member(s)

• Establish team goals

• Provide work assignments

Page 6: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-6

Storming

• Set goals

• Establish power levels

• Identify leadership roles

Page 7: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-7

Norming

• Build interpersonal relationships with team members

• Develop a common purpose for the project

• Develop standard operating procedures

Page 8: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-8

Performing

• Start project work

• Stage ends when the project is completed

Page 9: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-9

Adjourning

• Complete project assignments

• Team members are released from the project and reassigned

• Different emotional reactions exhibited

Page 10: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-10

Project Team Performance Factors

http://en.wikipedia.org/wiki/High-performance_teams

Page 11: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-11

Different Work Personalities

Page 12: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-12

Project Team Selection

• Keep teams small and manageable

• Get the right personalities

• Embrace diversity

• Reuse successful teams

• Plan ahead to get the right people

• Use your network

Page 13: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-13

Motivation

• An individual’s intensity, direction, and persistence toward attaining a goal

• Individuals are motivated by different things in different ways

• An individual’s level of motivation may be reflected through their:– Job satisfaction– Absenteeism– Turnover

Page 14: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-14

Need Theories of Motivation

• Hierarchy of Needs (Maslow)

• ERG Theory

• Two-Factor Theory

• Theory of Needs

Page 15: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-15

Maslow’s Hierarchy of Needs• A hierarchy of needs – physiological, safety,

social, esteem, and self-actualization – where as each need is met, the next higher-level need becomes the motivating focus

Page 16: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-16

ERG Theory

• Three core needs – Existence, Relatedness, and Growth – in which more than one need may be operative at the same time and that if the fulfillment of a higher-level need is unrealized, the desire to satisfy a lower-level need becomes the motivating focus

Page 17: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-17

Two-Factor Theory

• Intrinsic factors – motivational factors – like achievement, recognition, advancement, and responsibility are related to job satisfaction while extrinsic factors – hygiene factors – like salary, relationships with colleagues, and work conditions are associated with dissatisfaction

Page 18: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-18

Theory of Needs

• A person’s motivation can be explained by their need for achievement, power, and affiliation

Page 19: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-19

Process Theories of Motivation

• Theory X and Theory Y• http://en.wikipedia.org/wiki/Theory_X_and_Theory_Y

• Theory Z

• Goal-Setting Theory

• Equity Theory

• Reinforcement Theory

• Expectancy Theory

Page 20: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-20

Theory X and Theory Y

• Theory X: Assumes that people dislike work, are lazy, dislike responsibility, and must be coerced into working hard

• Theory Y: Assumes that people like work, are creative, like autonomy, and seek responsibility

Page 21: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-21

Theory Z

• Reflects the Japanese work philosophy which includes a belief in lifetime employment, strong company loyalty, and group consensus

Page 22: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-22

Goal-Setting Theory

• A specific and difficult goal, with clear feedback related to how well a person is doing in relation to meeting a goal, can be used to enhance a person’s work productivity

Page 23: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-23

Equity Theory

• Individuals compare their work inputs and outcomes with others and then respond to eliminate any inequities between those comparisons

Page 24: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-24

Reinforcement Theory

• States that both positive and negative feedback conditions behavior

Page 25: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-25

Expectancy Theory• People exert a high level of effort when (1)

he or she believes that effort will lead to a good performance appraisal, (2) that a good appraisal will lead to rewards, and (3) that these rewards will satisfy the person’s needs

Page 26: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-26

Motivating Team Members

• Recognize individual differences

• Use specific goals and feedback

• Allow team members to participate in decisions that affect them

• Link rewards to performance

• Check the system for equity • http://www.mindtools.com/pages/article/newTMM_67.htm

Page 27: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-27

Manager vs. Leader

• Manager: A formal position of authority in an organization that is responsible for planning, organizing, directing, monitoring, and controlling the activities of others

• Leader: A person, who, by virtue of his or her personal attributes, can exert influence on others

• http://www.mindtools.com/pages/article/newLDR_41.htm

Page 28: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-28

Leadership• The ability to influence people toward the

achievement of goals

• Attributes:

– Intelligence and competence in task and organizational activities

– Maturity and a broad range of interests– Considerate interpersonal skills and respect for the

needs and differences of others– Goal-oriented focus and a strong motivation to achieve

success– http://www.mindtools.com/pages/article/leadership-theories.htm– http://www.mindtools.com/pages/article/newLDR_84.htm

Page 29: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-29

Trait Theories of Leadership

• A set of leadership theories which state that personality, appearance, competence, and other personal characteristics differentiate leaders from non-leaders

Page 30: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-30

Behavioral Theories of Leadership

• Set of leadership theories which state that a person’s actions determine his or her potential to be a successful leader

Page 31: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-31

Contingency Theories of Leadership • Set of leadership theories which state that the

situation is most critical for identifying leadership success

Page 32: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-32

Contingency Theories of Leadership Leader-Member Relations: The degree of mutual trust,

respect and confidence between the leader and the subordinates.

Task Structure: The extent to which group tasks are clear and structured.

Leader Position Power: The power inherent in the leader's position itself.

Source:http://en.wikipedia.org/wiki/Fiedler_contingency_model

Page 33: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-33

Situational Leadership Model (SLM)

• http://en.wikipedia.org/wiki/Situational_leadership_theory

Page 34: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-34

Five Essential Practices To Effective Leadership

1. Challenging the process – Search for opportunities for change

2. Inspiring a shared vision – envision the future and others see the same future

3. Enabling others to act – Cultivate collaboration and build spirited teams

4. Modeling the way – Create standards of excellence and set an example

5. Encouraging the heart – Recognize the contribution of others

Page 35: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-35

Power

• Absolute capacity of a person to influence the behavior or attitudes of one or more target persons at a given point in time

• Ability to force people to do something they would not normally do

• http://www.mindtools.com/pages/article/newLDR_56.htm

• http://www.mindtools.com/pages/article/newLDR_04.htm

Page 36: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-36

Positional Power & Types• Power derived from an individual’s position in an

organization

• Types: Legitimate Power – Influencing people based on

being in a position of authority. Reward Power – Influencing people based on being

in a position to distribute rewards. Coercive Power – Influencing people based on

being in a position to punish. Information Power – Influencing people based on

their dependency on controlled information. Ecological Power – Influencing people based on

controlling physical resources like equipment and space.

Page 37: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-37

Personal Power & Types• Outcome of an individual’s unique

characteristics

• Types:

– Expert power – Influencing people based on having expertise, special skills, or knowledge (e.g., financial guru Warren Buffett)

– Referent power – Influencing people based on their strong affection, admiration, or loyalty (e.g., former US Secretary of State Colin Powel)

– Charismatic power – Influencing people based on having a favorable personality and interpersonal style (e.g., entertainment mogul Oprah Winfrey)

Page 38: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-38

Conflict & Types• Opposition of people in an organization from

incompatible or opposing needs, drives, wishes, external or internal demands

• Types:– Functional: Conflict that supports the goals of the

team and improves its performance• Low to moderate levels of Task or Process conflict can

increase a team’s performance

– Dysfunctional: Conflict that hinders group performance and is destructive to team performance

• Relationship conflict or high levels of Task or Process conflict will hinder a team’s performance

Page 39: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-39

Primary Causes of Conflict• Schedule – disagreements on task duration and sequencing

• Project priorities – disagreements on project vision and scope

• Manpower – disagreement on the utilization of people, especially those simultaneously involved in multiple projects

• Technical – disagreements over system design elegance and resource limitations

• Administration – disagreements due to authority over key resources

• Personality – disagreements due to dysfunctional interpersonal interactions

• Cost – disagreements rising from increasing resource constraints as a project evolves

Page 40: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-40

Conflict and Team Performance

Page 41: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-41

Project Conflict ConditionsCondition Description

Ambiguous roles, work boundaries, responsibility, and authority

Project teams often have members with different reporting structures, overlapping or conflicting responsibilities that can lead to conflict.

Inconsistent or incompatible goals Team members may perceive others to have different or conflicting goals that can lead to conflict.

Communication problems Task, process, or relationship ambiguity can result in reduced or ineffective communication that can lead to conflict.

Dependence on another party Team members depend on others to complete tasks or provide resources; delays or work quality issues can lead to conflict.

Specialization or differentiation Team members from different professional backgrounds often have different viewpoints, languages, and goals that can lead to conflict.

Need for joint decision making and consensus

Teams with a diverse mix of members may feel pressure to conform to the majority opinion, which can lead to conflict.

Behavior regulations Project teams have norms for working together that may conflict with an individual’s preferred work processes.

Unresolved prior conflicts Past unresolved issues between team members can lead to conflict.

Page 42: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-42

Conflict Intensity Range

Page 43: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-43

Conflict Resolution Techniques Conflict Resolution Techniques

Problem solving Face-to-face meetings can be used to identify and resolve conflicts through open and candid discussions.

Shared goals Create shared goals that can only be achieved through the cooperation of the conflicting parties.

Resource expansion When conflict is caused by resource scarcity – say, money, opportunities, space, equipment – additional resources can be used to resolve discrepancies.

Avoidance Withdrawal from, or suppression of, the conflict.

Smoothing Playing down differences while emphasizing common interests between the conflicting parties.

Compromise Each party to the conflict gives up something of value.

Authoritative command A person of power mandates an outcome and communicates it to the conflicting parties.

Altering team member behavior Use some type of training or intervention to alter the attitudes or behaviors that are causing conflict.

Altering the team structure Change the formal team structure so that conflicting members limit their interaction; a more extreme solution is to remove members from the team.

Page 44: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-44

Important Political Skills

• Understand what your organization values

• Understand how decisions are made in your organization

• Expand and strengthen your network

• Develop a clear and easy to communicate story

• Lead by example

Page 45: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-45

Global Project Teams

• Increased in popularity due to:

– Advances in telecommunications

– Increased globalization

– Increased outsourcing

Page 46: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-46

Why Outsource?

• Reduce or control costs

• Free up internal resources

• Gain access to world-class capabilities

• Increase revenue potential of the organization

• Reduce time to market

• Increase process efficiencies

• Outsource non-core activities

• Compensate for a lack of specific capabilities or skills

Page 47: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-47

Global Project Team Management Challenges

Page 48: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-48

Culture

• Collective programming of the mind that distinguishes the members of one group or category of people from another

Page 49: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-49

Cultures Vary By:• Power distance: describes how different

societies handle human inequality issues

• Uncertainty avoidance: level of risk taking common to a culture

• Individualism/collectivism: reflects the extent to which a society values the position of an individual versus the position of a group

• Masculinity/femininity: degree to which a society is characterized by masculine or feminine qualities

• Concept of time: extent to which a culture has a longer- or shorter-term orientation

Page 50: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-50

Cultures Vary By (cont)

http://www.mindtools.com/pages/article/newLDR_66.htm

http://geert-hofstede.com/turkey.htmll

Page 51: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-51

Other Possible Barriers

• Language – e.g., communication language and norms

• Work culture – e.g., work skills, habits, and attitudes toward work

• Aesthetics – e.g., art, music, and culture

• Education – e.g., attitudes toward education and literacy

• Religion, beliefs, and attitudes – e.g., spiritual institutions and values

• Social organizations – e.g., family and social cohesiveness

• Political life – e.g., political stability

Page 52: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-52

Environmental & ExpertiseRelated Challenges

• Different skill sets

• Different personnel costs

• Data collection and flow restrictions

• Legal policies

• Currency fluctuations

Page 53: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-53

Global Project Team Development Strategies

Page 54: © 2008 Prentice Hall3-1 Introduction to Project Management Chapter 3 Managing Project Teams Information Systems Project Management: A Process and Team

© 2008 Prentice Hall 3-54

Questions?