PMP domain - 42% of the exam

People

People is 42% of the PMP exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

126
Practice questions
4
Objectives
95
Medium
31
Hard

Where people go wrong

  • Imposing ground rules instead of facilitating them

    The wrong answers have the project manager write the rules, or hand the question upward. They issue ready-made rules, publish a manager-imposed policy, or escalate to the sponsor, and each skips the team's own agreement. Ground rules gain commitment because the team shapes them, so the correct answer is a facilitated session where members draft and agree rules for meetings, communication and decisions. Rules handed down invite the command-and-control stance a self-organising team works against.

    See it in a sample question
  • Delegating a task without matching authority

    Delegation fails in the wrong answers because responsibility moves without authority, or authority moves without limits. One option keeps sign-off on every action, so the approval load stays with the project manager. Another hands everything over with no boundaries or reporting. Effective delegation transfers the task together with matching decision authority, with the scope, decision limits and reporting agreed beforehand, while the project manager remains accountable for the outcome.

    See it in a sample question
  • Delaying or mismatching recognition

    The wrong answers hold recognition back or fit it badly. They defer it to an annual appraisal or the closeout review, which weakens the link between behaviour and acknowledgement. They also stage a public ceremony or cash bonus for someone who has said they prefer quiet peer respect. The correct answer acknowledges the specific contribution promptly, in a form the individual values, and names the effect it had on the project.

    See it in a sample question
  • Treating training as an event, not a gap closed

    The wrong answers treat training as an event instead of a response to a measured gap. They send documents, run a single session or demonstration, or ask for sign-off, and none of these shows that stakeholders can operate the system. The correct answer first compares the competencies the system requires with what stakeholders can do now, then plans targeted training to close those specific gaps before go-live.

    See it in a sample question
  • Resolving conflict by forcing, smoothing or escalating

    When two people disagree over a technical choice or the priority of a change, the wrong answers settle it by authority, by avoidance or by a quick trade. The project manager picks a winner, smooths the tension over, splits the difference, or escalates before trying anything else. The correct answer brings the parties together to surface the interests behind each position and work towards a solution both support, which resolves the cause and keeps the relationship intact.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free samplePeoplemedium

An agile team of eight has just formed to build a customer portal. Two members already disagree loudly over whether to review each other's code before merging, and the sponsor is pressing for early velocity. The project manager wants to prevent these clashes from recurring. What is the BEST way to establish how the team will work together?

  • AWrite a set of working agreements yourself based on best practice and circulate them for the team to follow.
  • BAsk the sponsor to decide the code-review policy so the team can stop arguing and focus on velocity.
  • CFacilitate a session where the team collectively drafts and agrees its ground rules, including how code review will be handled. Correct
  • DLet the two members settle the code-review question privately and adopt whatever they agree.
Team ground rules are most effective when the whole team creates and agrees them together rather than having them imposed. Collaboratively developed ground rules produce shared ownership and accountability, which is what makes team members actually follow the agreed behaviours; a leader-written or escalated ruleset lacks that buy-in and tends to be disregarded.

Why A is wrong: Author-imposed rules look efficient, but a self-organising team commits to standards it helped shape; rules handed down are more likely to be ignored, and this does not resolve the specific disagreement.

Why B is wrong: Escalating to the sponsor may feel decisive, but ground rules are the team's responsibility, not the sponsor's, and outsourcing the decision removes the ownership that makes rules stick.

Why C is correct: Ground rules that the team creates together carry shared ownership, so members are far more likely to honour them; agreeing the review approach up front settles the recurring clash at its source.

Why D is wrong: Letting the pair resolve it avoids a group discussion, but ground rules affect the whole team, and a private deal between two members will not bind the other six or build collective buy-in.

Free samplePeoplemedium

Midway through a predictive programme, the project manager assigns a senior engineer to lead the integration workstream but continues to make every supplier and design call themselves, leaving the engineer to relay decisions without any authority. The engineer grows frustrated and stakeholders are confused about who is actually in charge. What should the project manager do to delegate effectively?

  • AGrant the engineer the decision authority that matches the responsibility, communicate the delegated scope to stakeholders, and then step back from those calls. Correct
  • BReassign the workstream to a different engineer, on the assumption that the current lead is not asserting themselves strongly enough.
  • CKeep the arrangement but tell stakeholders to route all questions through the project manager to remove the confusion over who decides.
  • DAsk the sponsor to define, in the programme charter, exactly which decisions the engineer may take on the project manager's behalf.
Delegate by pairing responsibility with matching authority and communicating the delegated scope so the delegate can genuinely act. Delegation fails when responsibility is given without authority; granting decision rights that match the role and publishing that scope is the mechanism that lets a delegate act and removes the who-decides confusion.

Why A is correct: Correct: real delegation pairs responsibility with matching authority and makes that scope visible to stakeholders, which resolves the confusion and empowers the lead.

Why B is wrong: Swapping people blames the individual, but the confusion stems from responsibility being handed over without authority, so a new lead would hit the same wall.

Why C is wrong: Centralising queries does clarify the chain, but it does so by cancelling the delegation entirely, which wastes the lead role and keeps the project manager as the single decision point.

