1. What is Team Management?

Team management in the PMP context means leading people to achieve project goals on time, within budget, and at the required quality — while creating a positive, motivating environment. The PMP exam (as of 2021 ECO) heavily emphasizes predictive, agile, and hybrid approaches to team management, with nearly 42% of questions from Domain 1 (People).

🔑 Why It Matters on the Exam

  • 42% of PMP exam questions are from Domain 1 (People/Team)
  • PMP now tests the PM as a leader, not just a planner
  • Situational questions demand you pick the best leadership action

Core Responsibilities of a PM as Team Leader

✅ Build the Team

Identify, acquire, and onboard the right people for the right roles at the right time.

✅ Develop the Team

Train, mentor, coach, and grow team member skills throughout the project lifecycle.

✅ Manage the Team

Track performance, resolve conflicts, give feedback, and remove obstacles.

✅ Motivate the Team

Understand what drives each individual and create conditions for peak performance.

On situational questions, the PM almost always acts first — communicate, collaborate, resolve. Never ignore, escalate immediately, or blame team members without trying to solve it first.

2. PMI Talent Triangle

PMI defines the ideal PM through the Talent Triangle. All three sides appear in exam questions.

Ways of Working
Technical & delivery skills: predictive, agile, hybrid methods, tools, frameworks
Power Skills
Collaborative leadership, communication, problem-solving, influencing
Business Acumen
Strategic alignment, benefits realization, financial literacy
Questions about "what should the PM develop to be more effective?" almost always point to Power Skills (formerly Leadership) — the human side of project management.

3. Domain 1: People — Overview

Domain 1 covers 14 tasks across the PMP Exam Content Outline (ECO). These tasks define how a PM leads people.

#TaskKey Concept
1Manage conflictConfronting, collaborating, compromising
2Lead a teamServant leadership, vision, purpose
3Support team performanceFeedback, coaching, mentoring
4Empower team membersDelegation, autonomy, accountability
5Ensure team members are trainedGap analysis, training plans
6Build a teamTeam charter, ground rules, onboarding
7Address & remove impedimentsServant leader removes blockers
8Negotiate project agreementsWin-win, BATNA, principled negotiation
9Collaborate with stakeholdersEngagement, co-creation, transparency
10Build shared understandingKick-off, chartering, alignment
11Engage & support virtual teamsTime zones, culture, tools
12Define team ground rulesNorms, behaviors, team charter
13Mentor relevant stakeholdersKnowledge transfer, coaching
14Promote team performanceRecognition, rewards, high performance

4. Tuckman's Team Development Stages

Tuckman's model is one of the most tested topics in PMP Team questions. Know all five stages, their characteristics, and the PM's role at each stage.

1
Forming
Team meets, polite, unclear roles. PM directs, sets expectations.
2
Storming
Conflict, power struggles, frustration. PM coaches, mediates conflict.
3
Norming
Norms established, trust grows, collaboration improves. PM supports.
4
Performing
High performance, self-directed. PM delegates, removes obstacles.
5
Adjourning
Project ends, team disbands. PM celebrates, documents lessons.

PM Leadership Style by Stage

StageTeam BehaviorPM RoleKey Action
FormingPolite, uncertainDirectorDefine roles & charter
StormingConflict, resistanceCoachMediate, resolve conflict
NormingCooperativeSupporterFacilitate, give feedback
PerformingProductive, autonomousDelegatorRemove impediments
AdjourningWrap-up, emotionalCelebrantLessons learned, recognition
A new team member joins mid-project. The team, previously at Performing, starts having minor conflicts. What stage has the team likely regressed to? Answer: Storming. Adding a new member can restart the cycle. The PM should coach and re-establish norms.
Teams can move BACKWARD through stages when members change, project scope changes, or conflict arises. On the exam, if a high-performing team suddenly has conflicts, the PM should COACH and ADDRESS conflict — not escalate or accept it.

5. Team Charter

