Getting the right people on the right tasks at the right time is harder than it sounds. Master RACI, Resource Leveling, and histograms for the PMP exam.
You have the perfect plan, approved budget, and clear scope — but two key developers get pulled to another project at the most critical sprint. Or the testing equipment the team needs is only available for 2 weeks, but the testing phase runs 6 weeks. Sound familiar?
Resource management sounds simple — "find people, assign tasks" — but reality is far more complex. Resources are scarce, contested between projects, and availability changes constantly. A PM who fails to manage resources well will see schedules slip, costs rise, and quality fall — even if the original plan looked great.
This article walks through the complete resource management process: from planning, estimating, and acquiring to control — covering both team resources (people) and physical resources (equipment, materials).
Project Resources: More Than Just People
When people say "resource," many PMs only think of personnel. But PMI divides resources into two categories:
- Human Resources (Team Resources): People — developers, designers, testers, BAs, PMs, and everyone who participates in the project
- Physical Resources: Equipment, materials, facilities, infrastructure
Both need to be planned, estimated, acquired, and controlled. A construction project short on cranes is just as serious as being short on engineers. An IT project without test servers affects delivery just as much as lacking developers.
Plan Resource Management — Comprehensive Planning
First step: determine how resources will be estimated, acquired, managed, and used throughout the project.
Why a dedicated resource plan?
Because resource scarcity is always a reality — and resource competition between projects can seriously affect cost, schedule, risk, quality, and every other dimension. Effective resource planning must account for availability, competition, and scarcity from the outset.
Resource Management Plan — Two Parts
This plan is divided into two distinct sections:
Team Resource Management Plan | Physical Resource Management Plan |
Project organization chart | Resource Breakdown Structure |
Roles & responsibilities | Resource identification |
Authority & competences | Resource acquisition |
Team acquisition strategy | Resource allocation |
Team training & development | Resource control |
Recognition and reward | Resource release |
Team release plan |
Resource Breakdown Structure (RBS)
RBS is a hierarchical structure listing all resources by category and type. If WBS breaks down work, then RBS breaks down resources.
Example RBS structure:
Project Resources
- Personnel: Project Management, Engineering, Purchasing...
- Material: Cement, Rubber, Steel...
- Equipment: Crane, Excavator, Server...
Three "Breakdown Structures" — Clear Distinctions
Type | Breaks down what | Purpose |
WBS (Work Breakdown Structure) | Scope of work → deliverables | Defines what needs to be done |
OBS (Organizational Breakdown Structure) | Organization → departments/teams | Defines who is where in the organization |
RBS (Resource Breakdown Structure) | Resources → categories/types | Defines what resources are needed |
Exam tip: PMP questions often ask you to distinguish WBS, OBS, and RBS. Remember: WBS = what (work), OBS = who (organization), RBS = what with (resources). All three are hierarchical structures but break down different things.
What Is a RACI Chart? — Defining Roles and Responsibilities
A RACI Chart (also known as a Responsibility Assignment Matrix — RAM) is a tool that clearly defines who does what on a project. Each task is assigned one of four roles:
R — Responsible | The person who does the work. A task can have multiple R's. |
A — Accountable | The person ultimately responsible for the outcome. Each task must have exactly one A — this is the most important RACI rule. |
C — Consulted | Those whose input is sought before a decision. Two-way communication. |
I — Informed | Those kept updated on outcomes. One-way communication. |
The RACI Chart is created during Plan Resource Management and is its most important output — without it, you cannot effectively Acquire Resources or assign work.
📍 PMP Exam Tip on RACI: The most common mistake is having more than one "A" per task — this is always wrong. When a question asks "who is ultimately responsible if the task fails?" → the person with role A. "Who performs the day-to-day work?" → role R. These two cannot be collapsed into one.
Estimate Activity Resources — How Much Do You Need?
Determine the type and quantity of resources needed for each activity. This process coordinates closely with Estimate Activity Durations and Estimate Costs — because time, cost, and resources are interdependent.
Estimation techniques
Three familiar techniques — similar to estimation in Schedule and Cost Management:
- Analogous (Top-down): Used when only a few top-level WBS items are defined — fast but less accurate
- Parametric: Uses statistical relationships — for example: 1 developer handles 5 modules/month, so 20 modules requires 4 developer-months. More accurate than analogous.
- Bottom-up: Estimate at the activity level then roll up to work packages, control accounts, and the project — most accurate but most time-consuming
Alternative Analysis
Many activities can be completed in different ways with different resource allocations. Alternative analysis helps choose the best approach within the given constraints.
Practical example: rent a tower crane or buy one? Short-term, renting is cheaper, but long-term for the organization, buying may make more sense. The PM needs to analyze the trade-offs.
Output
- Resource Requirements: Define the type, quantity, and timing needed — for example: "2 senior programmers for 4 months" or "3 junior programmers for 5 months"
- Resource Histogram: A visual chart showing resource demand over time — helps identify peak periods and potential overallocation
- Basis of Estimates: Supporting documentation explaining how estimates were made
Acquire Resources — Find and Secure Resources
You have the plan and estimates — now you need to actually obtain the resources. Failure at this step can reduce the probability of success or even lead to project cancellation.
Acquisition methods
Method | Description | When to use |
Pre-assignment | Resources already designated in advance — may be stated in the Project Charter | When a specific expert is needed, or someone who committed from the start |
Negotiation (internal) | Negotiate with the Functional Manager to ensure availability | Matrix organizations — PM must "request" people from departments |
Negotiation (external) | Recruit or hire externally through procurement | When internal skills are lacking or specialized expertise is unavailable |
Virtual Teams | Team members work remotely using electronic tools | Geographically distributed teams — the internet makes this feasible and cost-effective |
💡Pro Tip: In the PMP exam, when a question describes a PM needing resources from another department in a matrix organization → the answer is usually "negotiate with the functional manager." PMs do not have the authority to simply take people — they must negotiate.
Key outputs
- Team Resource Assignments: Documents team members and their roles/responsibilities within the project. Accompanied by a team/staff directory.
- Physical Resource Assignments: Documents the materials, equipment, and facilities to be used.
- Resource Calendar: Identifies when and for how long each resource is available — including holidays. This is a critical input for schedule development.
Control Resources — Monitor and Adjust
Resources are assigned — but reality always differs from the plan. Control Resources ensures resources are used according to plan and deviations are addressed promptly.
Key activities
- Monitor resource expenditures
- Ensure resources are used and released according to plan
- Review resources used versus remaining needs
- Identify shortages or surpluses in a timely manner
- Manage actual changes as they occur
- Influence factors that could cause changes in resource utilization
- Update resource allocation as needed
Core principle: right resources, right time, right place, right amount. Missing any of these elements leads to delays.
Connections to Other Knowledge Areas
Resource Management does not exist in isolation — it connects closely with many other areas:
Knowledge Area | Connection |
Schedule Management | Duration depends on resource availability. Resource leveling/smoothing affects the critical path. |
Cost Management | Cost = resource rates × resource quantity × duration. Adding resources → increases cost. |
Scope Management | WBS defines work packages → the basis for estimating resources |
Team Management | Team management (develop, motivate, manage conflict) complements resource management |
Risk Management | Resource shortage is a risk. Key person dependency is a risk. |
Procurement | External resources are often acquired through the procurement process |
💡Pro Tip for the exam: When a question describes a resource problem — for example, "a key developer is about to leave the project" — think multidimensionally: this is both a resource issue and a risk, and it affects schedule and cost. The best answer usually reflects an integrated mindset, not just solving one dimension.
Summary: The Resource Management Process
Step | Process | Key Outputs | When |
1 | Plan Resource Management | Resource Management Plan, RBS | Planning |
2 | Estimate Activity Resources | Resource Requirements, Resource Histogram, Basis of Estimates | Periodically throughout |
3 | Acquire Resources | Team/Physical Assignments, Resource Calendar | Periodically throughout |
4 | Control Resources | Work performance info, Change requests, Updated plan | Throughout the project |
Key points to remember:
- Resources = Team (people) + Physical (equipment, materials, facilities)
- WBS = work, OBS = organization, RBS = resources
- Bottom-up = most accurate, Analogous = fastest
- Pre-assignment: designated in advance (Charter)
- Matrix org: must negotiate with Functional Manager
- Resource Calendar: when + how long available
- Resource Histogram: demand chart over time
- Resource Leveling (from Schedule Mgmt): balances demand, may delay schedule
- Resource Smoothing (from Schedule Mgmt): adjusts within float, no delays
Resource Management is the "silent" area — less highlighted than Scope or Schedule, but it impacts everything else. A solid resource plan helps you avoid mid-project shocks when you suddenly lose a key person, run short on equipment, or find yourself competing for resources with another project.
Practice scenario questions on resource planning and acquisition — especially in matrix organization environments — on CertFlow. This knowledge falls within the Process domain (41%) of the ECO 2026.
Frequently Asked Questions (FAQ)
What is a RACI chart and how do you read each role?
RACI is a responsibility matrix: R (Responsible) — the person who performs the work; A (Accountable) — the person ultimately responsible, only one per task; C (Consulted) — consulted before decisions are made; I (Informed) — notified after decisions are made. Each task must have exactly one person as A to prevent accountability gaps.
What is the difference between Resource Leveling and Resource Smoothing?
Resource Leveling: adjusts the schedule to avoid exceeding resource limits — may extend the project timeline. Resource Smoothing: shifts activities only within available float — does not change the project timeline but cannot resolve severe overallocation. Leveling is more powerful but more costly.
When should you outsource instead of using internal staff?
Outsource when: internal skills are lacking, speed is critical, the cost of outsourcing is lower than training, or the work falls outside your core competency. Use internal staff when: information security is a concern, tight quality control is needed, or the skills are strategically important for the future. This is a make-or-buy decision that frequently appears in PMP questions.
Now that you understand project resource management — it's time to practice with real exam questions.
Next article: Project Quality Management: QA, QC & Cost of Quality
Project team management: building the team and resolving conflict
Try Free PMP Practice Questions →
Official References:



