What you must be able to do. Read a team or stakeholder scenario and pick the action a servant leader would take to build, empower, and align people: coach and remove impediments, resolve conflict by collaborating, and engage stakeholders rather than command them.
In one sentenceLeading and building a high-performing team: setting a shared vision and ground rules, empowering and supporting the team, resolving conflict by collaborating, negotiating agreements, and engaging stakeholders including virtual teams.
Recall check: answer these from memory first
- A team conflict surfaces. What is the preferred resolution approach, and what should the project manager try before escalating to the sponsor?
- What does it mean to empower a self-organising team, and how does that differ from abdicating responsibility for the result?
- Which leadership style does the 2021 outline favour, and how does that change your answer on a command-and-control distractor?
What it tests. Whether you can lead people the way the 2021 outline expects: build and empower a high-performing team, set a shared vision and ground rules collaboratively, and adapt your leadership style to the team's situation. It covers managing and resolving conflict, negotiating project agreements, applying emotional intelligence, mentoring stakeholders, supporting self-organising teams, and engaging virtual and distributed teams so that everyone stays aligned with the project's goals.
How to study it. Anchor every People question to servant leadership and collaboration: the project manager coaches, facilitates, and removes impediments rather than directs. For any conflict scenario, learn why collaborate and problem-solve is the preferred resolution mode and why forcing, smoothing, and withdrawing are usually the distractors. Practise spotting premature escalation: the exam nearly always wants the project manager to try to resolve an issue with the people involved before taking it to the sponsor. Study the difference between delegating authority to a self-organising team and abdicating responsibility for the outcome.
Easy to confuse
- Collaborate/problem-solve versus forcing or smoothing. Collaborate/problem-solve addresses the root cause and produces a durable, win-win outcome, and it is the outcome the exam prefers. Forcing imposes one party's view and smoothing papers over the difference; both leave the real disagreement unresolved, so they are the distractors unless the scenario makes speed or a trivial issue decisive.
- Resolve it yourself versus escalate to the sponsor. The PMP answer almost always has the project manager engage the people involved and attempt resolution first, because escalation is a later step reserved for issues genuinely outside the team's authority. An option that jumps straight to the sponsor is usually premature escalation and the wrong choice.
- Empowering a team versus abdicating responsibility. Empowering delegates decision-making authority to the lowest responsible level while the project manager stays accountable for the outcome and keeps removing impediments. Abdicating hands over authority and then disengages; the option that has the project manager walk away from the result is the trap.
Worked example from the PMP bank
lock_openFree samplePeoplemedium
A newly formed agile team is midway through its first two sprints and members keep interrupting one another in stand-ups, with two engineers openly disagreeing about who owns integration testing. Delivery has slowed and morale is dipping. Applying servant leadership, what should the project manager do FIRST?
- AFacilitate the team in agreeing a set of ground rules covering communication, decision-making, and how work is shared.check_circle Correct
- BAssign each disputed task to a named individual and publish a fixed responsibility list so the arguments stop immediately.
- CEscalate the conflict to the sponsor and ask for a ruling on which engineer should lead integration testing.
- DWait for the team to settle by itself over the coming sprints, since storming behaviour usually passes without intervention.
A servant leader helps a storming team agree its own ground rules rather than imposing assignments or escalating. Ground rules set team-owned expectations for behaviour and collaboration, which resolves the storming-stage friction at its source and lets the self-organising team move toward performing without command-and-control intervention.
Why A is correct: The friction is typical of the storming stage, and a servant leader responds by helping the team surface and agree its own ground rules, which gives shared, durable norms the team owns rather than a manager's edict.
Why B is wrong: Imposing assignments is a command-and-control reflex that removes the self-organising team's ownership; it may quiet the symptom but does not address the missing agreement on how the team will work together.
Why C is wrong: Escalating a normal team-formation dispute is premature and undermines the team's ability to self-organise; the sponsor is not close enough to the work to make a better call than the team can.
Why D is wrong: Storming does often pass, but passive waiting while delivery and morale slide neglects the servant leader's duty to remove impediments and help the team reach performing sooner.
What you must be able to do. Given a delivery scenario, pick the step that follows the right process at the right time: plan and control scope, schedule, budget, quality, and risk, choose the fitting approach, and manage change through the proper mechanism.
In one sentenceDoing the technical work of delivery: planning and controlling scope, schedule, budget, quality, and risk, choosing predictive, agile, or hybrid, integrating the plan, and managing change, procurement, and closure through the right process.
Recall check: answer these from memory first
- A change request arrives mid-project. What does the project manager do before the change is implemented, and through which process?
- List the threat responses and the opportunity responses, and say which one fits an opportunity you want to make more likely.
- What is the difference between validate scope and control quality, and which comes first?
What it tests. Whether you can run the delivery mechanics correctly and in the right order: plan and manage scope, schedule, budget, and resources, decompose work into a work breakdown structure, and measure progress with techniques such as earned value. It covers planning and managing quality and risk, selecting the appropriate methodology (predictive, agile, or hybrid), integrating the subsidiary plans, and executing with the urgency to deliver value while managing communications, changes, issues, procurement, and orderly closure.
How to study it. This is the largest domain, so give it the most time, and study it as sequences rather than isolated facts. Learn the correct order of steps so you can catch questions where an action is right but premature: assess a change before implementing it, analyse a risk before choosing a response, control quality for correctness before validating scope for acceptance. Know the risk responses cold and which apply to a threat (avoid, transfer, mitigate, accept, escalate) versus an opportunity (exploit, share, enhance, accept). Be able to compute and interpret the core earned value measures, and be ready to tailor the approach to a predictive, agile, or hybrid context the stem establishes.
Easy to confuse
- Validate scope versus control quality. Control quality is internal and checks correctness against requirements before a deliverable is shown to the customer; validate scope is the customer formally accepting the deliverable. The exam expects quality to be controlled first, so an option that seeks customer acceptance of unverified work is the trap.
- Threat response versus opportunity response. Threats use avoid, transfer, mitigate, accept, or escalate; opportunities use exploit, share, enhance, accept, or escalate. The classic distractor applies a threat verb to an opportunity or vice versa, for example mitigating an opportunity you actually want to enhance, so match the verb to whether the risk is bad or good.
- Scope creep versus gold plating. Scope creep is uncontrolled change entering from outside without going through change control; gold plating is the team adding unrequested extras. Both are wrong, but the fix differs: creep is handled by enforcing integrated change control, while gold plating is prevented by delivering only the agreed scope. Adding unrequested features is never the PMP answer.
Worked example from the PMP bank
lock_openFree sampleProcesshard
A project depends on a specialised soldering process that the team has never performed, and analysis shows a real chance the in-house attempt will fail and delay the schedule. A certified subcontractor will perform the same work under a fixed-price contract that makes the vendor liable for rework. Which risk response does engaging that subcontractor represent?
- ATransfer, because a fixed-price contract shifts the financial consequence of the threat to a third party better able to bear it.check_circle Correct
- BMitigate, because the fixed-price contract reduces the probability that the soldering defect will occur on the project.
- CAvoid, because using a subcontractor removes the soldering scope and the associated threat from the project entirely.
- DAccept, because the team acknowledges the threat and relies on the subcontractor to deal with the outcome if it happens.
Recognise that shifting a threat's impact and ownership to a third party through a contract is the transfer response. Transfer is the threat response that reassigns the impact and ownership of a risk to a third party, commonly through insurance, warranties, or fixed-price contracts, while the underlying threat continues to exist rather than being removed or reduced.
Why A is correct: Transfer moves the impact of a threat, together with ownership of the response, to a third party without eliminating the threat. A fixed-price contract with rework liability is a textbook transfer mechanism.
Why B is wrong: Mitigation lowers the probability or impact while the team retains ownership of the threat. Here ownership of the consequence, including rework liability, passes to a third party, so the response is transfer rather than mitigation.
Why C is wrong: Avoidance eliminates the threat, often by removing or changing the scope. The soldering work still happens and the threat still exists; it has simply been moved to a party better able to bear it, which is transfer.
Why D is wrong: Acceptance takes no proactive action to change exposure and is tempting because the team is no longer doing the work. Signing a contract that reassigns liability is a deliberate proactive action, so it is transfer.
What you must be able to do. Read a scenario about compliance, benefits, or external change and pick the action that keeps the project compliant, tied to its business case, and adapting to shifts in the organisation and the market.
In one sentenceConnecting the project to the wider organisation: planning and managing compliance, delivering and measuring benefits and value against the business case, and responding to external change and organisational change.
Recall check: answer these from memory first
- Who owns benefit realisation after the project closes, and what must be in place to know the benefits were achieved?
- An external regulatory or market change occurs mid-project. What does the project manager assess first, and what might they recommend?
- Why is a project's success ultimately judged against its business case rather than only against scope, schedule, and cost?
What it tests. Whether you can keep the project aligned to the business it serves: plan and manage project compliance by identifying requirements, classifying compliance categories, and weighing the consequences of noncompliance. It covers evaluating and delivering benefits and value, confirming benefits are identified and owned and that a measurement system tracks them, and assessing external business-environment changes and organisational change so their impact on scope and adoption is managed.
How to study it. This is the smallest domain by weight, so study it for its distinctive ideas rather than breadth. Fix the benefits chain in mind: a project is approved against a business case, benefits often accrue after the project ends, and someone must own ongoing benefit realisation with a measurement system in place. Learn to treat compliance as something you identify, classify, and plan for, not something you bolt on late. For external and organisational change, practise assessing impact on scope and backlog first and recommending options, and remember that supporting adoption of the change is part of delivering value.
Easy to confuse
- Deliverables and outputs versus benefits and value. Outputs are what the project produces; benefits and value are the outcomes the organisation gains from using them, often after closure. An option that declares success on shipping the deliverable while ignoring whether the benefit was realised or measured is the distractor.
- Compliance requirement versus a nice-to-have quality target. A compliance requirement is mandatory, driven by regulation, safety, or contract, and noncompliance carries real consequences the project must plan for. A quality target is negotiable against cost and schedule. The exam expects mandatory compliance to be treated as non-optional, not traded away.
- Assess impact first versus react to an external change. When the business environment shifts, the project manager first assesses and prioritises the impact on scope and backlog, then recommends options such as a schedule or cost change. An option that immediately changes the plan, or that ignores the change, skips the assessment step the exam wants.
Worked example from the PMP bank
lock_openFree sampleBusiness Environmentmedium
A project manager is initiating a predictive project that will process the health records of hospital patients in a jurisdiction that has recently introduced strict data-protection legislation. The team is eager to begin design work. What should the project manager do FIRST?
- ABegin the technical design and schedule a compliance check once a working prototype is available for the team to review.
- BAsk the sponsor to confirm that the compliance requirements documented on the organisation's previous health project still apply to this one.
- CIdentify the specific regulatory and organisational compliance requirements that apply, and build them into the project management plan.check_circle Correct
- DEscalate to the legal department and pause all project activity until they deliver a full written interpretation of the legislation.
Identify applicable regulatory and organisational compliance requirements during initiation and integrate them into the project management plan. Compliance requirements shape scope, quality standards, and risk. Establishing them before design begins prevents costly rework and ensures the plan is built to meet legal and organisational obligations from the start.
Why A is wrong: This feels efficient because it keeps the team busy, but deferring compliance until a prototype exists risks building a design that has to be reworked to meet legal requirements identified too late.
Why B is wrong: Reusing prior requirements looks like sensible tailoring, but it assumes the old requirements are complete and current when new legislation may impose obligations the earlier project never faced.
Why C is correct: Identifying the applicable compliance requirements at the outset lets the project manager fold them into scope, quality, and risk planning before design decisions are made, which is the proactive process-following action.
Why D is wrong: Consulting legal is reasonable, but halting the entire project and waiting for an exhaustive interpretation escalates too far and stalls work the project manager could progress while requirements are being clarified.