Managing Project Teams – Chapter 11 Study Notes

Learning Objectives

• 11-01 Identify key characteristics of a high-performance project team.
• 11-02 Distinguish the different stages of team development (Tuckman model).
• 11-03 Explain how situational factors influence team development and performance.
• 11-04 Outline strategies for deliberately creating high-performance project teams.
• 11-05 Differentiate functional vs. dysfunctional conflict; list tactics for maximizing the former and minimizing the latter.
• 11-06 Identify the unique challenges of virtual project teams and best-practice counter-measures.
• 11-07 Recognize common pitfalls (e.g., groupthink, bureaucratic bypass) that erode project-team effectiveness.

Chapter Outline

• 11.1 Five-Stage Team Development Model
• 11.2 Situational Factors Affecting Team Development
• 11.3 Building High-Performance Project Teams
• 11.4 Managing Virtual Project Teams
• 11.5 Project Team Pitfalls

High-Performing Teams & Synergy

• Synergy concept:
  • Positive synergy → combined output exceeds additive sum: $1+1+1+1+1 = 10$ (metaphor: “team magic”).
  • Negative synergy → combined output lower than additive sum: $1+1+1+1+1 = 2$ (metaphor: “team drag”).
• Eight core characteristics of high-performing teams:
  1. Shared, compelling purpose understood by all.
  2. Optimal use of each member’s skills, knowledge and experience.
  3. Balanced roles; tasks shared rather than siloed.
  4. High energy toward proactive problem-solving (not blame-shifting).
  5. Open acceptance of differing opinions; psychological safety.
  6. Encouragement of calculated risk-taking & creativity.
  7. High personal performance standards (intrinsic & peer driven).
  8. Environment that supports both professional and personal growth.

Five-Stage Team Development Model (Tuckman Ladder)

• Stage 1 – Forming
  • Project activity: orientation, clarifying scope, roles, ground rules.
  • Process: dependence on leader; polite interactions; testing boundaries.
• Stage 2 – Storming
  • Emotional push-back against constraints; intragroup conflict, power struggles.
  • Healthy disagreement surfaces hidden expectations.
• Stage 3 – Norming
  • Cohesion develops; functional roles emerge; open information exchange.
  • Team norms solidify around decision-making & communication.
• Stage 4 – Performing
  • Synergy phase; solution emergence; high autonomy; constructive dissent.
• Stage 5 – Adjourning
  • Group dissolution, hand-offs, celebration, lessons-learned capture.

Situational Factors that Favor High-Performance Teams

• ≤10 people per team (optimizes communication complexity $\frac{n(n-1)}{2}$).
• Voluntary membership → intrinsic motivation.
• Members stay for the project’s full life cycle; reduces churn costs.
• Full-time assignment; minimizes multitasking drag.
• Organizational culture of cooperation & trust.
• Exclusive reporting line to the project manager; clear authority.
• Cross-functional representation of all relevant specialties.
• Compelling, visible objective (strategic relevance).
• Physical proximity: conversational distance (or high-bandwidth virtual equivalent).

Building High-Performance Project Teams

• Key managerial levers (Fig 11.3):
  • Recruit the right members.
  • Conduct purposeful meetings.
  • Establish team identity & shared vision.
  • Design reward systems that reinforce collective outcomes.
  • Facilitate sound decision-making.
  • Proactively manage conflict.
  • Periodically rejuvenate the team’s energy.

Recruiting Project Members

• Selection influenced by project importance & chosen org structure (functional, matrix, projectized).
• Competency criteria:
  • Problem-solving ability (systems thinking, creativity).
  • Availability/level of commitment.
  • Technical expertise depth & breadth.
  • Credibility inside & outside the organization.
  • Political connections – ability to negotiate resources.
  • Ambition, initiative, energy – drives momentum.
  • Familiarity with technology, domain, or stakeholders.

Conducting Project Meetings

• Kick-off meeting: sets tone, clarifies charter, roles, success criteria, communication plan.
• Establishing ground rules: punctuality, participation, decision documentation.
• Decision types:
  • Planning (scope, WBS, schedule, budget).
  • Tracking (status reviews, variance analyses).
  • Change (scope creep, re-baseline decisions).
  • Relationship (conflict resolution; stakeholder alignment).
• Subsequent meetings: keep short, agenda-driven, action-item focused.

Establishing Team Norms

• Confidentiality: information stays internal unless unanimously agreed.
• "No-surprise" rule: raise slippage early; mitigates late-project panics.
• Zero tolerance for bullying; fosters psychological safety.
• "Agree to disagree, then commit": once decision made, united front.
• Respect outsiders; avoid flaunting special status.
• Fun encouraged alongside hard work (boosts morale, creativity).

Establishing Team Identity & Vision

