Study guide

4.7 Planning & Managing Resources

Project Management Professional PMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Fundamentals

1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam

2 Chapter 2: People Domain Part 1

2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments

3 Chapter 3: People Domain Part 2

3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence

4 Chapter 4: Process Domain - Planning

4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement

5 Chapter 5: Process Domain - Execution & Control

5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure

6 Chapter 6: Business Environment Domain

6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change

7 Chapter 7: Agile & Hybrid Approaches

7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools

8 Chapter 8: Predictive (Waterfall) Approaches

8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control

4.7 Planning & Managing Resources

Key Takeaways Explain This Topic AI

The RACI matrix defines four roles: Responsible (does the work), Accountable (approves the work), Consulted (provides input), and Informed (receives updates)

Each task in a RACI matrix must have exactly one Accountable person, while there may be multiple Responsible, Consulted, or Informed parties

Resource leveling adjusts the schedule based on resource constraints and may extend the project duration, while resource smoothing works within float and does not extend duration

Team acquisition techniques include pre-assignment, negotiation, acquisition (hiring/contracting), and virtual teams

Project resources include both team resources (human) and physical resources (equipment, materials, facilities)

Last updated: January 2026

Resource management ensures the right people, equipment, and materials are available when needed. It encompasses planning, acquiring, developing, managing, and releasing both team and physical resources.

Resource Management Processes

  • Process Purpose Key Output
  • Plan Resource Management Define how to estimate, acquire, manage resources Resource Management Plan
  • Estimate Activity Resources Estimate type and quantities of resources Resource Requirements
  • Acquire Resources Obtain team members and physical resources Project Team Assignments
  • Develop Team Improve team competencies and interaction Team Performance Assessments
  • Manage Team Track performance, resolve issues, manage changes Change Requests
  • Control Resources Ensure physical resources are available as planned Work Performance Information
  • Types of Project Resources
  • Resource Type Description Examples
  • Team Resources Human resources Project manager, developers, analysts
  • Physical Resources Materials and equipment Computers, machinery, raw materials
  • Facilities Work locations Office space, data centers
  • Infrastructure Supporting systems Networks, servers, tools
  • RACI Matrix (Responsibility Assignment Matrix)

The RACI Matrix defines roles and responsibilities for project activities:

RACI Definitions

  • Role Description Rule
  • R = Responsible Does the work to complete the task Can have multiple
  • A = Accountable Ultimately answerable for completion Must have exactly ONE
  • C = Consulted Provides input before work or decisions Can have multiple
  • I = Informed Notified after work or decisions Can have multiple
  • RACI Matrix Example
  • Activity PM Developer Tester Sponsor Business Analyst
  • Requirements Gathering A C I C R
  • System Design A R C I C
  • Development I R, A C I I
  • Testing C C R, A I C
  • User Acceptance C I C A R
  • Deployment A R R I I
  • RACI Rules
  • Every task must have exactly one A (Accountable)
  • Every task should have at least one R (Responsible)
  • Minimize Cs and Is to avoid communication overload
  • A person can be both R and A for the same task
  • Review with stakeholders to confirm understanding
  • Common RACI Issues
  • Issue Problem Solution
  • No A assigned No one accountable Assign single accountable person
  • Multiple As Confusion over accountability Keep exactly one A per task
  • Too many Rs Unclear who does what Clarify specific responsibilities
  • All Cs Decision paralysis Limit consultations to necessary
  • Resource Estimation
  • Techniques for Estimating Resources
  • Technique Description Use When
  • Expert Judgment Subject matter expert input Complex or unique tasks
  • Analogous Estimating Based on similar projects Limited information available
  • Parametric Estimating Statistical relationships Historical data exists
  • Bottom-Up Estimating Detailed work package estimates WBS is complete
  • Resource Requirements Documentation
  • Element Description
  • Resource Type Skill set or equipment type needed
  • Quantity Number of resources required
  • Duration How long resources are needed
  • Timing When resources are needed
  • Skill Level Experience or capability required
  • Team Acquisition
  • Acquisition Techniques
  • Technique Description When to Use
  • Pre-Assignment Resources committed before project start Key resources already identified
  • Negotiation Working with functional managers Matrix organization
  • Acquisition Hiring or contracting external resources Skills not available internally
  • Virtual Teams Geographically distributed team members Global projects, remote work
  • Pre-Assignment

Resources are committed to the project before it officially starts:

  • Named in project charter
  • Specialized skills required
  • Key subject matter experts
  • Negotiation

In matrix organizations, PMs must negotiate for resources:

  • Negotiating With Focus On
  • Functional Managers Resource availability, skills, duration
  • Other Project Managers Resource sharing, priorities
  • External Organizations Contract terms, expertise
  • Virtual Teams

Teams working across different locations:

  • Advantage Challenge
  • Access to global talent Communication difficulties
  • Reduced travel costs Time zone coordination
  • Flexible work arrangements Building team cohesion
  • 24-hour productivity Cultural differences
  • Resource Optimization Techniques
  • Resource Leveling

Adjusts the schedule based on resource constraints:

  • Characteristic Description
  • Purpose Resolve resource over-allocation
  • Method Adjust activity start/finish dates
  • Impact May extend project duration
  • Changes Critical Path? Yes, can change critical path

Example : If two activities need the same resource simultaneously, one is delayed until the resource is available.

Resource Smoothing

Adjusts activities within their float to reduce resource peaks:

  • Characteristic Description
  • Purpose Reduce resource demand fluctuations
  • Method Use activity float to shift work
  • Impact Does NOT extend project duration
  • Changes Critical Path? No, works within float
  • Comparison
  • Factor Resource Leveling Resource Smoothing
  • Duration Impact May extend Never extends
  • Float Usage Uses all available Only uses existing float
  • Constraint Resource availability Fixed project end date
  • Use When Resources limited End date fixed
  • Team Development
  • Team Development Stages (Tuckman Model)
  • Stage Description PM Role
  • Forming Team comes together Provide direction, clarify goals
  • Storming Conflicts emerge Facilitate resolution, maintain focus
  • Norming Team develops processes Support collaboration
  • Performing Team works effectively Delegate, empower
  • Adjourning Project ends Recognize, transition
  • Team Development Techniques
  • Technique Purpose
  • Training Develop skills and competencies
  • Team Building Improve collaboration and trust
  • Co-location Physical proximity for better communication
  • Recognition Acknowledge contributions and achievements
  • Ground Rules Establish acceptable behavior
  • Resource Management Plan

The Resource Management Plan documents how resources will be managed:

  • Component Description
  • Resource Identification How resources will be identified
  • Acquiring Resources How resources will be obtained
  • Roles and Responsibilities RACI matrix, role descriptions
  • Organization Charts Project organization structure
  • Resource Calendar When resources are available
  • Training Needs Required skills development
  • Recognition Plan How to reward team members
  • Release Plan How resources will be transitioned
  • Key Takeaways
  • RACI matrix clarifies roles: Responsible, Accountable, Consulted, Informed
  • Each task must have exactly one Accountable person
  • Resource leveling may extend duration; resource smoothing works within float
  • Team acquisition includes pre-assignment, negotiation, acquisition, virtual teams
  • Teams progress through Forming, Storming, Norming, Performing, Adjourning
  • Resources include both team members and physical resources

Loading diagram... RACI Matrix Roles and Rules