PMP Resource Management: Acquire, Develop, Manage Team

If integration is the spine of project management and scope is the contract, then resource management is the heartbeat. I have managed projects with perfect plans that still failed because the team was misaligned, and I have managed projects with chaotic plans that succeeded because the team was world-class. The PMP exam recognises this, which is why pmp resource management has shifted noticeably toward leadership, team development, and conflict resolution in recent editions.

In this guide I want to walk you through resource management as both a planning discipline and a leadership discipline. We will cover the six processes, the Tuckman stages of team development, the five conflict resolution modes, team charters, virtual team challenges, and ten exam-style questions to sharpen your judgement.

By the end you should have a clear playbook for acquiring, developing, and leading teams, plus the language and frameworks the PMP exam expects from you. Let us get into it.

Resource Management is the set of processes used to identify, acquire, and manage the resources needed for successful completion of the project. "Resources" in PMBOK includes both team members (human resources) and physical resources (equipment, materials, supplies, facilities).

The knowledge area spans Planning (two processes), Executing (three processes), and Monitoring and Controlling (one process). It is one of the more execution-heavy knowledge areas because so much of leading a team happens during executing.

Note: PMBOK 6 renamed "Human Resource Management" to "Resource Management" to reflect that physical resources also need to be planned and controlled. PMBOK 7 continues this framing.

This process defines how to estimate, acquire, manage, and use both team and physical resources. Outputs include the resource management plan and the team charter.

The resource management plan addresses:

• Identification of resources
• Acquisition strategy (internal, contractor, virtual)
• Roles and responsibilities (RACI matrix, RAM)
• Project organisation charts
• Project team resource management
• Training needs
• Team development approach
• Resource control mechanisms
• Recognition plan

Tools include expert judgement, data representation (hierarchical charts like OBS, matrix-based charts like RACI, text-oriented descriptions), organisational theory, and meetings.

Estimate Activity Resources determines the team resources, type and quantity of materials, equipment, or supplies necessary to perform project work.

Outputs include resource requirements, basis of estimates, and the resource breakdown structure (RBS) - a hierarchical representation of resources by category and type.

Tools include expert judgement, bottom-up estimating, analogous, parametric, data analysis (alternatives analysis), PMIS, and meetings.

Worked example. An activity to deploy a CRM module needs:

• 1 senior developer (40 hours)
• 1 QA engineer (20 hours)
• 1 business analyst (8 hours)
• Cloud environment (1 production-equivalent for 5 days)
• Licensing (10 user seats)

That bundle of human and physical resources is the activity's resource requirements.

Acquire Resources obtains team members, facilities, equipment, materials, supplies, and other resources necessary to complete project work.

Tools include decision making (multi-criteria decision analysis, e.g., based on availability, cost, experience), interpersonal and team skills (negotiation), pre-assignment, and virtual teams.

Outputs include physical resource assignments, project team assignments, resource calendars, change requests, and updates.

Key concept: halo effect. Assuming a person is good at one thing because they are good at another (e.g., a great developer must be a great team lead). Avoid this when selecting team members.

Develop Team improves competencies, team member interaction, and overall team environment to enhance performance.

Tools include colocation, virtual teams, communication technology, interpersonal and team skills (conflict management, influencing, motivation, negotiation, team building), recognition and rewards, training, individual and team assessments, and meetings.

Key concepts:

• Colocation improves communication but is not always possible
• Virtual teams require deliberate communication structures
• Recognition should be culturally appropriate (avoid public praise in cultures that prize humility)
• Team building spans informal lunches to off-site retreats

Manage Team tracks team member performance, provides feedback, resolves issues, and manages team changes to optimise project performance.

Tools include interpersonal and team skills (conflict management, decision making, emotional intelligence, influencing, leadership), and PMIS.

This is where the PM exercises situational leadership: directing for new team members, coaching for those gaining skills, supporting for confident contributors, and delegating for self-sufficient experts.

The exam frequently tests “what should the PM do” when a team member underperforms, misses a meeting, or conflicts with another. Almost always the answer involves direct, private conversation first.

Control Resources ensures that physical resources assigned and allocated to the project are available as planned, monitors resource utilisation, and takes corrective action as necessary.

This process focuses on physical resources rather than team management (which sits in Manage Team).

