Project Resource Management is Knowledge Area 6 in PMBOK 6. It is about finding, getting, developing and managing everything the project needs: physical resources (equipment, materials, facilities) and team resources (the people who do the work). There are six processes: Plan Resource Management (decide the approach), Estimate Activity Resources (work out what each activity needs), Acquire Resources (get the people and things), Develop Team (build skills and teamwork), Manage Team (track performance, give feedback, sort out problems) and Control Resources (make sure resources are there as planned). The people side, Develop Team and Manage Team, is where many exam questions come from: Tuckman's model, conflict resolution, motivation, power and leadership.
✦
From my experience: On my UAE construction projects I managed teams of more than 20 nationalities, plus subcontractor crews who came and went as the work changed. I learned that resource management is about people as much as schedules. A crew that had just joined behaved very differently from one that had worked together for months, and long-lead materials could stop the job just as fast as a missing team. When I teach Tuckman's model and conflict resolution to my PMP students, I use these site examples because they make the theory stick.
This page is my exam-focused view of resource management: the processes, the people theories and the traps PMI likes to test. If you just need to sort out who does what on a real project, use my RACI matrix template instead. This page is for understanding the concepts and passing the exam.
Resource Management is where theory and real life are furthest apart. Getting a team, building its skills and managing its performance involves people, politics and motivation, and none of that fits neatly into a checklist. That is why the PMP exam spends so much time on the human side, and why technical people often find these questions hard.
PMBOK 6 changed this area in one big way. It split human resources from physical resources and renamed the area Project Resource Management. Equipment and materials are managed differently from people, but you still have to plan, get and control both.
On this page you will find the six processes with their inputs, tools and outputs, Tuckman's model, the five conflict resolution methods, the main motivation theories (Maslow, Herzberg, McGregor, McClelland), types of power, the RACI matrix, and how resource management works in agile, predictive and hybrid projects.
Two Resource Dimensions
Physical Resources vs Team Resources: The Dual Focus of KA06
Resource Management covers two very different kinds of resources, and you manage them in different ways.
Teams move through these stages, and can slip back when members change.
Physical resources are equipment, materials, supplies and facilities. You manage them mostly through planning and control: estimate what you need, get it, make sure it arrives on time and is used well, and watch for over- or under-use. When suppliers provide them, this overlaps with procurement.
Team resources are the people who do the work: team members, experts, contractors and anyone else who contributes. People are different from equipment. They have goals, feelings, relationships and careers. Develop Team and Manage Team focus on this human side: leadership, motivation, conflict and performance.
✦
Servant leadership: The PMP exam favours servant leadership. Your main job is to remove obstacles, grow the team's skills and create conditions where people can do their best work. This is the opposite of command and control. In many scenario questions, the wrong answers sound like a boss giving orders and the right answers sound like a leader supporting the team.
The Six Processes
Project Resource Management: The 6 PMBOK Processes
9.1
Plan Resource Management
Planning Process Group · Defines how to estimate, acquire, manage and use physical and team resources
+
Plan Resource Management sets the approach for the whole project. Its main outputs are the Resource Management Plan and the Team Charter. The Resource Management Plan says how you will identify and get resources, who has which role, the organisation chart, how you will estimate needs, how you will train people, how you will assess performance and how you will control resources.
The Team Charter sets the team's ground rules: how you communicate, make decisions, handle conflict, run meetings and hold each other accountable. Agreeing these early saves a lot of arguments later.
Key tools in Plan Resource Management:
Expert judgement: Drawing on experience of resource requirements from similar past projects and subject matter experts in relevant technical domains.
Data representation: RACI chart: The Responsibility Assignment Matrix (RAM) maps project activities to team roles, using RACI codes (Responsible, Accountable, Consulted, Informed) to define who does what for every deliverable or activity. The RACI ensures every piece of work has exactly one person Accountable and at least one person Responsible.
Organisational theory: Understanding how different organisational structures (functional, projectised, matrix) affect resource availability, authority and team dynamics, which directly informs resource planning assumptions.
Inputs
Project Charter
Project Management Plan (Quality, Scope, Schedule Mgmt Plans)
Data representation (hierarchical charts, RACI, text-oriented)
Organisational theory
Meetings
Outputs
Resource Management Plan
Team Charter
Project Documents Updates (Assumption log)
9.2
Estimate Activity Resources
Planning Process Group · Estimates team and physical resources required for each activity
+
Estimate Activity Resources works out the type, quantity and features of the resources each activity needs. It links closely to Estimate Activity Durations in schedule management: the duration depends on the resources, and the resources depend on the duration you are aiming for. You go back and forth until both make sense.
You estimate at the activity level. For each activity, ask: how many hours of which skill? Which equipment, materials or facilities, and when? What limits apply, such as shared people, calendars or locations?
Bottom-up estimating is the most accurate method here: estimate each activity, then add up through the WBS. It needs a good activity list. It also gives you a Resource Breakdown Structure (RBS): a list of resources grouped by category and type, used for planning, tracking and reporting.
Inputs
Project Management Plan (Resource, Scope Management Plans)
Project Documents (Activity list & attributes, Assumption log, Risk register)
Executing Process Group · Obtains team members, facilities, equipment and other resources
+
Acquire Resources is where you get the people, facilities, equipment and materials you need. It runs through execution because you bring resources in as each phase starts, not all on day one.
Getting people is hard because project managers usually have limited authority over who joins the team. In functional and matrix organisations, functional managers assign people, so you have to negotiate for the right people at the right time. Negotiation is a core skill for a PM.
Pre-assignment means some people are named for the project early, often because their skills are the reason for the project or because a contract requires them. You know them before planning starts, but check their availability rather than assume it.
Virtual teams work across locations, time zones or organisations. You need to plan for collaboration tools, cultural and time zone differences, building trust without meeting face to face, seeing performance without being in the same place, and the risk that people feel isolated.
Inputs
Project Management Plan (Resource, Procurement, Cost Management Plans)
Executing Process Group · Improves team competencies, interaction and the overall team environment to enhance project performance
+
Develop Team improves the team's skills, how members work together and the team environment. It is the most people-focused process in PMBOK: building trust, teamwork, skills and motivation so a group of individuals becomes a high-performing team. Its main output is the Team Performance Assessment: how well the team is working and what development is still needed.
Training and development: Identifying and addressing team members' skill gaps through formal training, coaching, mentoring and on-the-job learning. Training costs are project costs and must be planned and budgeted. Skills gaps that cannot be addressed through development within the project timeline may require resource replacement or procurement of specialist support.
Team-building activities: Structured activities designed to strengthen relationships, build trust, improve communication and develop shared norms. Effective team building is not a one-time event. It requires ongoing investment throughout the project lifecycle, particularly during and after periods of conflict or significant change.
Colocation: Placing team members in the same physical location to improve communication, collaboration and team identity. War rooms (dedicated project spaces where the whole team works together) are a colocation technique. While remote work has become standard, colocation during critical project phases can significantly accelerate team development and reduce communication friction.
Recognition and rewards: Formally acknowledging and rewarding team member contributions. Effective recognition systems must be: genuine (not formulaic), timely (close to the contribution), specific (about what was done and why it mattered), and aligned to team values. Public recognition in front of peers is typically more motivating than private financial rewards for many team members.
Inputs
Project Management Plan (Resource Management Plan)
Project Documents (Lessons learned register, Project schedule, Project team assignments, Resource calendars, Team charter)
Enterprise Environmental Factors
Organisational Process Assets
Tools & Techniques
Colocation
Virtual teams
Communication technology
Interpersonal and team skills (conflict management, influencing, motivation, negotiation, team building)
Recognition and rewards
Training
Individual and team assessments
Meetings
Outputs
Team Performance Assessments
Change Requests
Project Management Plan Updates
Project Documents Updates (Lessons learned, Project schedule, Project team assignments, Resource calendars, Team charter)
Enterprise Environmental Factors Updates
9.5
Manage Team
Executing Process Group · Tracks team member performance, provides feedback, resolves issues and manages team changes
+
Manage Team tracks how people are performing, gives feedback, solves problems and handles changes to the team. Develop Team is proactive (building the team). Manage Team is more day-to-day and reactive: dealing with performance issues, conflicts and, when development does not work, changes to the team.
Performance appraisals within projects: Formal and informal assessments of individual team member performance against agreed expectations. Project PMs often contribute to functional performance reviews of team members, even when they do not have direct line management authority. These contributions are a formal communication channel between project performance and individual career progression.
Conflict management: Conflict will happen in every project: limited resources, schedule pressure, different views and personalities. PMBOK says conflict is not always bad. Handled well, it can lead to better decisions and bring problems to the surface. Your job is to manage it well, not to stop it completely. See the conflict resolution section below.
Emotional intelligence (EI): your ability to understand and manage your own emotions and other people's. It matters most under stress, when frustration and tension are high. PMBOK lists it as a tool for Manage Team.
Inputs
Project Management Plan (Resource Management Plan)
Project Documents (Issue log, Lessons learned, Project team assignments, Team charter)
Work Performance Reports
Team Performance Assessments
Enterprise Environmental Factors
Organisational Process Assets
Tools & Techniques
Interpersonal and team skills (conflict management, decision making, emotional intelligence, influencing, leadership)
Project management information system
Outputs
Change Requests
Project Management Plan Updates
Project Documents Updates (Issue log, Lessons learned, Project team assignments)
Enterprise Environmental Factors Updates
9.6
Control Resources
Monitoring & Controlling Process Group · Ensures resources are available as planned; manages variances in physical resources
+
Control Resources makes sure physical and team resources are available as planned, compares actual use with the plan, and takes action when there are big differences. It is mostly about physical resources (equipment, materials, facilities), though it also covers how the team is being used.
Typical situations: equipment arrives late or breaks down, materials fail the specification, people are overloaded, people are sitting idle, or resource needs change with the scope. Each needs a different response, from chasing the supplier, to adjusting the schedule, to moving people around.
Resource optimisation: Two techniques from Schedule Management are applied here in a resource management context. Resource levelling resolves over-allocations by adjusting activity timing: potentially extending schedule duration. Resource smoothing uses activity float to reduce demand peaks without extending the schedule. Both aim to produce a resource plan that is feasible within available capacity.
Inputs
Project Management Plan (Resource Management Plan)
PMBOK Guide 6th edition (2017) lists these 6 processes. PMBOK 7 (2021) replaced processes with principles and performance domains, and PMBOK 8 now uses 6 principles and 7 performance domains. The processes are still a good way to learn the topic.
What are the 5 stages of Tuckman's model?
Bruce Tuckman's model is one of the most tested topics on the PMP exam. It describes the stages teams go through as they meet, build working relationships, deal with conflict and reach high performance. If you know the stage, you know what kind of leadership the team needs.
Tuckman's 5 Stages of Team Development
1
Forming
Team members meet and begin to understand their roles, responsibilities and how the team will operate. Behaviour is typically polite and cautious: individuals are testing boundaries and forming impressions. Productivity is low because the team is still learning how to work together. People are uncertain about what is expected of them and often look to the PM for direction.
Provide clear direction, structure and expectations. Define roles and responsibilities explicitly. Build psychological safety. Facilitate introductions and relationship-building.
2
Storming
The most difficult stage: conflict emerges as team members compete for position, challenge authority, disagree about approaches, and express frustration with constraints. Power struggles, personality clashes and resistance to leadership are common. Productivity drops further. Many teams get stuck here and never reach high performance. Teams that work through storming constructively emerge stronger.
Facilitate conflict resolution without avoiding it. Coach individuals through disagreements. Reinforce the team charter and agreed norms. Use collaborative conflict resolution rather than suppression. Be patient: this stage is necessary, not a failure.
3
Norming
The team establishes working norms: shared standards for how work will be done, how decisions will be made, and how the team will operate together. Conflict decreases, cohesion increases, and the team begins to function more efficiently. Trust starts to build. Individuals begin to identify with the team as a unit rather than as separate individuals.
Reinforce positive norms and collaborative behaviours. Gradually shift from directive to facilitative leadership. Encourage team-led decision making. Celebrate early successes to build confidence and cohesion.
4
Performing
The team operates at high effectiveness: members work interdependently, use each other's strengths, solve problems collaboratively and produce excellent work with minimal friction. The team is self-managing in day-to-day work; the PM can focus on strategic issues, stakeholder management and removing external obstacles rather than directing the team's work.
Shift to servant leadership: remove obstacles, provide resources, protect the team from external interference. Delegate decision-making authority. Maintain morale and momentum. Focus on stakeholder management and strategic issues.
5
Adjourning
The project ends and the team disbands. This stage involves completing final deliverables, capturing lessons learned, formal closure activities, and managing the emotional dimensions of team dissolution: which can include both relief and genuine loss, particularly for high-performing teams with strong bonds. Not in Tuckman's original four-stage model; added later.
Conduct thorough lessons learned. Provide career development feedback to team members. Recognise and celebrate team achievements. Manage the emotional aspects of closure with empathy. Ensure smooth knowledge transfer.
Conflict Resolution
Which conflict resolution method is most effective?
Conflict is normal in project teams and can even be useful. PMBOK names five ways to resolve it, and the exam often asks which one fits a given situation. The order below shows what PMBOK prefers: collaborate first, force last.
✦Collaborate / Problem SolveBest approach
Both parties work together to find a solution that fully satisfies all parties' interests. Requires open communication, trust and time. Produces the most durable resolution because all parties are genuinely satisfied. PMBOK's preferred technique. It builds relationships and produces lasting solutions. Also called "confronting" in some PMBOK versions.
✦Compromise / ReconcileAcceptable
Both parties give up something to reach a mutually acceptable solution. Neither party is fully satisfied but both accept the outcome as fair. A reasonable default when collaboration is not feasible due to time constraints or entrenched positions. Sometimes called a "lose-lose" outcome, both parties made concessions, though this framing is too negative for its practical value.
✦Accommodate / SmoothSituational
One party accommodates the other's position, emphasising areas of agreement and downplaying differences. Does not address the underlying issue: may allow conflict to resurface later. Sometimes appropriate as a short-term measure to preserve relationships or buy time for a fuller solution. Overuse leads to unresolved underlying tensions.
✦Avoid / WithdrawShort-term only
One or both parties retreat from the conflict situation, refusing to engage. Does not resolve the conflict, the underlying issue remains. Sometimes appropriate when the timing is wrong (the conflict is premature or emotions are too high for productive resolution). Persistent avoidance of conflict is destructive to team performance and trust. Most useful as a temporary tactical measure.
✦Force / DirectLast resort
The PM or a senior party imposes a solution, typically using positional authority or power. One party wins; the other loses. Creates resentment, undermines trust, and produces only temporary resolution. Appropriate only in genuine emergencies (safety issue, immovable deadline, legal requirement) where time constraints prevent collaborative resolution. Overuse destroys team morale and psychological safety.
Motivation Theories
Motivation Theories in Project Resource Management
The exam uses several motivation theories in Develop Team and Manage Team questions. Each one gives you a different way to understand what drives people.
Maslow's Hierarchy of Needs
Five needs arranged hierarchically: Physiological → Safety → Social/Belonging → Esteem → Self-Actualisation. Lower-order needs must be sufficiently met before higher-order needs motivate. In project management: a team member worried about job security (Safety) will not be motivated by project achievement recognition (Esteem). PMs must understand which level of need is currently most salient for each team member. Remote workers may have Social needs that need deliberate addressing through team-building.
Herzberg's Two-Factor Theory (Hygiene vs Motivators)
Hygiene factors (salary, working conditions, company policy, supervision): their absence causes dissatisfaction but their presence does not motivate. Motivating factors (achievement, recognition, the work itself, responsibility, growth): their presence actively motivates. Key implication: paying people fairly removes dissatisfaction but does not create motivation. To motivate, PMs must provide meaningful work, recognition, autonomy and development opportunities, not just better pay.
McGregor's Theory X and Theory Y
Theory X: Assumes people are inherently lazy, dislike work, and must be coerced, controlled and directed. Leads to micromanagement, close supervision and directive management styles. Theory Y: Assumes people are self-motivated, enjoy meaningful work, seek responsibility, and exercise self-direction when committed to objectives. Theory Y assumptions underpin servant leadership and Agile team management. The PMP exam consistently favours Theory Y approaches, autonomy, trust, meaningful work, over Theory X approaches.
McClelland's Theory of Needs (Acquired Needs)
Three acquired needs that motivate individuals differently: Achievement (nAch): driven by setting and achieving challenging goals, seeking feedback on performance; Affiliation (nAff): motivated by relationships, belonging and being liked; Power (nPow): motivated by influencing others, either for personal gain (personal power) or organisational effectiveness (institutional power). PMs must recognise which need profile dominates each team member and structure motivation accordingly. Achievement-oriented individuals need stretch targets; affiliation-oriented individuals need team belonging; power-oriented individuals need influence and leadership responsibility.
Power and Influence
Types of Power: How PMs Influence Without Authority
Project managers often have no formal authority over the people they rely on, especially in functional and matrix organisations. So you need to know where else your influence can come from.
Five Power Types: From Formal to Informal
Formal / Legitimate Power
The power that comes from the PM's official position and title. Team members comply because the PM has organisational authority over project decisions.
"As project manager, I am authorising this change."
Reward Power
The ability to offer positive consequences, recognition, bonuses, promotions, career opportunities, in exchange for desired behaviour. Effective when rewards are valued and the PM controls access to them.
"Your contribution on this project will be highlighted in your performance review."
Penalty / Coercive Power
The ability to impose negative consequences: poor reviews, assignment to undesirable work, exclusion from opportunities. Produces compliance but destroys trust and motivation. PMBOK explicitly discourages overuse. Should be a last resort.
"If this is not resolved, I will need to escalate to your functional manager."
Expert Power
Influence derived from the PM's technical knowledge, skills or experience. Team members comply because they trust the PM's expertise and judgement. Highly effective and does not require formal authority. Most valued when the PM has genuine domain expertise relevant to the project.
"Based on my experience with similar migrations, the approach that minimises risk is..."
Referent Power
Influence derived from the PM's personal character, relationships and reputation: people follow them because they like, respect or admire them. The most powerful and durable form of influence. Cannot be manufactured; built through consistent integrity, empathy and genuine investment in team members' development and wellbeing.
Team members go above and beyond because they respect and trust the PM as a person.
✦
PMP exam pattern: The exam usually prefers expert power and referent power. If a question asks how to influence people without formal authority, choose the expert or referent answer. Coercive (penalty) power is almost never the right answer unless there is a real safety or compliance emergency.
Responsibility Assignment
The RACI Matrix: Defining Roles and Responsibilities
The RACI matrix is the main tool for showing who does what. Every deliverable or activity in the WBS should have a RACI code for each relevant role.
Activity / Deliverable
Project Manager
Business Analyst
Developer
Test Lead
Sponsor
Requirements document
R
A
C
C
I
Solution design
C
C
A
C
I
Build and unit test
I
C
A
C
I
System integration test
C
C
R
A
I
User acceptance test
C
R
C
A
C
Go-live approval
R
C
C
C
A
R = Responsible (does the work) · A = Accountable (owns the outcome: only one per row) · C = Consulted (provides input before completion) · I = Informed (notified after completion)
RACI rules to remember: Every activity must have exactly one Accountable: two people accountable means nobody is truly accountable. Every activity must have at least one Responsible. There can be multiple R, C and I designations per row. An activity with too many C designations becomes a bottleneck: consulting everyone delays decisions. An activity with no I designations may result in stakeholders surprised by outcomes.
Interrelation to Other Knowledge Areas
How Resource Management Connects to Every Other Knowledge Area
✦KA01: Integration Management
The Resource Management Plan is a subsidiary component of the Project Management Plan, integrated under KA01. Team changes that affect project performance must be processed through integrated change control. When a team member departs mid-project or resource availability changes significantly, a change request may be needed to update the schedule and cost baselines. The PM's leadership style directly affects team performance, which affects the project's overall performance: integration management's health is inseparable from team resource management quality.
✦KA02: Scope Management
The WBS is the foundation for activity resource estimation in KA06. Every work package must be assigned to at least one Responsible resource via the RACI matrix. Scope changes that add work packages require resource planning updates: new resources may need to be acquired, or existing resources reallocated. The RACI matrix maps scope (deliverables) to responsibility (team members), making scope and resource management fundamentally linked throughout the project lifecycle.
✦KA03: Schedule Management
Resource availability is a primary constraint on activity duration. Estimate Activity Resources (KA06) and Estimate Activity Durations (KA03) iterate together. You cannot finalise either without the other. Resource calendars (working hours, holidays, part-time allocations, shared resource availability) define when resources can work on project activities. Resource levelling to resolve over-allocations may extend the critical path. Team performance, whether the team is in forming, storming or performing, directly affects actual vs estimated activity durations.
✦KA04: Cost Management
Labour is typically the dominant project cost category: resource rates, hours and utilisation flow directly into cost estimates and the cost baseline. Crashing the schedule (adding resources to compress the critical path) is a joint cost-resource management decision. Team development activities (training, team-building, colocation) are project costs that must be budgeted. Resource over-allocation resolved through overtime adds cost. Poor team performance leading to rework adds unplanned cost that damages CPI.
✦KA05: Quality Management
Resource skill gaps directly cause quality defects. An undertrained developer introduces bugs; an inexperienced BA writes ambiguous requirements. Training (a Develop Team activity) is simultaneously a quality prevention investment. It reduces defect probability by ensuring team members have the skills to do their work correctly. Quality audits may identify process failures that trace back to team competency gaps, triggering resource development interventions through KA06.
✦KA08: Risk Management
Resource risks are among the most common project risks: key person dependency (project fails if a specific individual leaves), resource unavailability (functional managers withhold promised resources), skill gaps (team cannot perform required work), and team conflict (interpersonal dynamics impede delivery). Key person risks require specific risk responses: knowledge transfer, cross-training, succession planning. The Risk Register feeds into resource planning as a constraint: high-risk activities may require more senior or experienced resources than standard allocation would suggest.
✦KA07: Communications Management
Team development depends on effective communication infrastructure. Virtual teams require deliberate communication planning, collaboration tools, meeting cadences, async communication norms, to compensate for the absence of face-to-face interaction. The Communications Management Plan defines how team members communicate, which directly enables or impedes team development. Conflict (a Manage Team activity) often has a communication failure at its root: unclear expectations, misunderstood instructions, or information withheld between team members.
✦KA09: Procurement Management
The make-or-buy decision in Procurement Management is directly linked to resource management:the decision to buy is typically driven by a resource capability or capacity gap. Contracted resources (consultants, contractors, outsourced teams) are managed through their contracts (KA09), not through the same team development processes as internal team members. Key person clauses, substitution approval, and supplier mobilisation plans in contracts are procurement mechanisms that address resource management concerns. Contract terms must align with the project's resource management plan.
✦KA10: Stakeholder Management
Team members are stakeholders. The Stakeholder Register should include project team members, and their engagement level should be actively managed alongside external stakeholders. Functional managers who control resource allocation are critical stakeholders in a matrix organisation: their cooperation or resistance directly affects the PM's ability to acquire and retain the team. The interpersonal and leadership skills developed through resource management (emotional intelligence, conflict management, influence) are equally applicable to stakeholder management.
Agile and Hybrid Approaches
Resource Management in Agile, Waterfall and Hybrid Environments
Resource Management in Waterfall
Traditional waterfall resource management follows the full six-process PMBOK model:
Detailed resource planning upfront: all resource requirements identified from the full WBS
Formal RACI matrix covering all activities and roles
Resource calendars defining availability across the project duration
Resource levelling applied during schedule development
Formal performance appraisal contributions to functional managers
Training plans developed and executed within defined project phases
Physical resource procurement managed through formal procurement processes
PM holds formal authority over project decisions; team members report through dual lines (functional and project)
Strength: Clear roles, responsibilities and reporting lines. Challenge: Resource availability commitments made early may not hold through the project lifecycle in volatile organisations.
Resource Management in Agile
Agile resource management is structured around stable, cross-functional teams with servant leadership:
Stable team composition: Agile thrives on team stability, the same people working together across multiple sprints rapidly progress through Tuckman's stages to performing
Cross-functional teams: All skills needed to deliver a sprint are within the team: no waiting for external specialists or handoffs
Self-organising teams: Teams decide how to do the work within the sprint; the Scrum Master removes obstacles rather than directing activities
Servant leadership: The Scrum Master (equivalent to PM) prioritises team empowerment, coaching and obstacle removal over directive management
Sustainable pace: Agile explicitly protects teams from overcommitment: velocity-based sprint planning prevents the over-allocation that causes burnout
Retrospectives provide continuous team development through structured reflection
T-shaped skills (broad knowledge + deep expertise) are valued for cross-functional flexibility
Strength: High-performing self-organising teams. Challenge: Stable team composition conflicts with the functional manager's need to allocate specialists across multiple projects.
Exam Tips
Resource Management: 7 Exam Tips for PMP and APM PMQ
1
Collaborate/Problem Solve is almost always the preferred conflict resolution approach. The PMP exam strongly favours collaborative conflict resolution that addresses the root cause and satisfies all parties. Forcing (directive authority) is almost never the right answer. Avoidance is occasionally acceptable as a short-term measure. When in doubt, choose the option that involves the conflicting parties working through the issue together.
2
Know Tuckman's stages and the PM's appropriate response at each. Forming requires direction and clarity. Storming requires conflict facilitation, not suppression. Norming requires coaching and gradual delegation. Performing requires servant leadership and obstacle removal. Adjourning requires closure management. Exam scenarios describe a team situation and ask what the PM should do: match the behaviour to the stage.
3
Theory Y and servant leadership are the exam's preferred management orientation. The PMP exam consistently rewards answers that trust the team, delegate authority, empower self-organisation, and support development. Theory X approaches (close supervision, directive control, coercive authority) are almost always wrong answers. When two options look similar, choose the one that gives the team more autonomy and the PM more of a facilitating role.
4
Herzberg: hygiene factors prevent dissatisfaction; motivators create motivation. A question asking what motivates a team member should be answered with factors from the motivating factors category (achievement, recognition, growth, the work itself), not hygiene factors like pay or working conditions. Removing a hygiene factor causes dissatisfaction; improving it does not create motivation.
5
Expert and referent power are the most effective for PMs without formal authority. In matrix organisations where PMs do not have line authority over team members, expert power (knowledge and competence) and referent power (personal relationships and respect) are the most effective influence mechanisms. Coercive/penalty power creates compliance but destroys trust. Formal/legitimate power is only available to PMs with explicit authority.
6
One and only one Accountable per RACI row. A key RACI rule tested on both PMP and APM PMQ: each activity must have exactly one person Accountable, the person who owns the outcome and is ultimately responsible to the organisation. Two Accountable parties means neither is truly accountable. Multiple Responsible parties are acceptable (the work can be shared); multiple Accountable parties create confusion and diluted ownership.
7
Resource Management Plan includes both physical and team resources. Exam questions sometimes focus only on people, but PMBOK Resource Management explicitly covers physical resources (equipment, materials, facilities) as well. The Control Resources process (9.6) is primarily about physical resources: ensuring equipment arrives on schedule, managing material utilisation, and correcting resource variances. Do not confuse it with Manage Team (9.5), which focuses on people performance.
Worked exam example: storming on site
Here is a scenario I use with my PMP students. Two experienced supervisors join your team from different subcontractors. Within a week they argue in front of the crew about the method for a task. The rest of the team is unsettled. What should you do first?
A) Decide the method yourself and tell both to follow it.
B) Meet both supervisors, listen to each side and work out a solution together, using the team charter as the reference.
C) Ask their functional managers to replace one of them.
D) Wait and let them sort it out.
The answer is B. The team is in storming, and the exam wants collaborate/problem solve. A is forcing, C escalates too early, and D is avoiding.
Mistakes I see most often in mock exams:
Picking "escalate to the functional manager" before the PM has tried to solve it.
Thinking pay rises motivate. In Herzberg's model pay is a hygiene factor.
Putting two people as Accountable on one RACI row.
Forgetting that Control Resources is mainly about physical resources.
Apply This Knowledge Area in Your PMP or APM PMQ Exam
Tuckman's model, conflict resolution, motivation theories and types of power come up often in PMP practice questions. The 2026 exam is built on the Exam Content Outline, where the People domain is 33% of the exam, so the people side of this page matters. The APM PMQ also tests team and resource management.
The six PMBOK 6 processes in Project Resource Management (Knowledge Area 6) are: (1) Plan Resource Management: set the approach; outputs are the Resource Management Plan and Team Charter. (2) Estimate Activity Resources: work out the resources each activity needs; outputs include Resource Requirements and the Resource Breakdown Structure. (3) Acquire Resources: get the people and physical resources; outputs include Project Team Assignments and Resource Calendars. (4) Develop Team: improve skills and teamwork; output is Team Performance Assessments. (5) Manage Team: track performance, give feedback and resolve conflict; outputs include Change Requests. (6) Control Resources: make sure resources are available as planned and fix variances; outputs include Work Performance Information and Change Requests.
Tuckman's model has five stages. Forming: people meet, roles are unclear, everyone is polite and looks to the PM for direction. Storming: conflict appears as people push for position, and productivity drops. Norming: the team agrees how to work, conflict goes down and trust builds. Performing: the team works well and mostly manages itself. Adjourning: the work ends and the team breaks up. Your leadership changes with each stage: directing at forming, facilitating at storming, coaching at norming and servant leadership at performing.
PMBOK's preferred method is Collaborate/Problem Solve (sometimes called confronting). Everyone works together to find a solution that meets all interests. It takes time and trust but lasts, because it fixes the real issue. From most to least preferred: Collaborate/Problem Solve, Compromise/Reconcile (both sides give something up), Smooth/Accommodate (play down differences, short-term only), Withdraw/Avoid (step back, only when the timing is wrong), and Force/Direct (impose a solution, only in a real emergency). The exam rewards collaboration and penalises forcing.
The RACI matrix is a grid with activities or deliverables as rows and roles as columns. Each cell has one code. Responsible (R): does the work. Accountable (A): owns the outcome; only one per row. Consulted (C): gives input before the work is finished (two-way). Informed (I): is told after it is finished (one-way). It makes sure every activity has an owner and stops gaps and duplication.
Develop Team (9.4) and Manage Team (9.5) are both executing processes, but they look in different directions. Develop Team is proactive: training, team building, recognition and colocation to grow the team's skills and trust. Its output is Team Performance Assessments. Manage Team is reactive and day-to-day: tracking performance, giving feedback, resolving conflict and changing the team when development does not work. Its main tools are emotional intelligence, interpersonal skills and conflict management. Develop Team asks "how do we build a better team?" Manage Team asks "how do we deal with what is happening now?"
Agile teams are stable and cross-functional. The same people work together sprint after sprint, so they reach the performing stage faster and stay there. Moving people in and out keeps pulling the team back to forming. Teams organise themselves inside the sprint and decide how to do the work. The Scrum Master acts as a servant leader: removing obstacles, coaching and protecting the team instead of handing out tasks. Sprint planning based on velocity helps avoid overloading people, and retrospectives build team development into every sprint.
