Resource questions are easy to underestimate. They look administrative — who does what, who is over-allocated, who signs off — so candidates skim them during study and lose points on exam day. The trouble is that resource scenarios sit across two domains at once. A question about an over-allocated developer is a scheduling problem; a question about the same developer refusing to attend stand-up is a people problem. The vocabulary overlaps, and the exam uses that overlap deliberately.
This guide covers the resource material that shows up most often in scenario questions. For each one the useful question is not the definition but what the scenario wants you to do next.
What the resource management plan actually holds
Before the techniques make sense, it helps to know where the answers live. PMP study material describes the resource management plan as the document covering how resources are identified, acquired, managed, and released, with components including roles and responsibilities, organization charts, a resource calendar, training needs, a recognition plan, and a release plan.
Two of those are worth memorizing because exam questions quietly test them:
- The resource calendar makes "the tester is unavailable in week six" a planning fact rather than a surprise. If a scenario treats a known unavailability as a crisis, the gap is in planning.
- The release plan answers "the work is done but the contractor is still billing." Releasing resources is a planned activity, not an afterthought at closure.
The exam also distinguishes team resources from physical ones. People are acquired, developed, and managed; equipment, materials, facilities, and infrastructure are acquired and then controlled. Questions about materials arriving late or being consumed faster than planned belong to controlling physical resources, and the right answer compares planned against actual usage before acting.
Responsibility assignment matrices and the RACI trap
A RACI chart assigns four roles per task: Responsible for doing the work, Accountable for answering for its completion, Consulted for input, and Informed for updates. The structural rule exam questions lean on is that each task has exactly one Accountable person, at least one Responsible person, and as few Consulted and Informed entries as the work allows.
That single-accountable rule is where most RACI questions live. The typical scenario does not ask you to build a matrix. It describes a symptom — two team leads each think the other is handling a deliverable, or a decision keeps getting reopened because three managers were consulted and none owns the outcome — and asks what the project manager should do. The answer is almost always to clarify the responsibility assignments, not to escalate, decide personally, or add a meeting.
Leveling versus smoothing: the distinction the exam cares about
This pair is the most mechanical thing in resource management and the most commonly confused. Both are optimization techniques applied to a schedule that already exists. They differ in what they are allowed to break.
Resource leveling responds to a hard constraint — a cap on hours per week, one specialist who cannot be in two places, a limited piece of equipment. Because the constraint must be respected, leveling is permitted to move activity dates, extend the project duration, and change the critical path.
Resource smoothing responds to a preference — a steadier workload rather than peaks and troughs. It moves work only within available float, so it does not extend the duration and does not change the critical path. The cost is that smoothing may be unachievable if there is not enough slack to absorb the peak.
| Leveling | Smoothing | |
|---|---|---|
| Driven by | A constraint to respect | A preferred even workload |
| Float | Not limited to float | Only within float |
| Duration | May be extended | Unchanged |
| Critical path | May change | Unchanged |
| Can it fail | No, but at schedule cost | Yes, if float is short |
Apply leveling first, then smooth whatever remains inside the float. On the exam, the tell is the wording. "No more than 40 hours per week is permitted" is a limit, so leveling. "The sponsor would prefer a steadier burn rate" is a preference, so smoothing. If a question asks what happens to the finish date and the technique named is smoothing, it does not move.
One more trap: a question may describe a resource conflict and offer schedule compression as an answer. Crashing and fast tracking address a duration problem, not an over-allocation problem.
Acquiring resources without inventing authority
Acquisition questions test how much power you think a project manager actually has. Three terms carry most of the weight.
Pre-assignment means resources were committed before the project formally started — people named in the charter, for instance. If a scenario says a key person was named there, you do not negotiate for them; you confirm availability and plan around their calendar.
Negotiation is the normal path in a matrix organization, where the project manager negotiates with functional managers, other project managers, and sometimes external organizations. When a question gives you a project manager who needs a resource belonging to another manager, the answer that goes around that manager is wrong, and so is the answer that escalates immediately. Negotiate first; escalate only when negotiation has demonstrably failed.
Virtual teams widen the talent pool and cut travel cost, at the price of time-zone coordination and harder cohesion. These questions ask what to do when a distributed team is not gelling, and they reward explicit communication agreements, relationship-building, and rotating meeting times over tool purchases.
Team charters and ground rules
A team charter is not a project charter. The project charter establishes stakeholder-level understanding of goals, constraints, funding, and milestones. A team charter covers how the team works together: members and roles, shared values, behavioral guidelines, ground rules for communication and tools, and the team's own conflict resolution and decision-making.
The exam-relevant point is ownership. PMP prep material on this task is consistent that the team creates its own charter, with the project manager acting as a guide who lets the team decide its way of working. The project manager facilitates, models the rules, and handles persistent violations — up to removing someone who repeatedly ignores agreed rules — but does not hand the rules down. So when a scenario presents a team arriving late to reviews or talking over each other, the better answer is to bring the team back to its ground rules or establish them together, not to issue a policy.
Ground rules are also meant to be living: if a rule no longer serves the work, the team revisits and removes it. An option that enforces an obsolete rule for consistency's sake is usually the distractor.
Why this material is worth a study session now
PMI's description of the exam that launched in July 2026 puts the domain weights at People 33%, Process 41%, and Business Environment 26%. Resource material straddles the first two: team development, ground rules, and conflict sit in People, while resource planning, optimization, and control sit in Process. That makes it a good return on a single study block, because the same concepts answer questions in two domains.
PMI also describes the refreshed exam as putting more emphasis on agile and hybrid delivery, and resource thinking shifts with it. On an adaptive team, "who is accountable" is more often answered by the team's own working agreements than by a matrix the project manager drew. When a scenario is clearly adaptive, prefer the answer that goes to the team and its agreements; when it is clearly predictive, prefer the answer that goes to the plan and the schedule.
A checklist for resource questions
Work through these in order when a scenario looks like a resource problem:
- People or physical resources? Control applies to physical resources.
- A constraint or a preference? Constraint means leveling; preference means smoothing.
- Does the question ask about the finish date or the critical path? Only leveling moves them.
- Is accountability ambiguous? Then the matrix is the subject, not the people.
- Does the resource belong to someone else? Negotiate before escalating.
- Is the approach adaptive? Route behavior questions through the team's own agreements.
The pattern across all six is the one that governs most situational questions on this exam: identify whose decision it actually is before deciding what to do.