A team charter is a document that defines team values, agreements, and operating guidelines. It is co-created by the team — NOT imposed by the PM. This is a key distinction on the exam.

📄 What Goes in a Team Charter?

  • Team values — What the team believes in (respect, honesty, quality)
  • Communication agreements — When and how to communicate
  • Decision-making process — Consensus, majority, or PM decides?
  • Meeting norms — Frequency, duration, punctuality rules
  • Conflict resolution process — How disagreements are handled
  • Working hours & availability — Especially for virtual teams
  • Quality standards — What "done" means
Your team is experiencing frequent miscommunications about deliverable quality. As PM, what should you do? Answer: Work with the team to create or update the team charter with clear quality standards and communication agreements.
Team charter ≠ Project Charter. The Project Charter authorizes the project. The Team Charter governs how the team works together. Always co-create; never dictate.

6. Virtual & Distributed Teams

Virtual teams are groups working across different locations, time zones, and cultures. PMP exam heavily tests how to manage them effectively.

Advantages of Virtual Teams

Challenges & PM Solutions

ChallengePM Solution
Isolation & disconnectionRegular video check-ins, team-building activities
Communication barriersClear norms in team charter, multiple channels
Time zone conflictsRotating meeting times, record sessions
Cultural differencesCultural awareness training, explicit norms
Technology gapsStandardize tools, provide training
Trust issuesFocus on outcomes not hours, face-to-face kickoff

💡 Best Practices for Virtual Teams

  • Start with an in-person or video kickoff meeting
  • Establish a team charter early
  • Use visual collaboration tools (Miro, Jira, Teams)
  • Document everything — don't rely on hallway conversations
  • Recognize contributions publicly and frequently
On the exam, virtual team questions often test: Who creates communication agreements? (The team together). What is the FIRST thing to do? (Usually establish communication norms / team charter).

7. Servant Leadership

Servant leadership is the primary leadership philosophy tested on the PMP exam. In this model, the PM serves the team — not the other way around. The PM's job is to remove obstacles, support team members, and enable them to do their best work.

🌟 Core Servant Leadership Behaviors

  • Remove impediments — Clear the path
  • Empower the team — Give autonomy
  • Listen actively — Hear concerns
  • Show empathy — Understand feelings
  • Facilitate decisions — Not dictate
  • Develop people — Coach & mentor
  • Build community — Foster belonging
  • Put others first — Team before ego

Servant Leader vs. Traditional Manager

Traditional ManagerServant Leader (PMP Style)
Commands and controlsFacilitates and empowers
Makes all decisionsInvolves team in decisions
Focused on their own goalsFocused on team success
Hoards informationShares information freely
Punishes failureCreates safe space to fail & learn
A team member tells you that their current task tools are slowing them down and causing errors. As a servant leader, what do you do? Answer: Work to remove this impediment — find better tools, procure them, and support the team member. Your job is to clear obstacles.
When an exam question asks "what should the PM do FIRST?" and involves a team issue — the servant leader answers usually involve LISTENING, COMMUNICATING, or REMOVING IMPEDIMENTS. Avoid answers that say "ignore it," "punish," or "escalate without trying."

8. Leadership Styles

The PMP exam tests multiple leadership styles and when to use each. Know the situational context for each style.

StyleWhen to UseKey Feature
ServantAlways (preferred in PMP)Remove obstacles, serve team
TransformationalNeed major change/innovationInspire vision, change culture
TransactionalClear deliverables, stable environmentRewards & penalties, KPIs
Laissez-faireExpert team, well-performingHands-off, team is autonomous
Democratic/ParticipativeDecisions need team inputInclusive, consensus-driven
Autocratic/DirectiveCrisis, emergency, new/inexperienced teamPM decides alone, fast action
CoachingTeam needs skill developmentGuide, ask questions, develop
VisionaryNew direction neededArticulate compelling future state
PacesettingHigh standards needed quicklyLead by example, high bar
AffiliativeTeam morale is low, healing neededPeople first, harmony focus

💡 Situational Leadership (Hersey & Blanchard)

