4.4. Plan and Manage Resources
💡 First Principle: Resource planning fails most often not from under-forecasting quantity, but from ignoring availability constraints (shared resources, competing project demands) that make a technically-correct plan practically unworkable.
Enablers: define and plan resources based on requirements, and manage/optimize resource needs and availability on an ongoing basis.
This is a deliberately compact task (only 2 enablers) compared to others — reflecting that in the 2026 ECO, detailed resource estimation techniques are covered more as part of task 4.1's "estimate work effort and resource requirements," while this task is about the ongoing management and optimization discipline.
Plan from the actual requirements, in order
Resource planning for a phase follows a sequence, and the exam tests it directly:
Start from what this work needs. Copying the resource plan from a previous, superficially similar phase skips the first step, and the risk is that real differences in scope, technology, or pace go unaccounted for — leaving needs under- or over-estimated.
Quantity is not availability
A plan can list the right skills in the right numbers and still be unworkable, because the specific people who hold those skills are already committed elsewhere for the same dates. Shared specialists, matrix reporting, and competing project demands are availability constraints, and a sound plan names them explicitly. If a resource you need is fully committed to another internal project, the usual move is a negotiated reallocation with that project's manager — not simply assuming they will appear.
Optimize before you acquire
Resource optimization is the term for adjusting an existing plan — leveling workload, reallocating people, retiming work — to make the best use of what you already have before acquiring anything new. When a key person is unexpectedly out for two weeks, your first step is to evaluate those optimization options; buying or hiring comes later, if at all.
Two optimization techniques are easily confused:
| Technique | What it does | Effect on the schedule |
|---|---|---|
| Resource leveling | Adjusts start and finish dates based on resource constraints, to balance demand with supply | Can change the critical path and push the end date out |
| Resource smoothing | Adjusts activities so resource demand does not exceed predefined limits, using only available float | Critical path and end date do not move |
⚠️ Exam Trap: When a scarce, expensive resource is available only during a fixed window, the answer is leveling — shifting the dependent activities' dates so they fall inside that window. Smoothing cannot help if the fix requires moving work beyond its float.
Choosing internal or external options
When a real gap remains, match the option to the nature of the need:
- Internal: reassign someone from a lower-priority project, or train an existing team member in a skill you will need repeatedly on future work.
- External: a short-term specialist contractor for a temporary spike in demand, a time-boxed consultant for a one-time specialized capability, or a vendor delivering a discrete piece of work (which then becomes a procurement decision — see 4.5).
Internal options build lasting capability but take ramp-up time; external options are fast but cost more and leave little behind when they end.
Keep managing it
A resource plan built at kickoff and never revisited will drift out of date. Team composition, priorities, and availability all shift during a project, which is why the ECO frames this enabler as ongoing management and optimization. In adaptive teams the same discipline shows up as stable, dedicated team membership and capacity-based planning each iteration.
⚠️ Exam Trap: Answering purely from a "get more resources" instinct when a scenario describes a resource shortfall. PMI more often expects optimization of existing resource allocation (reprioritization, cross-training, timing adjustments) as the first-line response, with acquiring new resources as a later-order option.