Why D is wrong: Involving the sponsor sounds rigorous, but setting a delegate's day-to-day decision scope is the project manager's own job, so this escalates a call they should make and delays the fix.

Free samplePeoplemedium

A hybrid product team hit a difficult integration milestone on time, and one tester quietly did the unglamorous work of building the regression harness that made the smooth cutover possible. At the next review the project manager wants to recognise the contribution in a way that reinforces the behaviour and fits the individual. What is the best approach to recognising this contribution?

  • AAcknowledge the tester's specific contribution promptly and in a form the individual values, making clear which behaviour made the outcome possible. Correct
  • BWait until the project's final closeout so that all contributions across the whole delivery can be acknowledged together in a single ceremony.
  • CGive the whole team an identical financial bonus regardless of individual contribution to avoid any appearance of favouritism.
  • DMention in passing that the milestone went well and move on, on the assumption that hitting the date is its own reward for a professional team.
Recognition works best when it is prompt, specific to the contribution, and tailored to what the individual values. Recognising an individual contribution close to the event, naming the behaviour that produced the result, and matching the reward to the person's preferences reinforces that behaviour far more effectively than delayed or uniform rewards.

Why A is correct: Correct: timely, specific recognition tailored to what the individual values reinforces the desired behaviour and is more effective than delayed, generic, or one-size-fits-all rewards.

Why B is wrong: Batching recognition to closeout feels fair and tidy, but delaying it for months weakens the link between the behaviour and the acknowledgement, so it does little to reinforce the effort now.

Why C is wrong: Equal treatment avoids friction, but a flat bonus that ignores the specific effort fails to recognise the individual contribution the objective calls for and can demotivate those who went further.

Why D is wrong: Trusting professionals to be self-motivated has some truth, but a vague passing remark neither names the contribution nor reinforces it, so a valuable behaviour goes unrecognised.

Free samplePeoplemedium

On a predictive project, a key business stakeholder will need to operate a new reporting tool at go-live but has never used similar software. The project manager wants to ensure the stakeholder is adequately prepared. Which approach is BEST?

  • AProvide the full user manual near go-live so the stakeholder can read it before the tool is handed over.
  • BAssess what the stakeholder must be able to do, then plan and deliver targeted training and practice before go-live so they are competent at handover. Correct
  • CAssume the stakeholder will pick up the tool quickly since modern software is intuitive, and offer help only if problems appear.
  • DDelegate all training responsibility to the software vendor and remove it from the project's concern.
Ensure stakeholders are adequately trained by assessing the capability needed and delivering targeted practice before handover. Adequate training is achieved by defining the specific capability the stakeholder must have, then planning and delivering hands-on training and practice ahead of go-live, so competence is confirmed at handover rather than left to documentation or chance.

Why A is wrong: Handing over documentation looks like enabling self-service, but a manual alone rarely builds an operating skill and leaving it to go-live gives no time to practise.

Why B is correct: Identifying the required capability and delivering targeted training with practice before go-live ensures the stakeholder is adequately trained, which is exactly the objective's intent.

Why C is wrong: Assuming intuitiveness and reacting to problems seems low-cost, but it leaves a foreseeable competency gap to chance and risks a failed handover.

Why D is wrong: Using vendor expertise can help, but fully offloading the outcome without confirming the stakeholder's readiness abdicates the project manager's accountability for adequate training.

Free samplePeoplehard

On an agile software project, two senior developers disagree sharply about which data-access pattern the team should adopt, and the tension is now spilling into daily stand-ups and slowing delivery. Each has technical merit on their side and neither will concede. What is the BEST way for the project manager to handle the conflict?

  • AHave each developer submit their preferred pattern in writing so the project manager can pick the stronger option and direct the team to use it.
  • BEncourage both developers to focus on their shared goal, downplay the technical disagreement, and let the friction settle so the team can keep delivering.
  • CAsk the two developers to meet with the project manager, surface the underlying concerns behind each position, and work toward a solution that both can support. Correct
  • DSplit the difference by having the team use one pattern for existing modules and the other pattern for all new modules going forward.
Collaborating to address the underlying concerns of both parties produces the most durable resolution to a technical conflict. Collaborate/problem-solve works because it treats the disagreement as a shared problem to be solved on the merits, incorporating both parties' concerns so the outcome is jointly owned and the working relationship stays intact, unlike forcing, smoothing, or compromise.

Why A is wrong: This looks decisive and fast, but it is a forcing approach that imposes a winner and a loser; the losing developer is likely to stay disengaged, so the underlying tension is not resolved.

Why B is wrong: Emphasising harmony is tempting because it calms the room quickly, but this is smoothing; it hides the real disagreement rather than resolving it, so the conflict tends to resurface later.

Why C is correct: This is the collaborate/problem-solve approach: it addresses the root concerns openly and seeks a solution both parties own, which durably resolves the conflict and preserves the relationship.

Why D is wrong: A middle path feels even-handed, but this is compromise, where each side gives something up and the team may end up with an inconsistent design that satisfies no one and adds maintenance cost.

Other domains in this exam

See also the PMP cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.