Tools include data analysis (alternatives analysis, cost-benefit analysis, performance reviews, trend analysis), problem solving, interpersonal and team skills (negotiation, influencing), and PMIS.

Bruce Tuckman’s model is heavily tested. Memorise the order and the characteristics.

Forming. Team meets, learns about the project, roles and responsibilities. Members are polite, reserved, and unclear about their place. PM provides direction.

Storming. Team begins to address work, but conflicts emerge over approaches, decisions, leadership styles. Productivity drops. PM coaches and mediates.

Norming. Team starts working together, behaviours and processes settle, trust builds. Productivity rises. PM supports.
Performing. Team operates as a well-organised unit. Members are interdependent, working through issues smoothly. PM delegates.

Adjourning. Team completes work and disbands. PM recognises contributions, captures lessons learned, supports transitions.
 

Mnemonic I use: “Forms Storm Norms Perform Adjourns”.

Five modes from Thomas-Kilmann, all examinable.

Withdraw / Avoid. Retreating from the conflict or postponing the issue. Useful when more information is needed or stakes are low. Generally not preferred for project issues.

Smooth / Accommodate. Emphasising areas of agreement rather than differences. Useful when relationship matters more than the issue. Tends to leave root causes unaddressed.

Compromise / Reconcile. Both parties give up something to reach a solution. Useful when a quick resolution is needed and stakes are moderate. Sometimes called “lose-lose” because neither party fully wins.

Force / Direct. Pushing one viewpoint at the expense of others. Sometimes necessary for emergencies. Often damages relationships.

Collaborate / Problem Solve. Working together to find a solution that meets everyone’s needs. The PMI-preferred approach when time permits. Often called “win-win”.

Exam answer pattern: when in doubt, choose collaborate/problem solve. When time is critical, force/direct may be acceptable. Avoid is rarely correct.

The team charter is a document that establishes the team’s values, agreements, and operating guidelines. PMBOK 6 made it an explicit output of Plan Resource Management.

A useful team charter covers:

• Team values (e.g., respect, transparency, accountability)
• Communication guidelines (channels, response times)
• Decision-making process (e.g., consensus, majority, delegated authority)
• Conflict resolution process
• Meeting guidelines (cadence, agenda, ground rules)
• Other team agreements (working hours, escalation paths)

I co-create the team charter with the team in the first week. Imposed charters fail; co-created ones stick.

Virtual teams - members in different locations using technology to collaborate - bring unique benefits and challenges.

Benefits:

• Access to broader talent pool
• Lower travel and facility costs
• Inclusion of mobility-impaired members
• 24/7 productivity through time zones

Challenges:

• Communication misunderstandings (lack of non-verbal cues)
• Isolation and disengagement
• Difficulty building trust
• Coordination across time zones
• Technology and connectivity dependence

My playbook for virtual teams:

1. Establish clear communication norms early (channel use, response times)
2. Schedule regular video meetings (cameras on by default)
3. Use asynchronous tools for documentation (wikis, shared drives)
4. Build in informal connection time (virtual coffees, ice-breakers)
5. Rotate meeting times to share time-zone burden
6. Over-communicate compared to colocated teams

Q1. In which Tuckman stage does conflict typically peak?
 

A. Forming
B. Storming
C. Norming 
D. Performing
 

Answer: B.
 

Q2. A team member misses two consecutive status meetings. What should the PM do first?
 

A. Escalate to the functional manager
B. Have a private conversation with the team member
C. Issue a formal warning
D. Reassign the work

Answer: B.
 

Q3. Which conflict mode is PMI-preferred?
 

A. Withdraw
B. Smooth
C. Compromise
D. Collaborate

Answer: D.

Q4. A RACI matrix is a:

A. Hierarchical chart
B. Matrix-based responsibility assignment
C. Text-based role description
D. Resource calendar

Answer: B.

Q5. The team charter is an output of:
 

A. Plan Resource Management
B. Acquire Resources
C. Develop Team
D. Manage Team
 

Answer: A.

Q6. Colocation is a tool of which process?

A. Plan Resource Management
B. Estimate Activity Resources
C. Develop Team
D. Control Resources

Answer: C.

Q7. Two team members disagree on a technical approach with a deadline tomorrow. PM should:

A. Pick one side
B. Avoid the issue
C. Facilitate a quick collaborative discussion
D. Smooth over the conflict
 

