September 7, 2026 · 7 min read
TL;DR: Options that add resources, hire, or bring in additional staff are keyed 6 times against 24 as distractors across this bank. The keyed cases all share two features: a measured shortfall that adding people can actually fix, and either authorization or the person who owns the trade in the room. The failures skip both.
"The project is behind, so add people" is the oldest wrong answer in project management, and Fred Brooks named it more than fifty years ago. The exam does not want you to recite Brooks's law. It wants you to notice when the scenario has, or has not, earned the right to spend headcount.
Across the 2,141 questions here, 30 answer options add resources, hire someone, or bring in additional staff. Six are keyed. What separates them is not agile versus predictive, and it is not team size. It is whether a number came first.
When the arithmetic says the project can afford the trade, and someone with authority is making it.
The cleanest case is an earned value question. The sponsor keeps commenting on cost. Planned value is $840,000, earned value is $795,000, actual cost is $755,000. Work both variances before choosing anything:
That combination is the whole answer. Less work has been done than planned, but it has cost less than the work was supposed to cost, so there is favourable cost variance sitting there to buy back schedule with. "Add resources to bring the project schedule back on track" is keyed. Drawing on the contingency reserve is the closest distractor and it fails on principle: reserves fund identified risks that have occurred, not routine schedule recovery, and there is a cost surplus to spend before any reserve gets touched.
Change the numbers and the answer changes with them. If the CPI were below 1, adding resources would be pouring money into a project already burning it, and the keyed answer would be somewhere else entirely.
Because they buy capacity instead of understanding.
| Distractor | What the scenario had not established |
|---|---|
| "Hire the resource anyway in order to achieve the project objectives" | Whether the hire was authorized at all |
| "Reassign the new hire's tasks to a more experienced team member" | Whether the new hire is actually underperforming |
| "Release the new hire and request a replacement through HR" | The same thing, irreversibly |
| "Escalate to senior management and demand they assign an additional resource" | Whether the shortfall needs a person or a decision |
| "Technical skills to handle the risk of adding resources" | That adding resources was the right response at all |
That new-hire scenario is worth reading closely. An experienced team member tells the project manager privately that a new colleague "doesn't seem to have the skills for this role" and suggests reassigning their tasks. The project manager has not observed the new hire's work. Three of the four options act on the report: reassign the tasks, release the person, or take no action because reassigning would be disruptive. The keyed answer observes the new hire's actual work against the role's expectations first.
What the project manager holds is one colleague's secondhand impression, which may be wrong, incomplete, or itself a symptom of friction between two people. Note that doing nothing is not the safe middle here either. If there is a real capability gap, verifying it is the only thing that would let the project manager close it.
Common trap: adding resources to an agile team without the product owner. In one bank question a team estimated at 50 points delivers 37 and then 35. Two answers are keyed: telling the product owner that the empirical data makes the release plan unachievable, and exploring the possibility of adding resources with the product owner. Pushing the team to hit the estimate and extending the sprint until 50 points are done are both distractors. The collaborative framing is what makes the resource option keyed rather than trapped, because the release trade-off between scope, schedule and cost belongs to the product owner. This bank explains that distinction instead of just marking the option wrong, which is what makes the near-miss options useful rather than annoying.
Is adding resources ever the correct answer on the PMP exam? Yes, when a measured schedule shortfall sits alongside favourable cost performance and the decision is made with whoever owns the trade. In this bank, add-resource options are keyed 6 times out of 30, and every keyed case has a number or an owner behind it.
Why is "add more people" usually a distractor? Because it treats headcount as a diagnosis. Most bank scenarios that offer it have not yet established what is causing the shortfall, so adding people commits cost and onboarding effort to a problem nobody has sized.
Can a project manager add resources to an agile team unilaterally? No. One bank question with a team delivering 37 and 35 points against an estimated 50 keys exploring the possibility of adding resources with the product owner, because the release trade-off between scope, schedule and cost belongs to them.
What does the exam want when someone reports a team member is underperforming? Verification before action. A bank question has an experienced colleague privately claim a new hire lacks the skills; the keyed answer observes the new hire's actual work against the role's expectations before deciding anything.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, with every wrong answer explained rather than just marked wrong, so an add-resources distractor tells you whether it failed on the diagnosis or on the authority. Start the free 20-question sample with no card and no signup.
Related: Removing the Difficult Team Member: 0 Keyed, 17 Distractors and RACI, Resource Assignment, and Acquiring a Team You Don't Control. The domain walkthrough is at /study/people.
Is adding resources ever the correct answer on the PMP exam?
Yes, when a measured schedule shortfall sits alongside favourable cost performance and the decision is made with whoever owns the trade. In this bank, add-resource options are keyed 6 times out of 30, and every keyed case has a number or an owner behind it.
Why is 'add more people' usually a distractor?
Because it treats headcount as a diagnosis. Most bank scenarios that offer it have not yet established what is causing the shortfall, so adding people commits cost and onboarding effort to a problem nobody has sized.
Can a project manager add resources to an agile team unilaterally?
No. One bank question with a team delivering 37 and 35 points against an estimated 50 keys exploring the possibility of adding resources with the product owner, because the release trade-off between scope, schedule and cost belongs to them.
What does the exam want when someone reports a team member is underperforming?
Verification before action. A bank question has an experienced colleague privately claim a new hire lacks the skills; the keyed answer observes the new hire's actual work against the role's expectations before deciding anything.