Match leadership style to team member's competence + commitment:

  • S1 Directing — Low competence, high enthusiasm (new employee)
  • S2 Coaching — Some competence, lower confidence (struggling learner)
  • S3 Supporting — High competence, variable motivation (experienced but disengaged)
  • S4 Delegating — High competence, high commitment (expert, self-directed)
Transformational leadership is often tested as the CHANGE management style. Transactional is often presented as less effective in the PMP world. Servant leadership is almost always the correct default answer.

9. Emotional Intelligence (EI/EQ)

Emotional Intelligence (EQ) is a PM's ability to recognize, understand, and manage emotions — in themselves and in team members. Daniel Goleman's model is the one tested on PMP.

Self-Awareness
Know your own emotions and how they affect others
Self-Regulation
Control impulses, stay calm under pressure
Motivation
Inner drive, passion for work beyond money
Empathy
Understand others' emotions and perspectives
Social Skills
Manage relationships, build networks, influence

EI in Practice

Self-Awareness Example

PM notices they get defensive during risk discussions. They pause, reflect, and consciously remain open to bad news.

Empathy Example

A team member is quieter than usual. PM checks in privately: "I noticed you seem stressed — is everything okay?" This builds trust.

EI questions often describe a PM dealing with a difficult team member or emotionally charged situation. The correct answer almost always involves EMPATHY (understand first) and ACTIVE LISTENING before taking action.

10. Maslow's Hierarchy of Needs

Maslow's Hierarchy is one of the most-tested motivation theories. People must satisfy lower-level needs before higher ones motivate them.

LevelNeed TypeWorkplace Example
5 — TopSelf-ActualizationCreative work, mastery, meaningful projects
4EsteemRecognition, promotions, titles, respect
3Social / BelongingTeam belonging, friendships, inclusion
2SafetyJob security, safe work environment
1 — BasePhysiologicalSalary, breaks, basic working conditions
A team member is performing poorly. You discover they recently lost their apartment and are struggling financially. According to Maslow, they're stuck at which level? Answer: Level 1-2 (Physiological/Safety). Expecting them to be motivated by meaningful work (Level 5) is unrealistic until basic needs are met. PM should connect them with EAP resources.
On the exam, Maslow questions often test: "Why is recognition NOT working for this employee?" The answer is usually a lower-level need isn't being met first.

11. Herzberg's Two-Factor Theory

Herzberg identified two categories of factors that affect motivation:

❌ Hygiene Factors (Dissatisfiers)