Answer: C. Collaborate where time permits; if not, force is acceptable. The example allows a quick collab.

Q8. A team member from a high-context culture is being publicly praised but seems uncomfortable. PM should:

A. Continue praising in front of others
B. Adjust the recognition style privately
C. Stop recognising the team member
D. Ask HR to handle it

Answer: B. Cultural sensitivity matters.

Q9. Resource breakdown structure (RBS) is:

A. A hierarchical representation of resources
B. The risk breakdown structure
C. A schedule diagram
D. A cost report

Answer: A.

Q10. During performing stage, the PM should:

A. Direct heavily
B. Coach intensively
C. Delegate and remove blockers
D. Mediate conflict

Answer: C.

The traps that catch most candidates.

• Confusing Manage Team with Control Resources. Manage Team = people; Control Resources = physical resources.
• Mixing up Tuckman stages. Storming comes before norming.
• Avoidance / withdraw being “correct”. Rarely. Only correct when more information is needed or stakes are low.
• PM going to functional manager first. Almost always wrong. Talk to the team member first.
• Assuming colocation is always best. Sometimes virtual teams are required. PMI is neutral.
• Treating team charter as optional. It is a formal output. Always create one.
• Confusing RBS (resource) with RBS (risk). Same acronym, different breakdown.

The PMP exam expects familiarity with several classic leadership and motivation theories. Here is a quick reference of the ones I see most often in question banks.

Maslow’s hierarchy of needs. Five levels: physiological, safety, social/belonging, esteem, self-actualisation. People must satisfy lower needs before higher ones become motivators. Useful framing for team member engagement.

Herzberg’s two-factor theory. Hygiene factors (salary, working conditions, policies) prevent dissatisfaction but do not motivate. Motivators (achievement, recognition, growth) drive performance. PMs should ensure hygiene factors are adequate, then focus on motivators.

McGregor’s Theory X and Theory Y. Theory X assumes workers dislike work and need supervision. Theory Y assumes workers are self-motivated and seek responsibility. PMI generally favours Theory Y.

McClelland’s theory of needs. Three needs drive behaviour: achievement, affiliation, power. Different team members are driven by different needs. Match work to drivers.

Vroom’s expectancy theory. Motivation = expectancy x instrumentality x valence. People are motivated when they believe effort leads to performance, performance leads to reward, and the reward is valued.

Situational leadership (Hersey-Blanchard). Leadership style should match team member maturity: directing for low maturity, coaching for moderate-low, supporting for moderate-high, delegating for high.

Exam tip: when a question mentions “what motivates the team”, recognition and achievement are usually preferred over salary or perks.

PMs operate in matrix organisations where formal authority is often limited. Understanding power forms is essential.

Positional power (legitimate). Authority that comes from role. Limited for PMs in weak matrix organisations.

Reward power. Ability to grant rewards (recognition, promotions, bonuses). PMs often have informal reward power even when formal is limited.

Expert power. Influence based on knowledge or skill. Strong PMs build expert power through preparation and credible contributions.

Referent power. Influence based on respect, charisma, or relationship. The most enduring form of power.

Punitive (coercive) power. Ability to impose penalties. Least effective long-term, damages trust.

I encourage PMs to invest in expert and referent power as primary, supplement with reward power, and avoid coercive power unless absolutely necessary. Most exam questions about influence reward this hierarchy.

Here is the playbook I use when forming a new team, distilled to seven practices.

1. Hold a structured kick-off. Cover purpose, scope, success metrics, charter, communication norms, and immediate next steps. Build energy.
2. Co-create the team charter. Do not impose. Facilitate values, norms, and decision-making process discussions.
3. Run a skills inventory. Understand each member’s strengths, growth areas, and aspirations. Match work accordingly.
4. Set up regular one-on-ones. Weekly or fortnightly. Topics: progress, blockers, well-being, growth.
5. Build feedback loops early. Establish how feedback flows in both directions, including upward to the PM.
6. Celebrate small wins. Recognition early in the project builds engagement and trust.
7. Plan for adjourning. From day one, think about how this team will close: lessons learned, recognition, transition support.

These seven practices, done consistently, take a forming team through to performing faster than any single intervention. They also align with PMP exam expectations about servant leadership and team development.