🏆 PMP Team Managing
Complete Exam Preparation — Domain 1: People | In-Depth Study Guide with Examples, Scenarios & Exam Tips
📌 01 · Overview & Big Picture
Team Managing is the largest domain in the PMP exam — Domain 1 (People) accounts for 42% of all exam questions. It covers everything a project manager does to build, lead, and sustain a high-performing project team.
Why It Matters
Projects are delivered by people. A PM's primary job is not just planning tasks — it's Emotional Intelligence, influencing without authority, resolving conflict, and creating the environment where teams can thrive.
Key PMBOK Processes (6th Ed.)
| Process | Process Group | Purpose |
|---|---|---|
| Plan Resource Management | Planning | Define how to acquire, manage & release team |
| Estimate Activity Resources | Planning | Estimate type/quantity of resources |
| Acquire Resources | Executing | Obtain team members & physical resources |
| Develop Team | Executing | Improve competencies, team interaction, environment |
| Manage Team | Executing | Track performance, provide feedback, resolve issues |
| Control Resources | Monitoring & Controlling | Ensure resources are available as planned |
PMP exam uses an agile/hybrid lens. Know PMBOK processes AND agile practices (Scrum, Kanban, servant leadership). Expect situational questions blending both.
PMI's Talent Triangle — Relevant Areas
- Leadership — motivating, coaching, conflict resolution
- Ways of Working — predictive vs agile team structures
- Business Acumen — understanding why team decisions affect business value
🌱 02 · Develop Team
Develop Team (Executing) = improve team competency, interaction, and the overall environment to enhance project performance. The PM invests in people to boost output quality, reduce turnover, and build morale.
Tools & Techniques
- Colocation — placing team members in same physical location ("war room")
- Virtual Teams — remote collaboration using technology
- Training — classroom, online, coaching, mentoring
- Team Building Activities — social events, retreats, games
- Recognition and Rewards — formal & informal appreciation
- Ground Rules — clear behavioral expectations
- Personnel Assessment Tools — MBTI, DISC, 360° reviews
A PM notices that two engineers avoid collaborating. She schedules a team lunch, creates pair programming tasks, and implements a daily stand-up. Team cohesion improves over two sprints.
Tuckman's Team Development Model
| Stage | Behavior | PM Action |
|---|---|---|
| 🟡 Forming | Polite, unclear roles, excitement/anxiety | Directive — set goals, clarify roles |
| 🔴 Storming | Conflict, jockeying for position, resistance | Coach — facilitate, resolve conflict |
| 🔵 Norming | Cohesion, shared norms, trust builds | Supportive — encourage, step back |
| 🟢 Performing | High output, self-directed, peak performance | Delegate — empower the team |
| ⚪ Adjourning | Project closing, team disbands, reflection | Celebrate — lessons learned, recognition |
Tuckman is HEAVILY tested. A new team member joining mid-project sends the team BACK to Forming. A conflict that breaks out means you're in Storming — coach and facilitate, don't avoid.
Your team was performing well (Performing stage). A senior developer leaves and a junior joins. The team starts missing deadlines and tensions rise. — Answer: Team regressed to Storming. PM should coach, clarify roles, and facilitate conflict resolution.
Team Charter
A Team Charter is a document that establishes team values, agreements, and operating guidelines. It is created BY the team, FOR the team — not by the PM alone.
- Communication expectations (response time, channels)
- Decision-making authority
- Meeting norms (frequency, agenda)
- Conflict resolution approach
- Working hours, availability
The Team Charter is NOT the same as the Project Charter. Project Charter authorizes the project. Team Charter governs how the team works together. On agile projects, the team often creates a working agreement instead.
🎯 03 · Manage Team
Manage Team (Executing) = track team member performance, provide feedback, resolve issues, and coordinate changes to optimize project performance.
Key Activities
- Observe and monitor work behaviors
- Conduct performance appraisals
- Manage conflict proactively
- Update Issue Log
- Use interpersonal skills — emotional intelligence, influencing, decision-making
Performance Appraisal
Evaluates team member contributions, skills, and effectiveness. Can be formal (annual review) or informal (project-based feedback). On projects, 360° feedback is common — peers, subordinates, and supervisors all provide input.
PMP favors timely, specific, constructive feedback. If a team member is underperforming: First, have a private conversation. Then coach. Then escalate if needed — never go to HR as the FIRST step.
Jake, a developer, consistently submits code late. The PM first meets with Jake privately to understand root causes (personal issues? skill gap? unclear requirements?). Together, they create a performance improvement plan. The PM provides weekly check-ins. Performance improves within 3 weeks.
Issue Log
A document that records and tracks all issues — including team-related problems (conflicts, skill gaps, behavior issues). Each entry includes: issue description, owner, priority, and resolution date.
Issue Log ≠ Risk Register. Risks are uncertain future events. Issues have ALREADY occurred. Manage them — don't ignore them.
Inputs to Manage Team
| Input | Why It Matters |
|---|---|
| Project Management Plan | Resource management plan defines how team is managed |
| Work Performance Reports | Shows how team is performing vs. plan |
| Team Performance Assessments | Output of Develop Team — identifies improvements |
| Issue Log | Documents and tracks problems |
| Lessons Learned Register | Historical knowledge to avoid repeating mistakes |
👑 04 · Leadership Styles
A PM must adapt their leadership style to the situation, the individual, and the project phase. PMP values Servant Leadership most highly — especially in agile contexts.
Situational Leadership (Hersey & Blanchard)
Leadership style should match the team member's development level = Competence + Commitment.
| Development Level | Description | Leadership Style |
|---|---|---|
| D1 — Enthusiastic Beginner | Low competence, high commitment | S1 — Directing (tell what/how) |
| D2 — Disillusioned Learner | Low–moderate competence, low commitment | S2 — Coaching (explain why, support) |
| D3 — Capable but Cautious | Moderate–high competence, variable commitment | S3 — Supporting (encourage, listen) |
| D4 — Self-Reliant Achiever | High competence, high commitment | S4 — Delegating (empower fully) |
If a new hire is eager but inexperienced → DIRECT. If a senior expert seems unmotivated → SUPPORT (find out why). If someone just joined from another field → COACH. Match style to person, not to role title.
A veteran engineer says "I know how to do this, just let me work." — Answer: Use Delegating (S4). She is high competence + high commitment. Micromanaging her will demotivate.
Servant Leadership
The PM serves the team — removes obstacles, provides resources, shields from distractions. Core behaviors:
- Listening — deeply understanding team needs
- Empathy — understanding others' perspectives
- Healing — helping team overcome setbacks
- Awareness — self-awareness & situational awareness
- Persuasion — influencing rather than commanding
- Stewardship — acting as caretaker of team & stakeholders
In agile, the Scrum Master is the quintessential servant leader. On the PMP exam, if a question asks what a PM should do when team has a blocker — answer is REMOVE the obstacle (servant leadership), not escalate or delegate the problem away.
Other Leadership Styles
| Style | Characteristics | When Best Used |
|---|---|---|
| Autocratic / Directing | PM makes all decisions; high control | Crisis, new team, tight deadline |
| Democratic / Consultative | Team input; PM decides | Complex decisions, experienced team |
| Laissez-Faire / Delegating | Full team autonomy | Expert team, creative work |
| Transformational | Inspire vision, lead change | Innovation, culture change |
| Transactional | Rewards & penalties; management by exception | Repetitive work, clear metrics |
| Charismatic | Personal magnetism; high energy | Motivating; risky if over-relied upon |
| Interactional | Mix of transformational + transactional | Balanced environments |
💡 05 · Motivation Theories
Maslow's Hierarchy of Needs
People are motivated by unmet needs, moving upward through levels:
| Level | Need | Project Example |
|---|---|---|
| 5 — Top | Self-Actualization | Challenging projects, growth opportunities |
| 4 | Esteem | Recognition, title, respect from peers |
| 3 | Social / Belonging | Team belonging, friendships at work |
| 2 | Safety | Job security, safe working conditions |
| 1 — Base | Physiological | Salary, office space, basic resources |
Lower-level needs must be met first. If team members fear layoffs (Safety), recognition (Esteem) won't motivate them. Address the base need first.
Herzberg's Two-Factor Theory
| Hygiene Factors (De-motivators if absent) | Motivators (True drivers of satisfaction) |
|---|---|
| Salary, company policy, supervision quality, working conditions, job security | Achievement, recognition, the work itself, responsibility, advancement, growth |
Hygiene factors prevent dissatisfaction but don't create motivation. Only Motivators create TRUE satisfaction. Raising salary alone won't make a team member love their job — giving them meaningful, challenging work will.
McGregor's Theory X and Theory Y
| Theory X | Theory Y |
|---|---|
| People dislike work; must be coerced | People enjoy work; self-directed |
| Requires close supervision | Seek responsibility; creative |
| Autocratic management style | Democratic / participative style |
PMP and PMI favor Theory Y thinking. Agile is built on Theory Y assumptions. If a question asks "what should a PM believe about team members?" — Theory Y is almost always the right PMP answer.
McClelland's Theory of Needs
| Need | Behavior | Best Suited For |
|---|---|---|
| Achievement (nAch) | Wants challenging tasks, personal accomplishment | Individual expert roles |
| Affiliation (nAff) | Values relationships, collaboration, acceptance | Team roles, customer-facing work |
| Power (nPow) | Wants influence, leadership, control | Leadership roles, management tracks |
Maria constantly volunteers for the hardest problems and sets high personal standards → nAch dominant. Assign her to complex, independent tasks. Don't put her on repetitive maintenance work.
Expectancy Theory (Vroom)
Motivation = Expectancy × Instrumentality × Valence
- Expectancy: Effort → Performance (Can I do it?)
- Instrumentality: Performance → Reward (Will I get rewarded?)
- Valence: Value of the reward (Do I care about this reward?)
A team member is not motivated even with a bonus offered. Investigation reveals: He doesn't believe the bonus will actually be paid (low Instrumentality) and he doesn't value money as much as flexible hours (low Valence). Solution: Change the reward to time off and demonstrate past bonus payments.
⚔️ 06 · Conflict Management
Conflict on projects is normal and inevitable. PMI says conflict can be BENEFICIAL when managed correctly — it can lead to creative solutions and stronger team bonds.
Sources of Conflict (in order of frequency on projects)
- Schedules — most common source
- Project priorities
- Resources (competition for limited resources)
- Technical opinions
- Administrative procedures
- Cost
- Personality clashes — LEAST common
Schedules = #1 source of conflict. Personality = last. This often surprises people — memorize this list!
Thomas-Kilmann Conflict Resolution Modes
| Mode | Approach | Win/Lose | When to Use |
|---|---|---|---|
| ⭐ Collaborate / Problem Solve | Work together for best solution | Win-Win | Best for long-term; PMI PREFERRED |
| Compromise / Reconcile | Both parties give something | Lose-Lose (partial) | Temporary fix; time-limited situations |
| Accommodate / Smooth | Yield to preserve relationship | Lose-Win | When issue is minor; relationship matters |
| Force / Direct | Use authority to decide | Win-Lose | Crisis or safety; last resort with peers |
| Withdraw / Avoid | Retreat, postpone, ignore | Lose-Lose | Rarely recommended; cooling-off only |
PMI's PREFERRED conflict mode = Collaborate/Problem Solve (confronting). It addresses root causes. Withdrawal is the WORST. For the exam, if no perfect answer exists, pick Collaborate first. If you see "temporary" solution in the question, Compromise may be acceptable.
Conflict Scenarios
Two team members disagree on the technical approach to building an API. They are both senior engineers. → PM should facilitate a collaborative discussion, allow both to present their approaches with pros/cons, and reach a consensus. Do NOT just pick one person's approach (Force) or tell them to figure it out themselves (Withdraw).
A team conflict is escalating and harming sprint velocity. The PM has tried collaborative discussion twice with no result. → Now Force is appropriate — PM makes a decision to move the project forward.
The sponsor wants a feature that the lead developer strongly opposes. The PM needs the sponsor happy AND team cohesion. → Compromise — both parties give ground. A reduced feature set is delivered with agreed-upon constraints.
📡 07 · Communication in Teams
A PM spends ~90% of their time communicating. Effective communication is the backbone of team management.
Communication Channels Formula
Channels = N × (N−1) / 2
Where N = number of stakeholders/team members.
Team of 10 people: 10 × 9 / 2 = 45 communication channels. Adding 2 more: 12 × 11 / 2 = 66 channels. Adding 2 people added 21 NEW channels — complexity explodes!
This formula appears frequently on the PMP exam. Memorize it. Also remember: more people = exponentially more complexity, which is WHY small agile teams (5–9) are optimal.
Communication Models
| Model | Description |
|---|---|
| Basic (Shannon-Weaver) | Sender → Message → Channel → Receiver. Noise can distort. |
| Interactive | Bidirectional: feedback loops between sender and receiver |
| Transactional | Both parties send and receive simultaneously; most realistic |
5 elements of communication: Sender, Message, Medium/Channel, Receiver, Feedback
Noise = anything that distorts the message (cultural differences, language barriers, emotional state, technical jargon)
Communication Dimensions
- Formal vs Informal — reports vs hallway conversation
- Vertical vs Horizontal — up/down the hierarchy vs peer-to-peer
- Official vs Unofficial — signed documents vs rumors
- Written vs Oral — email/reports vs meetings/calls
- Verbal vs Non-verbal — words vs body language (55% of communication!)
Active Listening
Active Listening is more than hearing words — it's fully understanding meaning, intent, and emotion.
- Maintain eye contact
- Paraphrase back ("So what I'm hearing is...")
- Ask open-ended questions
- Do NOT interrupt or finish sentences
- Acknowledge emotions ("I can see that's frustrating")
On the exam: when a team member expresses a concern, the FIRST thing a PM should do is LISTEN and acknowledge — not immediately solve the problem or dismiss the concern. Active listening is almost always a correct initial answer.
🌐 08 · Virtual Teams
Teams where members work from different geographic locations, time zones, or organizations. Post-pandemic, this is now the dominant model globally.
Benefits
- Access to global talent pool
- Reduced travel/office costs
- 24-hour productivity across time zones
- Inclusion of people with mobility limitations
Challenges & PM Responses
| Challenge | PM Response |
|---|---|
| Communication delays (async) | Establish response time norms; use collaborative tools |
| Time zone conflicts | Rotate meeting times; record meetings |
| Cultural differences | Cultural awareness training; inclusive norms |
| Isolation / low morale | Virtual team building; regular 1:1 check-ins |
| Technology failures | Backup communication channels; tech support plan |
| Trust issues | Early kickoff meeting (even virtual); shared goals |
Virtual teams require MORE communication planning — not less. The PM must be PROACTIVE: schedule regular touchpoints, use video (not just text), and create a team identity even across distances.
A global team spans Chicago, London, and Singapore. PM establishes: (1) rotating meeting schedule, (2) shared Confluence workspace, (3) a "team channel" for non-work connection, (4) weekly PM 1:1 with each member. Engagement scores rise 30% over 2 months.
🧠 09 · Emotional Intelligence (EI)
Emotional Intelligence is the ability to understand and manage your own emotions, and to empathize with others. Daniel Goleman identified 5 components:
| Component | Definition | PM Application |
|---|---|---|
| Self-Awareness | Know your emotions & how they affect others | PM stays calm under pressure |
| Self-Regulation | Control impulses; think before acting | PM doesn't react angrily to bad news |
| Motivation | Internal drive; optimism in setbacks | PM inspires team during schedule crisis |
| Empathy | Understand others' feelings & perspectives | PM recognizes team burnout early |
| Social Skills | Manage relationships, build networks | PM navigates stakeholder politics |
PMP exam consistently tests EI. When a team member is upset or resistant — EMPATHIZE first, then problem-solve. Never dismiss emotions or immediately go to command-and-control.
A key developer stormed out of a sprint review after criticism of his code. → PM should: (1) Give him time to cool down. (2) Meet privately — listen, acknowledge his feelings. (3) Understand the root cause. (4) Work together on next steps. Do NOT: ignore it, talk to the team about it, or write him up immediately.
📋 10 · Responsibility Assignment Tools
RAM — Responsibility Assignment Matrix
A RAM maps project roles to work packages or activities. The most common form is the RACI chart.
RACI Chart
| Letter | Meaning | Count Per Task |
|---|---|---|
| R — Responsible | Does the actual work | 1 or more |
| A — Accountable | Owns the outcome; approves deliverable | Exactly 1 |
| C — Consulted | Provides input; two-way communication | 0 or more |
| I — Informed | Kept updated; one-way communication | 0 or more |
CRITICAL: Each task must have EXACTLY ONE "A" (Accountable). If multiple people are accountable, nobody is truly accountable. If NO one is accountable, the task will fall through the cracks.
Task: "Write Test Cases" — Developer: R, QA Lead: A, BA: C, PM: I. The QA Lead owns the outcome. Developer does the work. BA is consulted for business context. PM is just kept informed.
RACI vs. RAM
RAM is the broader concept (can include RACI, RASCI, or other formats). RACI is the most common format. On the exam, RAM = RACI in most contexts.
🔄 11 · Agile Team Management
Agile team management is fundamentally different from predictive. Power is distributed, teams are self-organizing, and the PM becomes a servant leader or facilitator.
Scrum Roles
| Role | Responsibilities |
|---|---|
| Product Owner (PO) | Owns product backlog; prioritizes features; represents customer; defines "done" |
| Scrum Master (SM) | Servant leader; removes impediments; facilitates ceremonies; protects team from distractions |
| Development Team | Self-organizing; cross-functional; delivers working product each sprint; 3–9 members |
On PMP exam: PM ≈ Scrum Master in agile context. The PM's job shifts from commanding to ENABLING. Never "assign" tasks in agile — the team PULLS work from the backlog.
Agile Ceremonies
| Ceremony | Purpose | Frequency | Who Attends |
|---|---|---|---|
| Sprint Planning | Select backlog items for sprint; define sprint goal | Start of each sprint | Whole Scrum team |
| Daily Scrum / Stand-up | Sync: what done, what planned, blockers | Daily (15 min max) | Dev team + SM |
| Sprint Review | Demo working software to stakeholders; get feedback | End of sprint | Whole team + stakeholders |
| Sprint Retrospective | Inspect process; improve team practices | After sprint review | Whole Scrum team |
| Backlog Refinement | Groom/estimate backlog items | Ongoing (mid-sprint) | PO + Dev team |
Sprint Retrospective is a TEAM MANAGEMENT tool — it's where the team discusses working agreements, collaboration improvements, and process fixes. It is NOT for showing the product. That's the Sprint Review.
Self-Organizing Teams
In agile, teams decide how to do the work. The PM does NOT assign tasks — team members self-select based on skills and capacity. The PM creates the conditions for self-organization:
- Clear goal and product backlog
- Cross-functional team composition
- Psychological safety
- Remove impediments promptly
- Trust and transparency
🏅 12 · Recognition & Rewards
Recognition keeps teams motivated, reinforces desired behaviors, and reduces turnover. Effective reward systems should be:
- Timely — given soon after the achievement
- Specific — tied to a clear behavior or outcome
- Fair — applied consistently
- Appropriate — matched to the individual's values (some prefer public, some private)
Formal vs. Informal Recognition
| Formal | Informal |
|---|---|
| Performance bonuses, promotions, awards ceremonies, written commendations | Public "thank you," handwritten note, team lunch, extra day off, shout-out in meeting |
PMI says: do NOT give rewards tied to zero-sum competition (e.g., "top performer of month" when only 1 wins). This destroys teamwork. Use win-win recognition — celebrate team achievements, not just individuals vs. each other.
A team delivers a critical milestone 2 days ahead of schedule. PM: (1) Sends email to sponsor copying team. (2) Buys lunch for the team. (3) Presents a "team excellence" certificate in the sprint review. Cost: minimal. Impact: team morale peaks, retention improves.
🔑 13 · Power, Influence & Politics
PMs often have authority over the project but NOT over team members (especially in matrix organizations). They must lead through influence, not just authority.
Types of Power
| Type | Source | Example | PMI View |
|---|---|---|---|
| Formal / Legitimate | Position/title | "I'm the PM — do this" | OK, but limited |
| Reward | Ability to give rewards | Bonus, recognition, promotion | Good if used fairly |
| Coercive / Penalty | Ability to punish | Negative reviews, termination threats | Last resort |
| Expert | Knowledge/skill | "She knows this domain better than anyone" | ⭐ BEST power type |
| Referent | Admiration/respect | "I follow him because I believe in him" | ⭐ BEST power type |
| Informational | Access to information | PM who controls information flow | Use transparently |
| Situational | Unique circumstances | Crisis expert gaining temporary authority | Contextual |
PMI FAVORS Expert and Referent power. These come from earning respect, not from your title. On the exam: "Which type of power is MOST effective?" → Expert or Referent. "Which is LEAST appropriate?" → Coercive/Penalty.
A PM manages a team where the developers are more technically skilled than she is. She lacks Expert power. What should she do? → Build Referent power by being consistently fair, trustworthy, transparent, and supportive. Earn their respect through character and commitment.
📝 14 · Practice Quiz (Click to Answer)
Q1. A team that was performing well just had a new member join. Shortly after, disagreements and slowdowns occur. What stage is the team in?
A. Performing B. Storming C. Norming D. AdjourningQ2. Which conflict resolution mode does PMI consider MOST effective for lasting resolution?
A. Compromise B. Smoothing C. Collaborate / Problem Solve D. ForceQ3. According to Herzberg, which of the following is a MOTIVATOR (not a hygiene factor)?
A. Salary increase B. Better working conditions C. Recognition for achievement D. Job securityQ4. Your team has 8 members. A new stakeholder joins. How many new communication channels are added?
A. 8 B. 8 new channels (28→36) C. 9 new channels D. 36 channels addedQ5. In a RACI chart, how many people should be "Accountable" for a single task?
A. As many as needed B. At least two for redundancy C. Exactly one D. The PM is always accountableQ6. A senior engineer is highly skilled and self-motivated. What leadership style should the PM use?
A. Directing B. Coaching C. Supporting D. DelegatingQ7. Which type of power does PMI consider MOST effective for project managers?
A. Formal / Legitimate B. Coercive C. Expert and Referent D. RewardQ8. In agile, who is responsible for prioritizing the product backlog?
A. Scrum Master B. Product Owner C. Project Manager D. The development team collectively📄 15 · Ultimate Cheat Sheet
Tuckman Stages
- Forming → Direct
- Storming → Coach
- Norming → Support
- Performing → Delegate
- Adjourning → Celebrate
Conflict Sources (Order)
- Schedules (#1)
- Priorities
- Resources
- Technical
- Admin
- Cost
- Personality (#7 = last)
Conflict Modes
- ⭐ Collaborate = Best
- Compromise = OK temp
- Smooth = minor issues
- Force = crisis/last resort
- Withdraw = Worst
Power Types
- ⭐ Expert = Best
- ⭐ Referent = Best
- Reward = Good
- Formal = Limited
- Coercive = Worst
Maslow (Bottom→Top)
- Physiological
- Safety
- Social
- Esteem
- Self-Actualization
Herzberg
- Hygiene = prevents dissatisfaction
- Motivators = creates satisfaction
- Salary = HYGIENE (not motivator)
- Achievement = MOTIVATOR
McGregor
- X = people dislike work; control
- Y = people enjoy work; empower
- PMI favors Theory Y
Communication Formula
Channels = N(N−1)/2
10 people = 45 channels
Adding 1 = N−1 new channels
RACI Rules
- A = exactly 1 per task
- R = 1 or more
- C = 2-way communication
- I = 1-way communication
Scrum Roles
- PO = backlog priority
- SM = servant leader
- Dev Team = self-organizing
- Team size: 3–9 members
EI Components (Goleman)
- Self-Awareness
- Self-Regulation
- Motivation
- Empathy
- Social Skills
Situational Leadership
- D1 = Directing
- D2 = Coaching
- D3 = Supporting
- D4 = Delegating
🔤 16 · Keywords Glossary
Click any keyword throughout this guide to see a quick definition. All keywords are listed below:
Emotional Intelligence
Servant Leadership
Colocation
Virtual Teams
Training
Team Building Activities
Recognition and Rewards
Ground Rules
Personnel Assessment Tools
Team Charter
Performance Appraisal
Issue Log
Active Listening
RAM
Self-Organizing Teams
Psychological Safety
Impediment
Velocity
Definition of Done
Working Agreement
Burnout
Cross-functional Team
Matrix Organization
Influence Without Authority
Tuckman Model
Herzberg Theory
Maslow Hierarchy
Retrospective