If MISSING → causes dissatisfaction. If present → just prevents dissatisfaction (doesn't motivate).

  • Salary / pay
  • Job security
  • Working conditions
  • Company policies
  • Supervision quality
  • Interpersonal relations

✅ Motivators (Satisfiers)

If present → TRULY motivates. Related to the work itself.

  • Achievement / accomplishment
  • Recognition for work
  • Responsibility
  • Advancement / growth
  • The work itself (interesting)
  • Personal development
KEY DISTINCTION: Salary is a HYGIENE factor — not a motivator! On the exam, if a question says "the team gets a raise but morale is still low," the answer is: pay is a hygiene factor; you need to address motivators (recognition, growth, interesting work).

12. McGregor's Theory X and Theory Y

McGregor proposed that managers have two fundamentally different views of human nature, and these views shape how they manage:

📛 Theory X Manager

  • Believes people are lazy by nature
  • Must be watched, controlled, threatened
  • Avoids responsibility
  • Uses micromanagement
  • Authoritarian style

✅ Theory Y Manager (PMP Preferred)

  • Believes people are self-motivated
  • Seek responsibility naturally
  • Creative problem-solvers
  • Uses empowerment & delegation
  • Participative / servant leader style
PMP exam ALWAYS favors Theory Y behavior. When a question describes a PM micromanaging or threatening the team, that's Theory X — and it's WRONG. Theory Y = trust, empower, delegate = correct PMP answer.

💡 Theory Z (Ouchi)

An extension that adds: long-term employment, collective decision-making, and holistic concern for the employee (work-life balance). Sometimes appears on exam as a third option.

13. McClelland's Theory of Needs

McClelland argued that people are primarily driven by one of three needs — learned over time:

nAch
Need for Achievement
Wants challenging tasks, personal responsibility, feedback on results. Avoids low/high risk. Best as individual contributor or technical expert.
nAff
Need for Affiliation
Wants to belong, be liked, avoid conflict. Strong team player. Avoids competitive situations. Best in collaborative roles.
nPow
Need for Power
Wants influence and control. Two types: Personal (self-gain) or Institutional (team/org success). Best as a leader or manager.
On the exam: high nAch people dislike low-accountability group roles. High nAff people hate competitive or isolating environments. High nPow (institutional) people make great project managers!

14. Vroom's Expectancy Theory

People are motivated when they believe their effort will lead to performance, and performance will lead to a desired reward. The formula:

Motivation = Expectancy × Instrumentality × Valence
ComponentQuestion It AnswersExample
Expectancy (E)Can I do the work?"If I try hard, can I complete this task?"
Instrumentality (I)Will my effort be recognized?"If I complete it, will I get a bonus?"
Valence (V)Do I value the reward?"Do I even care about that bonus?"
A developer is not motivated to work overtime. Investigation reveals they don't believe overtime will lead to a promotion (low Instrumentality) and they wouldn't value the promotion anyway (low Valence). PM should find rewards they actually value and make the path to rewards clear.
Expectancy Theory = the motivation formula. If any one factor is ZERO, motivation = ZERO. Exam questions about "why isn't the bonus working?" often point to low Valence (reward isn't valued by that person).

15. Communication Models

Communication is the PM's most critical skill — the PMBOK says PMs spend 90% of their time communicating. Three models are tested:

Basic Communication Model

Sender → Encode → Message → Channel/Medium → Decode → ReceiverFeedback

  • Encode: Convert thoughts into language/symbols
  • Decode: Receiver interprets the message
  • Noise: Anything that distorts the message (language barriers, distractions, jargon)
  • Feedback: Receiver confirms understanding (closes the loop)

Communication Methods

TypeWhen BestExamples
InteractiveComplex, sensitive, immediate feedback neededMeetings, calls, video conferences
PushLarge audience, one-way informationEmails, memos, reports, newsletters
PullReference material, large volumesIntranet, SharePoint, shared drives
On exam: when to use INTERACTIVE communication? Always for sensitive issues, conflicts, complex topics. Never rely on email alone for sensitive conversations.

16. Communication Channels Formula

The number of potential communication channels grows rapidly as team size increases:

Channels = n(n-1) / 2    where n = number of people
Team Size (n)Channels
2 people1 channel
5 people10 channels
10 people45 channels
15 people105 channels
20 people190 channels
Your team grows from 5 to 10 members. How many NEW channels were added? Answer: 45 − 10 = 35 new channels. This is why large team communication is exponentially complex.
This formula appears directly on the exam! Also: if the question asks "a PM joins a team of 5" → the PM is the 6th person → n=6 → 6(5)/2 = 15 channels. Know the formula cold!

17. Active Listening

Active listening is more than hearing — it's fully engaging with the speaker to understand the complete message, including emotion and intent.

Active Listening Techniques

✅ Do This

  • Maintain eye contact
  • Paraphrase to confirm understanding
  • Ask open-ended questions
  • Note non-verbal cues
  • Avoid interrupting
  • Acknowledge emotions

❌ Avoid This

  • Thinking about your response while they talk
  • Checking your phone/emails
  • Finishing their sentences
  • Dismissing their concerns
  • Jumping to solutions too fast
Active listening exam pattern: Team member raises concern → PM should FIRST listen and acknowledge, THEN investigate or act. Never skip the listening step.

18. Conflict Resolution

Conflict is normal and can be healthy. The PMP exam tests the 5 conflict resolution techniques and when each is appropriate. Confronting/Problem-Solving is almost always the correct PMP answer.

TechniqueAlso CalledWhen to UsePMP Rank
Confront / Problem-SolveCollaborateWin-win, long-term solution, most situations⭐ BEST
CompromiseReconcileBoth parties give a little; temporary solution✅ Good
Smooth / AccommodateYieldPreserve relationship, issue is minor⚠️ Short-term only
Force / DirectWin-loseEmergency, time-critical, authority must decide⚠️ Use with caution
Withdraw / AvoidRetreatCool-down period, gather more info (TEMPORARY)❌ Worst long-term
Two engineers disagree on which technical approach to use. The conflict is slowing the project. What should the PM do? Answer: Confront/Problem-Solve. Bring both parties together, explore root causes, find a technical solution that satisfies both. Don't force, smooth, or avoid.

💡 Sources of Conflict (PMI Priority Order)

  1. Schedule pressures (most common!)
  2. Project priorities
  3. Resource availability
  4. Technical opinions
  5. Administrative procedures
  6. Cost / budget
  7. Personality clashes (least common in PMI's view)
The exam loves to make "smoothing" or "avoiding" look attractive because they seem kind. RESIST. Confront/Problem-Solve is the answer 90% of the time unless the question specifically says "emergency" or "time is critical."

19. Team Performance

Monitoring and improving team performance is an ongoing PM responsibility. Key tools and techniques include:

Team Performance Assessment Tools

📊 Assessments

  • Attitudinal surveys
  • Structured interviews
  • Ability tests
  • Focus groups
  • 360-degree feedback

📈 Performance Indicators

  • Schedule variance (SV)
  • Defect rates / quality metrics
  • Team velocity (agile)
  • Burn-down charts
  • Retention / turnover rates

Feedback Principles

✅ Giving Effective Feedback

  • Timely — As close to the event as possible
  • Specific — Describe exact behavior, not personality
  • Constructive — Focus on improvement, not criticism
  • Private — Negative feedback ALWAYS in private
  • Balanced — Include positives with areas for improvement
  • Forward-looking — What will change, not just what went wrong
PMP exam rule: Praise publicly, criticize privately. If a question shows a PM calling out an employee's mistake in a team meeting — that's WRONG behavior.

20. Recognition & Rewards

Recognition and rewards are part of the Develop Team process. Effective recognition increases motivation, loyalty, and performance.

Types of Rewards

TypeExamplesEffectiveness
MonetaryBonuses, raises, gift cardsShort-term motivator (hygiene factor)
Non-monetaryPublic praise, certificates, extra PTOOften more powerful long-term
Team-basedTeam celebrations, group recognitionBuilds camaraderie
DevelopmentTraining, stretch assignments, promotionLong-term motivator (Herzberg satisfier)

💡 Key Recognition Principles (PMP)

  • Recognition should be tied to project objectives
  • Individual recognition must consider cultural sensitivities (not everyone wants public spotlight)
  • Win-win rewards are preferred over zero-sum (individual vs. team)
  • Intrinsic rewards (growth, mastery) outlast extrinsic (money)
Never reward ONLY individual performance if it undermines team collaboration. On the exam, team-based rewards that align with project goals are usually the better answer.

21. Agile Team Roles

The PMP exam includes agile team management heavily. Know the three Scrum roles (in Scrum the preferred term is "accountabilities"):

Product Owner
(PO)
Owns the Product Backlog. Prioritizes features. Represents business/customer. Defines what gets built and why.
Scrum Master
(SM)
Servant leader for the team. Removes impediments. Facilitates ceremonies. Coaches agile practices. Not the boss!
Dev Team
(Developers)
Cross-functional, self-organizing. 3-9 people ideal. Decides HOW to build. Commits to sprint goals. No sub-teams.

Key Scrum Ceremonies

CeremonyPurposeWho AttendsFrequency
Sprint PlanningSelect backlog items for sprintFull Scrum TeamStart of each sprint
Daily Scrum / Standup15-min sync on progress & blockersDev Team (SM optional)Daily
Sprint ReviewDemo working product to stakeholdersAll + stakeholdersEnd of sprint
Sprint RetrospectiveInspect & improve team processScrum TeamAfter Sprint Review
Backlog RefinementClarify/estimate upcoming itemsPO + Dev TeamAs needed (mid-sprint)
Scrum Master ≠ Project Manager. The SM removes impediments and facilitates — they do NOT assign tasks or make scope decisions. The PO owns the backlog and priorities. The team commits to the sprint.

22. Self-Organizing Teams

Self-organizing teams are a hallmark of agile. They decide internally how to accomplish work — without being directed by a manager. This is intentional and tied to the Agile Manifesto.

Characteristics of Self-Organizing Teams

✅ PM's Role with Self-Organizing Teams

  • Remove impediments
  • Provide resources and support
  • Protect the team from outside interference
  • Coach and develop (don't direct)
  • Trust the team's judgment on HOW to work
If a PMP exam question shows a PM assigning tasks to an agile team, telling them how to do their work, or overriding their estimates — that is WRONG in agile. Self-organizing = team decides HOW.

23. Retrospectives

A retrospective is the agile ceremony for continuous process improvement. The team reflects on their working process — not the product. It answers three questions:

What went well?
Celebrate successes; reinforce positive behaviors
What didn't go well?
Identify problems without blame; focus on process
What will we improve?
Concrete action items for the next sprint

💡 Retrospective Best Practices

  • Blame-free environment — critique the process, not the person
  • Every voice counts — all team members participate
  • Actionable outcomes — at least 1-2 concrete improvements per retro
  • Follow up — check previous retro action items at the start
  • Prime directive: "Everyone did the best they could with the information they had"
Retrospective = continuous improvement tool = Kaizen principle. If an exam question asks "how does an agile team continuously improve?" → Retrospective. If it asks about product improvement → Sprint Review.

24. Stakeholder Engagement

Stakeholders are individuals or organizations that affect or are affected by the project. Engaging them effectively is a key Domain 1 skill.

Stakeholder Engagement Levels

LevelBehaviorPM Goal
UnawareDoesn't know about the projectInform and create awareness
ResistantOpposes the projectUnderstand concerns, address them
NeutralNeither supportive nor resistantEducate, move toward supportive
SupportiveAware and supportiveMaintain engagement
LeadingActively promotes the projectLeverage as champion!

📊 Stakeholder Engagement Assessment Matrix

The SEAM shows Current (C) vs. Desired (D) engagement levels for each stakeholder. The PM's job is to close the gap between C and D through targeted communication and engagement strategies.

The goal is to move ALL stakeholders to "Supportive" or "Leading." Resistant stakeholders are not enemies — engage them, understand their concerns, and involve them in solutions. Ignoring resistant stakeholders is always WRONG.

25. Power / Interest Grid

The Power/Interest Grid (Mendelow Matrix) maps stakeholders by their power to influence the project and their interest in the project outcome.

QuadrantPowerInterestStrategy
Manage CloselyHighHighMaximum engagement, frequent updates, involve in decisions
Keep SatisfiedHighLowRegular high-level updates; ensure needs are met
Keep InformedLowHighRegular communication; tap their enthusiasm
MonitorLowLowMinimal effort; routine updates only
Your project sponsor (high power, high interest) suddenly becomes disengaged and stops attending steering committee meetings. What should the PM do? Answer: Schedule a one-on-one meeting with the sponsor immediately. Their disengagement is a major risk. Understand the cause and re-engage. A disengaged high-power stakeholder can kill a project.
High power, low interest stakeholders are often the most dangerous if ignored — they can suddenly become resistant. KEEP SATISFIED means proactive, not reactive communication.

26. 📋 Master Cheat Sheet

🏆 Tuckman's Stages → PM Role

Forming=Direct | Storming=Coach | Norming=Support | Performing=Delegate | Adjourning=Celebrate

🏆 Conflict Resolution Best → Worst

Confront/Collaborate ✅ → Compromise ✅ → Smooth ⚠️ → Force ⚠️ → Withdraw ❌

🏆 Motivation Theories Summary

TheoryKey PointExam Trick
Maslow5 needs hierarchy (basic→self-actualization)Meet lower needs FIRST
HerzbergHygiene vs. MotivatorsSalary = hygiene, NOT motivator
McGregorTheory X (control) vs. Y (empower)PMP always = Theory Y
McClellandnAch, nAff, nPownPow (institutional) = good PM
VroomE × I × V = MotivationAny factor = 0 → no motivation

🏆 Communication Formula

Channels = n(n-1)/2  |  PM spends 90% time communicating  |  Interactive > Push > Pull

🏆 Servant Leadership = Always the Best Answer

Remove impediments | Empower team | Listen first | Never micromanage | Facilitate decisions

🏆 Agile Quick Facts

PO owns backlog | SM removes impediments (not boss) | Dev team self-organizes | Retro = process improvement | Review = product demo | Sprint = 1-4 weeks

🏆 Team Charter Must-Knows

Co-created by team (NOT imposed) | Includes values, norms, communication rules, conflict process | Different from Project Charter

🏆 Stakeholder Grid Rules

High Power + High Interest = MANAGE CLOSELY | High Power + Low Interest = KEEP SATISFIED | Never ignore high-power stakeholders

27. Practice Questions (10 Exam-Style)

Q1. Your team has been performing well for months. A new senior developer joins and the team begins arguing about processes. Which stage has the team entered?
Q2. A team member keeps missing deadlines but is technically excellent. You discover they feel their work is meaningless. According to Herzberg, what should you address?
Q3. Two team members have a technical disagreement that is delaying the project. What is the BEST conflict resolution approach?
Q4. Your team of 5 expands by adding 3 new members. How many new communication channels are added?
Q5. A Scrum Master notices a team member is struggling with a new technology. What should the Scrum Master do FIRST?
Q6. A stakeholder has HIGH power but LOW interest in the project. How should the PM engage them?
Q7. You are leading a virtual team across 4 time zones. Team members report feeling disconnected. What is the BEST first step?
Q8. During a retrospective, a team member blames another for the sprint failure. How should the Scrum Master respond?
Q9. A PM gives the team members complete autonomy and doesn't get involved unless asked. The team is expert and highly motivated. This BEST describes which leadership style?
Q10. According to Maslow, a team member's motivation for recognition awards has decreased since they were laid off from their second job. The MOST likely reason is:

28. Key Formulas, Numbers & Facts

Formula / FactValue / Rule
Communication Channelsn(n-1)/2
PM Communication Time~90% of their time
Domain 1 (People) Weight~42% of PMP exam
Ideal Scrum Team Size3–9 developers (+ SM + PO)
Sprint Duration1–4 weeks (fixed iteration)
Tuckman Stages Count5 (Forming–Storming–Norming–Performing–Adjourning)
Herzberg Hygiene ExamplesSalary, working conditions, job security, policies
Herzberg Motivator ExamplesAchievement, recognition, responsibility, growth
Maslow Levels5: Physiological→Safety→Social→Esteem→Self-Actualization
Best Conflict Style (PMP)Confront / Problem-Solve / Collaborate
Worst Conflict StyleWithdraw / Avoid (for persistent conflicts)
EI Components (Goleman)5: Self-Awareness, Self-Regulation, Motivation, Empathy, Social Skills
Vroom FormulaMotivation = E × I × V (Expectancy × Instrumentality × Valence)
McClelland NeedsnAch (achievement), nAff (affiliation), nPow (power)
Stakeholder Engagement Levels5: Unaware→Resistant→Neutral→Supportive→Leading

🏆 You Are PMP Team Management READY!

Master these concepts and you will dominate Domain 1. Trust the servant leadership framework — it's the answer to most situational questions.

Eng. Ahmad Safi, PE