• Practical mechanisms:
  • Frequent & effective meetings.
  • Co-location or virtual-space equivalence (digital war room).
  • Catchy project name, logo, or mascot.
  • Early joint build or deliverable to create shared success memory.
  • Rituals (e.g., Friday demo, stand-up shout-outs).
• Vision requirements (Fig 11.4):
  • Communicates strategic sense (why it matters to organization).
  • Conveys passion (emotional hook).
  • Inspires others (internal & external stakeholders).

Managing Project Reward Systems

• Rewards should motivate collective performance & discretionary effort.
• Group rewards often preferred to prevent sub-optimization.
• Increase value via lasting significance: plaques, visibility, career impact.
• Negative reinforcement (penalties) sometimes necessary but used cautiously.
• Legitimate cases for individual rewards: exceptional heroics or specialized breakthroughs.
  • Examples: personalized letters, public recognition, desirable job assignments, schedule flexibility.

Facilitating Decision-Making Process

1. Identify the real problem (root cause analysis, stakeholder mapping).
2. Generate alternatives (brainstorming, nominal group technique).
3. Reach a decision (consensus, majority, expert authority, multi-criteria scoring).
4. Follow-up: document rationale, assign owners, set review points.

Managing Conflict

• Functional conflict:
  • Opposing views resolved constructively; produces deeper understanding and better solutions.
  • Encourage by assigning a devil’s advocate or structured "why-not" sessions (e.g., 15-minute negative brainstorm).
• Dysfunctional conflict:
  • Unresolved differences impede cooperation; erodes trust & progress.
  • Five managerial responses (escalating directness):
    • Mediate – facilitate dialogue.
    • Arbitrate – impose a decision after listening.
    • Control – set ground rules, separate parties.
    • Accept – allow time for natural cooling if low impact.
    • Eliminate – reassign or remove individuals when necessary.
• Conflict hot-spots over life cycle (Fig 11.5):
  • Defining: priorities, procedures.
  • Planning: priorities, schedules, technical approaches.
  • Executing: schedule, workforce allocation, technical issues.
  • Delivery/closing: schedules, procedures, hand-off clarity.

Rejuvenating the Team

• Informal techniques:
  • New rituals (e.g., milestone celebrations).
  • Inspirational video or success story.
  • Sponsor pep-talk linking work to strategy.
• Formal techniques:
  • External facilitator for team-building workshop (clarify roles, surface hidden issues).
  • Outdoor adventure/team challenge to accelerate bonding through intense shared experience.

Managing Virtual Project Teams

• Challenge 1: Building Trust
  • Hold initial in-person or high-fidelity video kick-off to exchange social cues.
  • Clarify roles, responsibilities, and deliverables early.
  • Whenever possible, staff with members who have prior positive history together.
• Challenge 2: Developing Effective Communication Patterns
  • Prevent "virtual disappearance"—schedule regular check-ins.
  • Establish code of conduct & explicit protocols (response time, platform etiquette).
  • Provide safe paths for surfacing assumptions & conflict (e.g., anonymous retro board).
  • Use video or screen-share tools to verify work & encourage presence.
  • "Share the pain": rotate time-zone inconvenience to distribute burden fairly.

Best Practices for Result-Only Work Environment (ROWE)

• Clear, measurable goals aligned to project vision.
• Transparent communication (dashboards, Kanban boards, Slack channels).
• Appropriate collaboration tools (version-control, shared repositories).
• Regular feedback loops (retrospectives, one-on-ones).

24-Hour Global Clock (Fig 11.6)

• Illustrates overlapping prime, secondary, and downtime windows for U.S. East Coast, Scotland, and Australia.
• Highlights:
  • Three-way prime conferencing window ≈ $12\text{ noon} – 2\text{ PM}$ U.S. / $5\text{ PM} – 7\text{ PM}$ Scotland / $2\text{ AM} – 4\text{ AM}$ Australia.
  • Hand-off points scheduled at end of each region’s workday to enable 24-hr progress.
  • Use color-coding (prime, secondary, downtime) to plan stand-ups, reviews, & escalation paths.

Project Team Pitfalls

• Groupthink
  • Illusion of invulnerability → reckless risk-taking.
  • Suppression/whitewash of critical thinking.
  • Negative stereotypes of outsiders (“they don’t understand”).
  • Direct pressure on dissenters → self-censorship.
• Bureaucratic Bypass Syndrome
  • Team circumvents parent-org protocols; speeds action short-term, jeopardizes legitimacy long-term.
• Team Spirit → Team Infatuation
  • Excessive inward focus; loses touch with broader organization & stakeholders.

Key Terms

• Brainstorming
• Dysfunctional conflict
• Functional conflict
• Groupthink
• Nominal Group Technique (NGT)
• Positive synergy
• Project kick-off meeting
• Project vision
• Team building
• Virtual project team