Guide §2.6 · PRINTED PP. 79–91
Resources Performance Domain
The Resources domain addresses how the project plans, estimates, acquires, leads, uses, monitors, and releases human, physical, and virtual resources. It deliberately separates leading the team from controlling nonhuman resources: people require motivation, feedback, development, trust, conflict resolution, cultural intelligence, and empowerment, while equipment, materials, facilities, software, licenses, services, and environments require availability, configuration, logistics, utilization, maintenance, and release control. Both sides must be integrated with schedule, finance, procurement, risk, quality, and sustainability.
Understand the chapter
The Resources domain addresses how the project plans, estimates, acquires, leads, uses, monitors, and releases human, physical, and virtual resources. It deliberately separates leading the team from controlling nonhuman resources: people require motivation, feedback, development, trust, conflict resolution, cultural intelligence, and empowerment, while equipment, materials, facilities, software, licenses, services, and environments require availability, configuration, logistics, utilization, maintenance, and release control. Both sides must be integrated with schedule, finance, procurement, risk, quality, and sustainability.
Learning objectives
- Distinguish the responsibilities of the project manager, resource manager, team members, and suppliers in functional, matrix, contracted, and self-organizing settings.
- Plan how resources will be estimated, acquired, led, utilized, monitored, controlled, and released.
- Estimate type, quantity, characteristics, timing, and availability of team, physical, and virtual resources using appropriate methods and calendars.
- Negotiate and select resources while documenting the schedule, cost, quality, and risk implications of constrained alternatives.
- Create conditions for high performance through shared purpose, roles, norms, trust, collaboration, autonomy, recognition, adaptability, and resilience.
- Monitor planned versus actual use, shortages, surpluses, downtime, productivity, waste, rework, inventory, and release timing.
- Tailor leadership and resource systems to development approach, team maturity, culture, virtual work, scarcity, well-being, industry methods, and sustainability.
Key concepts
Resource plan
An account of what people, equipment, and materials are needed and when.
Team leadership
Creating trust, capability, ownership, and clear responsibility.
Resource utilization
Comparing available capacity and actual use to identify shortages or waste.
Deeper understanding
Why it matters
Human leadership and physical or virtual resource control are related but explicitly different management problems.
Decision questions
- Which resource is scarce, shared, or unavailable at the moment its dependent work starts?
- Have the estimated capabilities actually been acquired and linked to the scheduled activities?
- Can team members describe the goal and raise a concern safely before it becomes a defect?
Teach it back
- Distinguish the responsibilities of the project manager, resource manager, team members, and suppliers in functional, matrix, contracted, and self-organizing settings.
- Plan how resources will be estimated, acquired, led, utilized, monitored, controlled, and released.
- Estimate type, quantity, characteristics, timing, and availability of team, physical, and virtual resources using appropriate methods and calendars.
Signals to notice
- Human leadership and physical or virtual resource control are related but explicitly different management problems.
- A booked resource is not necessarily usable: location, timing, condition, and competing assignments matter.
- Resource efficiency must be read with rework, downtime, and team resilience rather than utilization alone.
Section-by-section reading
Use the printed page references to read each section in the official publication, then explain the idea in your own words.
Key concepts: people, physical and virtual resources
Resources encompass project people as well as equipment, materials, facilities, infrastructure, software, licenses, services, information, and other physical or virtual assets. Availability, utilization, and maintenance all matter. Leading a team requires different skills from controlling stock or arranging a testing environment. The project manager helps form an effective group, while resource planning must account for competition with other projects and for constraints on when and where resources are needed. A nominal assignment is not evidence of available capacity. Efficient use also does not mean keeping every person or machine continuously busy; the question is whether the right capability is ready when work requires it and released when no longer needed.
Understand this item
Why it matters: Delivery depends on several resource types becoming available together; a named person, reserved machine, or purchased license is useless if it lacks capacity, access, or timing when dependent work begins.
Decision to make: Map each activity to the capability, asset, location, calendar, and readiness condition it needs, then manage the scarcest shared resource rather than maximizing everyone's utilization.
Do not confuse it with: Human resources need trust, motivation, feedback, and development, whereas physical and virtual assets need logistics, configuration, maintenance, utilization, and release control.
Teach it back: Explain why a fully allocated roster can coexist with a resource shortage, using an example in which one missing license or calibrated instrument blocks the whole task.
Apply it: A surveying team needs qualified operators, calibrated instruments, site access, data licenses, and a usable processing environment on the same day.
Check yourself: Which resource is scarce, shared, or unavailable at the moment its dependent work starts?
Plan, estimate, and acquire resources
Resource management planning sets the approach and management effort appropriate to project type and complexity, including competition for scarce resources. Estimation identifies the types, quantities, and characteristics needed, helping anticipate shortages, surpluses, and allocation risk. Acquisition then obtains and assigns people, physical assets, or virtual capacity to activities. A forecast resource need, a formal assignment, and a resource actually available at the required location and time are different states. The guide also points to the impact of unavailability on schedule, cost, quality, risk, and training. Coordinate resource estimates with cost estimates and activity plans rather than assuming the original team roster or supplier quotation is enough.
Understand this item
Why it matters: A resource estimate is only a forecast; value is protected only when required capabilities are actually secured and ready at the scheduled time and place.
Decision to make: Estimate types and quantities with the activity and cost plans, choose acquisition routes, reserve scarce capacity, and confirm access before the work window opens.
Do not confuse it with: Planning defines how resources will be managed, estimating predicts what is needed, and acquisition converts that need into a usable assignment; none of these states substitutes for the next.
Teach it back: Describe the evidence that would move two certified testers and a lab slot from estimated needs to genuinely available resources.
Apply it: Estimate two certified testers and a lab slot, secure the reservations, then verify access before a commissioning shutdown begins.
Check yourself: Have the estimated capabilities actually been acquired and linked to the scheduled activities?
Lead the team and build high performance
Leading the team combines management of processes and work with leadership through motivation, listening, influence, and enablement. The guide includes feedback, competency improvement, conflict resolution, issue escalation, and team changes. Common development foundations include a communicated vision and clear roles; high-performing teams also need open, safe communication and shared understanding. Style should reflect members' willingness and ability, not a fixed preference for direction or delegation. Productive collaboration is not proved by assigning tasks to named individuals. Team members must be able to surface problems and jointly address them without losing accountability for outcomes. Recognition and coaching can be as relevant as formal reporting in sustaining performance.
Understand this item
Why it matters: Clear assignments alone do not create coordinated performance; people must understand the goal, surface concerns safely, resolve conflict, and share responsibility for outcomes.
Decision to make: Adapt direction and delegation to team capability, establish roles and working norms, and use coaching, recognition, listening, and joint problem solving to strengthen performance.
Do not confuse it with: Managing work organizes tasks and accountability, while leadership builds motivation, trust, competence, and influence; high performance needs both rather than task control alone.
Teach it back: Explain how you would test whether a team has shared ownership instead of merely checking that every task has an individual assignee.
Apply it: A newly combined engineering team agrees on roles, holds short problem-solving sessions, and coaches junior inspectors rather than only issuing task orders.
Check yourself: Can team members describe the goal and raise a concern safely before it becomes a defect?
Monitor and control resourcing
This named process focuses on physical and virtual resources: verify availability, compare planned with actual usage, remedy shortages or surpluses, and release assets at the proper time. Team performance is addressed under Lead the Team, so equipment-utilization data should not be casually substituted for an individual performance assessment. The guide highlights practical consequences of failing to control assets: late critical equipment, low-quality material causing rework, excessive inventory cost, or stock too thin for demand. Review actual consumption before reallocating future capacity, and inform affected stakeholders of shortages. The appropriate target is reliable delivery with sensible utilization, not maximum inventory or a perfectly full calendar.
Understand this item
Why it matters: Late, poor-quality, overstocked, or underused assets can damage dates, cost, and quality even when the original resource plan looked sufficient.
Decision to make: Compare actual availability and consumption with the plan, investigate causes of shortages or surpluses, communicate impacts, correct the constraint, and release assets when no longer needed.
Do not confuse it with: Asset monitoring evaluates physical and virtual resource use; it should not be misused as an individual performance rating, which belongs within team leadership.
Teach it back: Given rising scrap, explain why inspecting material quality may be a better control response than adding another machine.
Apply it: After scrap rates rise, the team inspects incoming material quality and revises orders instead of merely renting another cutting machine.
Check yourself: Does actual asset usage match the plan, and is corrective action addressing the cause of the deviation?
Tailoring and interactions across domains
Tailor leadership and resourcing to development approach, project variability, team maturity, virtual work, and constraints. Experienced self-managing teams may need less direction; a new distributed team may need a charter, collaboration tools, deliberate relationship-building, and clearer working practices. High-variability adaptive work can require flexible resource agreements and lean control. Resource decisions interact strongly with scope, schedule, finance, stakeholder needs, and risk, and other projects may compete for the same assets. The guide explicitly relates resource estimates to cost estimates. A scarce specialist can create a schedule delay even if the financial budget is ample, while an apparently cheaper substitution may threaten quality and downstream acceptance.
Understand this item
Why it matters: Resource choices propagate through schedule, cost, quality, procurement, and risk, so a locally cheap or convenient choice can weaken the project as a whole.
Decision to make: Tailor leadership and agreements to team maturity, distribution, variability, and shared-resource competition, then update all affected forecasts when a constraint changes.
Do not confuse it with: A mature self-managing team may need broad decision space, while a new distributed team may need explicit norms, tools, overlap hours, and clearer boundaries.
Teach it back: Explain how a scarce specialist can delay a well-funded project and identify which plans and stakeholders must be updated.
Apply it: Two projects want the same environmental lab; leaders sequence samples and revise forecasts rather than assuming both can book it simultaneously.
Check yourself: How do shared-resource conflicts alter cost, dates, quality, and risk in both projects?
Check results: shared ownership, utilization, downtime, and efficiency
The guide's sample checks pair outcomes with evidence: team members know the vision, own results, collaborate and adapt; actual resource use is compared with planned use; downtime is judged against planned resource time; and productivity is assessed with suitable indicators. Physical efficiency may be visible in materials consumed, scrap, and rework, while procurement checks follow ordering, manufacture, and delivery. A single utilization percentage cannot establish team health or project success. Review whether members feel empowered and recognized alongside whether assets are acquired, available, and released efficiently. Choose measures that expose waste or interruption without encouraging unsafe shortcuts or inflated output at the expense of accepted results.
Understand this item
Why it matters: No single utilization number shows whether resources are creating accepted results; reliable performance requires evidence about team health, flow, waste, availability, and outcomes together.
Decision to make: Review ownership, collaboration, downtime, scrap, rework, procurement progress, and planned-versus-actual use as a balanced set, avoiding measures that reward unsafe busyness.
Do not confuse it with: High utilization can conceal queues, burnout, or defects, while some spare capacity can improve recovery and flow when the real goal is dependable delivery.
Teach it back: Propose a small evidence set that demonstrates both an empowered team and efficient asset use without treating constant busyness as success.
Apply it: A weekly review pairs machine downtime and scrap with delivery progress and a team discussion of unresolved handoff problems.
Check yourself: What evidence shows both a functioning team and efficient, reliable use of assets?
Apply it to a project
Regional warehouse automation A project must install conveyor controls in three warehouses without stopping operations. Controls engineers are scarce, robots arrive from an external vendor, testing licenses are limited, and the team spans four time zones. Plan Resource Management defines resource categories, a RACI, team norms, decision authority, acquisition routes, release criteria, safety requirements, and maintenance windows. Estimate Resources combines bottom-up crew estimates with production-rate parameters and calendars. The resource breakdown structure reveals that one testing license, not labor, is the binding constraint. Acquire Resources negotiates a second temporary license and preassigns the lead controls engineer to high-risk commissioning. A substitute robot model is rejected because its safety certification is not equivalent. Lead the Team creates overlap hours, rotates inconvenient meeting times, coaches site leads, and uses retrospectives and recognition. Performance is assessed at team level, including trust, handoff quality, and recovery from incidents. Monitor and Control Resourcing tracks robot delivery, license use, downtime, scrap, rework, and release dates. Value-stream mapping shows waiting for safety permits, so the permit workflow—not technician utilization—is improved. Good resource management finds the real constraint, protects people and compliance, and aligns assignments, calendars, logistics, and team conditions with delivery.
What to watch for
- Misconception: Resource management is staffing. Correction: The domain includes people plus equipment, materials, facilities, infrastructure, software, testing environments, licenses, services, information, and other virtual assets.
- Misconception: The project manager always controls resource selection. Correction: Functional or resource managers, matrix authority, collective agreements, subcontractors, partnerships, and procurement may constrain selection.
- Misconception: Team leadership and physical-resource control are the same process. Correction: Lead the Team addresses people and performance; Monitor and Control Resourcing focuses on physical and virtual resources.
- Misconception: Maximum utilization is always efficient. Correction: Excess utilization creates queues, fragility, errors, burnout, and slower flow. Optimize the system and outcomes, not one percentage.
- Misconception: A resource substitution solves an availability problem if headcount is unchanged. Correction: Different competency, features, cost, calendars, quality, or compliance may alter duration, budget, risk, and acceptance.
- Misconception: Virtual teams only need collaboration software. Correction: They also need trust-building, shared norms, accessible information, overlap rules, inclusive meetings, relationship time, and sometimes face-to-face contact.
Test your reasoning
Which process produces the team charter?
Show answer and reasoning
Plan Resource Management The charter is established while planning the resource and team approach, then used and updated as the team works.
Which process primarily monitors equipment, materials, software licenses, and facilities?
Show answer and reasoning
Monitor and Control Resourcing That process controls physical and virtual resource availability and usage. Team-member performance is addressed through Lead the Team.
A preferred engineer is unavailable. What is the best next action?
Show answer and reasoning
Assess alternatives and document competency, schedule, cost, quality, compliance, and risk impacts PMBOK 8 permits alternatives when criteria are not violated, but requires the consequences of different capabilities or costs to be acknowledged.
Why can 100% utilization reduce delivery performance?
Show answer and reasoning
It removes capacity for variability and creates queues, switching, and burnout Local utilization is not the same as system flow. A constrained system often needs slack and protected capacity.
Which combination best indicates a high-performing team?
Show answer and reasoning
Shared purpose, trust, collaboration, adaptability, autonomy, resilience, and recognition These characteristics align with the domain's high-performing-team factors; healthy teams can disagree and adapt rather than avoiding all conflict.
Study companion only; the official guide is available from PMI.