PMP (PMBOK 7) · Domain 1 of 3

PMP (PMBOK 7) Domain 1: People

People is a third of the July 2026 PMP exam: shared vision, conflict, team leadership, stakeholder expectations, knowledge transfer and communication. Here each task is tied to the PMBOK 7 principles and performance domains that explain why the best answer is best.

Exam weight
33%
Official tasks
8
Estimated questions estimate
~59
Suggested study time estimate
40–55 hrs

About 23 min read Reviewed October 2026

Overview

The People domain covers the human side of running a project: building a common vision, resolving conflict, leading and empowering the team, engaging and aligning stakeholders, keeping customers' expectations on track, moving knowledge to the people who need it, and communicating in a way that supports governance. The July 2026 outline compresses these into eight tasks, down from fourteen in the 2021 version, so each task now carries broader judgment.

Studying it through PMBOK Guide 7th Edition gives the reasoning behind the answers. Four principles do most of the work here (Create a collaborative project team environment, Effectively engage with stakeholders, Demonstrate leadership behaviors, and Focus on value), and two performance domains, Team and Stakeholder, describe the outcomes PMI expects. Process decisions in Domain 2 and governance or change decisions in Domain 3 usually succeed or fail on the people work covered here.

How it's tested

People questions are short situational scenarios: a team member is disengaged, two leads disagree, a sponsor's expectations drift, or a stakeholder was never consulted. Most ask what the project manager should do FIRST, NEXT, or what is BEST. Expect predictive, agile and hybrid settings, and expect several options that are all reasonable actions in the wrong order.

  • Understand before acting

    The correct option investigates, talks privately, or analyzes the stakeholder or conflict source before any resolution, escalation, or change. Options that jump to a fix assume facts the scenario has not given you.

  • Empower, do not direct

    In agile or hybrid teams the best answer coaches the team to solve the problem or lets the product owner decide priorities. The project manager removing autonomy, assigning tasks, or deciding scope for the team is usually a distractor.

  • Engagement gap to plan

    The scenario reveals a stakeholder whose current engagement (unaware, resistant, neutral) differs from what is needed. The answer updates the stakeholder register or engagement plan and tailors communication, rather than sending more of the same reports.

Reasoning it through

A hybrid team's two senior developers argue in stand-ups about an architecture choice, and velocity is falling. Options: escalate to the sponsor, decide yourself, tell them to compromise, or meet them to understand both positions and facilitate a decision against the agreed technical criteria. The scenario signals an open, task-based conflict between capable people, so collaborate/problem-solve is the target mode. Facilitating after understanding the source reflects the Team principle and leaves ownership with the team.

Tasks 8

Official tasks from the PMI outline, in outline order.

1.1 Develop a common visionCreate, promote and refresh a shared picture of what the project is for.
What it means
The project manager makes sure key stakeholders and the team hold the same view of the outcome and its value, keeps that vision visible, updates it when conditions change, and traces misunderstandings back to their root cause.
What to understand
A vision is about the outcome and value, not the scope list; in agile settings it often lives in a product vision statement or team charter. PMBOK 7 lens: Demonstrate leadership behaviors (leaders communicate vision) and Focus on value, with the Stakeholder performance domain outcome of agreement on project objectives.
How it shows up
Team members prioritize features in conflicting directions or a stakeholder rejects a deliverable that met the specification. The clue is that people disagree on why the work exists, so revisiting the vision with them comes before re-planning tasks.
Common confusion
Candidates treat a vision problem as a scope or requirements problem and reach for change requests, when the real gap is that stakeholders never agreed on the intended outcome.
1.2 Manage conflictsFind the source and context of conflict and apply an agreed resolution approach and ground rules.
What it means
The project manager identifies what the conflict is about (task, process, priorities, resources, personality), considers the context such as urgency and relationships, applies a resolution strategy the parties accept, and maintains ground rules in the team charter.
What to understand
The five classic modes are collaborate/problem-solve, compromise/reconcile, smooth/accommodate, force/direct and withdraw/avoid; collaboration is the default when time allows and the relationship matters, while forcing fits only emergencies or safety issues. PMBOK 7 lens: Create a collaborative project team environment, and the Team performance domain outcome of shared ownership.
How it shows up
The scenario names who is in conflict, about what, and how urgent it is. Private, early, direct conversation and resolution by the people involved is usually best; a ground-rule violation points to the team charter.
Common confusion
Compromise is not the best mode just because it sounds fair: each side gives something up, so it is a fallback when collaboration cannot find a solution that meets both needs.
1.3 Lead the project teamSet expectations, empower, solve problems and choose a fitting leadership style.
What it means
The project manager establishes team-level expectations and clear roles, represents the team's voice to the organization, values diverse skills and perspectives, removes obstacles to problem solving, and adapts leadership style to the team's maturity and situation.
What to understand
Servant leadership (shield the team, remove impediments, coach, grow people) is PMI's default in adaptive settings; situational leadership matches directing or delegating to competence and commitment, and Tuckman's stages (forming, storming, norming, performing, adjourning) tell you what the team needs now. PMBOK 7 lens: Demonstrate leadership behaviors, with leadership exercised by anyone on the team, not only the project manager.
How it shows up
A new team member struggles, a high performer is overloaded, or the team keeps waiting for instructions. The answer develops capability, clarifies roles (for example with a RACI chart), or delegates decisions to the team.
Common confusion
Servant leadership does not mean doing whatever the team asks or avoiding hard conversations; the leader still sets expectations and addresses underperformance, but by coaching first.
1.4 Engage stakeholdersIdentify and analyze stakeholders, tailor communication, and build trust and influence.
What it means
The project manager identifies everyone who affects or is affected by the project, analyzes their power, interest, influence and attitude, executes the stakeholder engagement plan, and builds the trust needed to align their needs with project objectives.
What to understand
Identification starts early and continues all project long, because stakeholders change. Tools include the power/interest grid, salience model (power, legitimacy, urgency) and the engagement assessment matrix comparing current with desired levels (unaware, resistant, neutral, supportive, leading). PMBOK 7 lens: Effectively engage with stakeholders, and the Stakeholder performance domain sequence identify, understand and analyze, prioritize, engage, monitor.
How it shows up
A late-discovered stakeholder demands changes, or an influential manager is quietly resistant. The best response adds or updates them in the stakeholder register, analyzes their concerns, and engages them directly before acting on their demands.
Common confusion
Engagement is two-way and relationship-based; distributing status reports is communication, not engagement, and does not move a resistant stakeholder toward supportive.
1.5 Align stakeholder expectationsCategorize stakeholders, surface their expectations and facilitate alignment.
What it means
The project manager groups stakeholders, makes their expectations explicit, brings parties with competing expectations together to reach a shared position, and uses mentoring opportunities to build understanding.
What to understand
Alignment is about making conflicting expectations visible and resolving them in a facilitated forum before they become rejected deliverables or change requests; categorizing helps decide who must be in the room. PMBOK 7 lens: Effectively engage with stakeholders and Focus on value, since expectations are judgments about value.
How it shows up
Two department heads expect different benefits from the same release. The best answer facilitates a joint session against the business case or vision, rather than meeting each separately and promising both.
Common confusion
Candidates confuse aligning (getting stakeholders to a shared set of expectations, usually early) with managing (keeping delivered outcomes matched to agreed expectations over time, task 1.6).
1.6 Manage stakeholder expectationsKeep outcomes matched to internal and external customer expectations and monitor satisfaction.
What it means
The project manager identifies what internal and external customers expect, keeps delivered outcomes aligned with those expectations as work proceeds, and monitors satisfaction so drift is caught and addressed.
What to understand
Satisfaction is measured, not assumed: demos and reviews, acceptance feedback, surveys or net promoter score give early signals. PMBOK 7 lens: the Delivery performance domain lists stakeholder satisfaction as a delivery outcome, and the Measurement performance domain supplies the indicators.
How it shows up
A customer says the product works but is not what they hoped for, late in a predictive project. The clue is drift without a formal change; the answer involves reviewing feedback and agreed acceptance criteria with the customer rather than silently adding features.
Common confusion
Gold plating (adding unrequested extras to please the customer) is not managing expectations; it adds cost and risk and bypasses change control.
1.7 Help ensure knowledge transferIdentify, gather and share the knowledge the project depends on.
What it means
The project manager identifies knowledge critical to the project, gathers it from people and records, and builds an environment where people share it, including at handoffs and when team members leave.
What to understand
Explicit knowledge (documents, procedures, data) can be codified; tacit knowledge (experience, judgment, relationships) moves through pairing, shadowing, communities of practice and conversations. PMBOK 7 lens: the Project Work performance domain includes managing knowledge, and Create a collaborative project team environment supplies the trust that makes sharing happen.
How it shows up
A key specialist is leaving in two weeks or a vendor team is rolling off. The best answer arranges pairing or shadowing and captures what can be documented, not just a final write-up.
Common confusion
Lessons learned captured only at the end are not knowledge transfer; PMI expects knowledge to be gathered and shared throughout so the current project benefits.
1.8 Plan and manage communicationDefine a communication strategy, feedback loops and reporting that fits sponsors and governance.
What it means
The project manager defines how, when and to whom information flows, promotes transparency and collaboration, sets up feedback loops, understands reporting requirements, and produces reports that meet sponsor expectations and support governance.
What to understand
Communication channels grow as n(n-1)/2, so a team going from 6 to 10 people moves from 15 to 45 channels. Choose push (email, reports), pull (wiki, dashboard) or interactive (meetings) by need; agile teams favor information radiators and face-to-face conversation. PMBOK 7 lens: Effectively engage with stakeholders, with communication spread across the Stakeholder, Team and Measurement performance domains.
How it shows up
A sponsor complains of surprises, or a remote team misses decisions. The answer checks the communication plan and the stakeholder's information needs, then tailors format, frequency or channel, often adding a feedback loop.
Common confusion
More reports are not better communication; if a stakeholder is not reading the report, the fix is a format or channel that matches their needs, not higher frequency.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Servant leadership

    A leadership approach in which the leader serves the team first by removing impediments, shielding it from distraction, coaching, and enabling self-organization.

    Remember
    Servant leaders still hold the team to agreed expectations; they influence through support and facilitation rather than command, and step in directly only when coaching fails or safety is at stake.
    Tested as
    It is the default lens for agile and hybrid People scenarios, where the best option usually facilitates or removes a blocker instead of assigning work.
    Trap
    Choosing an option where the project manager makes the team's technical or estimation decision for them because it seems efficient.

  • Conflict resolution modes

    Collaborate/problem-solve, compromise/reconcile, smooth/accommodate, force/direct and withdraw/avoid are the five standard approaches to a disagreement.

    Remember
    Collaborate gives a lasting win-win when time and trust allow; force is for emergencies; withdraw only buys time; smoothing emphasizes agreement while leaving the issue unresolved.
    Tested as
    Scenarios ask which approach is best given urgency, relationship importance and whether the conflict is about the task or personalities.
    Trap
    Picking compromise as the best answer when the scenario allows time for collaboration, which would give both parties what they need.

  • Tuckman ladder

    Teams move through forming, storming, norming, performing and adjourning, and can slide back when members change.

    Remember
    Conflict during storming is normal and should be facilitated, not suppressed; adding a new member can send a performing team back to forming.
    Tested as
    Questions describe team behavior and ask what stage the team is in or what the leader should provide at that stage.
    Trap
    Treating storming-stage disagreement as a performance problem to escalate rather than a stage to guide through with ground rules.

  • Team charter and ground rules

    A team-created agreement covering values, working agreements, decision-making, conflict handling and communication norms.

    Remember
    The team writes it and enforces it collectively; when a ground rule is broken, the first step is to refer to the charter, usually in a private conversation.
    Tested as
    Ground-rule violations and recurring friction point to creating, revisiting or enforcing the charter.
    Trap
    Escalating a ground-rule breach to the functional manager before the team or project manager has addressed it directly.

  • Stakeholder engagement assessment matrix

    A grid showing each stakeholder's current engagement level (C) and desired level (D) across unaware, resistant, neutral, supportive and leading.

    Remember
    The gap between C and D drives the engagement actions; not everyone needs to be leading, only at the level the project requires.
    Tested as
    A resistant or unaware key stakeholder in a scenario usually means the answer updates engagement strategies based on this gap.
    Trap
    Assuming every stakeholder should be moved to leading, which wastes effort on low-influence people.

  • Power/interest grid and salience model

    Power/interest sorts stakeholders into manage closely, keep satisfied, keep informed and monitor; the salience model classifies by power, legitimacy and urgency.

    Remember
    High power and high interest means manage closely; high power and low interest means keep satisfied, not ignore.
    Tested as
    Used to decide how much attention a newly identified stakeholder needs and through which channel.
    Trap
    Placing a powerful but disinterested executive in 'monitor' and getting blindsided when they veto the project.

  • Communication channels formula

    The number of potential communication channels among n people is n(n-1)/2.

    Remember
    Adding people grows channels quadratically: 8 people gives 28 channels, 12 gives 66; questions often ask for the increase, so subtract.
    Tested as
    A direct calculation question, or the reasoning behind why adding team members late increases coordination overhead.
    Trap
    Forgetting to include the project manager in n, or reporting the new total when the question asks how many channels were added.

  • Push, pull and interactive communication

    Push sends information to recipients, pull lets them retrieve it when needed, and interactive exchanges it in real time.

    Remember
    Interactive is most effective for resolving misunderstandings and complex issues; pull suits large audiences and reference material.
    Tested as
    Scenarios with confusion, ambiguity or a sensitive decision point toward interactive communication.
    Trap
    Choosing a detailed email (push) to resolve a misunderstanding that needs a conversation.

  • Emotional intelligence

    The ability to recognize and manage your own emotions and those of others: self-awareness, self-management, social awareness and social skill.

    Remember
    PMBOK 7 treats it as a core leadership skill; it shows up as reading the room, private feedback and staying calm when a stakeholder is angry.
    Tested as
    Angry-stakeholder and demotivated-team scenarios reward empathy and listening before problem solving.
    Trap
    Selecting the answer that immediately corrects or argues with an upset stakeholder instead of first acknowledging and understanding their concern.

  • Tacit vs. explicit knowledge

    Explicit knowledge can be written down and stored; tacit knowledge lives in people's experience and is shared through interaction.

    Remember
    Documents alone cannot transfer tacit knowledge; use pairing, shadowing, mentoring, communities of practice and storytelling.
    Tested as
    Departing experts and vendor handoffs are tested as knowledge-transfer tasks.
    Trap
    Answering 'ask the expert to document everything' when the knowledge at risk is judgment that needs pairing to transfer.

  • PMBOK 7 Team performance domain

    The performance domain covering activities and functions associated with the people who produce project deliverables, aiming for shared ownership, a high-performing team and leadership shown by all members.

    Remember
    Outcomes are shared ownership, a high-performing team, and appropriate leadership and interpersonal skills demonstrated by all team members.
    Tested as
    It explains why PMP answers favor team decisions, collective ownership and coaching over project-manager control.
    Trap
    Thinking leadership belongs only to the project manager; PMBOK 7 expects leadership behaviors from everyone on the team.

  • PMBOK 7 Stakeholder performance domain

    The performance domain covering stakeholder activities, aiming for a productive working relationship, agreement on objectives and satisfied, supportive stakeholders.

    Remember
    Its working sequence is identify, understand and analyze, prioritize, engage, and monitor, repeated throughout the project.
    Tested as
    Gives the order of steps behind many FIRST/NEXT questions about new or difficult stakeholders.
    Trap
    Engaging or negotiating with a stakeholder before analyzing their interests and influence.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Collaborate vs. compromise vs. smooth vs. force vs. withdraw

ConceptMeaningKey differenceCommon trap
Collaborate / problem-solve Work openly with the parties to find a solution that meets everyone's underlying needs. Produces lasting, win-win resolution but needs time, trust and a willingness to engage. Rejecting it in a scenario that clearly allows time, because it seems slower than compromise.
Compromise / reconcile Each party gives up something to reach a mutually acceptable middle position. Partial satisfaction for both; suitable when collaboration has failed or stakes are equal and time is limited. Treating it as the most mature option because it sounds balanced.
Smooth / accommodate Emphasize areas of agreement and play down differences, sometimes conceding to the other side. Preserves relationships short term but leaves the underlying issue unresolved. Choosing it for a substantive technical disagreement that will resurface.
Force / direct Impose one viewpoint, typically using positional authority. Fast and win-lose; appropriate for emergencies, safety or compliance issues with no time to discuss. Selecting it for ordinary priority disputes because the project manager 'owns' the project.
Withdraw / avoid Retreat or postpone the issue, possibly to let tempers cool or gather information. Resolves nothing; acceptable only as a short-term tactic or for trivial issues. Mistaking a cooling-off period for a resolution strategy.

Engage stakeholders vs. align expectations vs. manage expectations vs. communicate

ConceptMeaningKey differenceCommon trap
Engage stakeholders (task 1.4) Identify and analyze stakeholders and build relationships, trust and influence through the engagement plan. About involvement and attitude: moving people from current to desired engagement. Assuming a stakeholder is engaged because they receive reports.
Align stakeholder expectations (task 1.5) Surface and reconcile differing expectations among stakeholder groups through facilitated discussion. About agreement between stakeholders, mostly early or when new conflicts surface. Promising each group its own version privately instead of facilitating a shared position.
Manage stakeholder expectations (task 1.6) Keep delivered outcomes matched to internal and external customer expectations and monitor satisfaction. About ongoing fit between what is delivered and what customers expect, measured over time. Gold plating to keep a customer happy instead of confirming expectations and acceptance criteria.
Plan and manage communication (task 1.8) Design and run the information flows, feedback loops and reports the project needs. About the mechanism of information exchange, which supports the three tasks above. Answering an engagement or expectation gap with only a communication tweak.

ECO People tasks vs. PMBOK 7 principles and performance domains (editorial mapping)

ConceptMeaningKey differenceCommon trap
Develop a common vision; Lead the project team Principle: Demonstrate leadership behaviors. Performance domain: Team. Leadership in PMBOK 7 is shown by any team member, with vision and motivation as leader behaviors. Reading leadership as authority; PMBOK 7 frames it as influence and enabling others.
Manage conflicts; Help ensure knowledge transfer Principle: Create a collaborative project team environment. Performance domains: Team, Project Work. Collaboration, psychological safety and working agreements make conflict productive and knowledge flow. Treating knowledge management as a documentation task rather than a team-culture outcome.
Engage, align and manage stakeholders; Communication Principles: Effectively engage with stakeholders; Focus on value. Performance domains: Stakeholder, Delivery, Measurement. Engagement is proactive and continuous; satisfaction is a delivery outcome measured with real indicators. Thinking the PMBOK 7 lens adds new exam content; it explains the reasoning behind ECO tasks, it is not a separate syllabus.

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Escalate first

    What candidates pick
    Inform the sponsor or the team member's functional manager about the problem.
    Why it looks right
    It feels responsible and shows the issue is being taken seriously by someone with authority.
    Why it's wrong
    PMI expects the project manager to own people issues within their authority first; escalation is for issues beyond that authority or after direct attempts fail.

    Clue to watch for The scenario has not mentioned any prior attempt to resolve it directly; look for 'meet privately', 'discuss', or 'understand the cause' options.

  2. The project manager decides for the agile team

    What candidates pick
    Assign the disputed story, choose the technical approach, or set the estimate personally.
    Why it looks right
    It resolves the problem quickly and looks decisive.
    Why it's wrong
    Self-organizing teams own how the work is done and product owners own priority; PMBOK 7's Team performance domain emphasizes shared ownership, so the leader facilitates instead.

    Clue to watch for Words like 'agile team', 'sprint', 'self-organizing', or 'product owner' signal that the answer should coach or facilitate.

  3. Replace the difficult team member

    What candidates pick
    Request that the underperforming or disruptive person be removed from the project.
    Why it looks right
    It removes the visible source of the problem.
    Why it's wrong
    Removal skips understanding the cause, coaching, training or clarifying expectations; it is a last resort after documented attempts.

    Clue to watch for The scenario gives no history of feedback or support, which means investigation and coaching come first.

  4. Send more information

    What candidates pick
    Increase report frequency or add the stakeholder to more distribution lists.
    Why it looks right
    It appears to fix a communication gap with little effort.
    Why it's wrong
    If the stakeholder is resistant or unaware of why the project matters, the gap is engagement, not volume; the plan and approach need tailoring.

    Clue to watch for The stakeholder 'does not read' reports or 'is opposed', which points to engagement analysis and interactive communication.

  5. Accept the new stakeholder's demands immediately

    What candidates pick
    Add the late stakeholder's requirements to keep them supportive.
    Why it looks right
    Satisfying a powerful person seems like good stakeholder management.
    Why it's wrong
    New requirements must go through analysis and change control; first add them to the register and understand their needs and influence.

    Clue to watch for 'Newly identified' or 'was not consulted' stakeholder: update the stakeholder register and analyze before committing.

  6. Compromise as the mature choice

    What candidates pick
    Ask both parties to meet halfway.
    Why it looks right
    It sounds fair and ends the dispute quickly.
    Why it's wrong
    Both parties lose something and the root issue may persist; when time permits, collaboration that addresses both needs is preferred.

    Clue to watch for No deadline pressure in the scenario and the relationship is ongoing: choose the collaborate/problem-solve option.

Answer framework

Use this sequence when a People question describes a person, relationship or expectation problem.

  1. Identify who is involved and whether the issue is about vision, conflict, capability, engagement, expectations or information flow.
  2. Gather facts first: talk privately with the people involved and check the team charter, stakeholder register or communication plan.
  3. Choose the response that keeps ownership with the team or stakeholder, such as coaching, facilitating or collaborating, before directive action.
  4. Tailor the approach to the development approach and context; agile teams decide how to work, product owners decide priorities.
  5. Escalate only when the issue exceeds your authority or direct attempts have failed, then update the relevant plan or register so the fix lasts.

Practice question

Two weeks into a hybrid project, a respected engineer repeatedly interrupts colleagues in planning sessions, and two quieter team members have stopped contributing ideas. The team charter includes a ground rule about letting people finish speaking. What should the project manager do FIRST?

Want more like this? The PMP (PMBOK 7) practice test has questions for every domain.

Checklist

0 of 13

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Start with the PMBOK 7 Team and Stakeholder performance domains and the four principles that drive this domain (collaborative team environment, stakeholder engagement, leadership behaviors, focus on value). They give you a single mindset that explains most People answers, which is faster than memorizing scenario rules. Then work through the eight ECO tasks in order, writing one sentence for each on what the best project manager behavior looks like.

Give the most time to conflict resolution modes, servant leadership in agile teams, and the stakeholder engagement sequence, because those produce the most FIRST and NEXT questions. Learn the communication channels formula well enough to calculate an increase without hesitation.

Candidates usually underestimate knowledge transfer and expectation management, both of which are expressed as separate tasks in the July 2026 outline, and the difference between communication and engagement. Experienced managers also underestimate how strongly PMI prefers private, direct conversation over escalation.

Afterwards, practice mixed scenario sets that include predictive, agile and hybrid settings, and for each wrong answer write down which principle the correct option reflected. Then move to Process questions, where many People tasks reappear inside planning and status scenarios.

FAQ

How much of the PMP exam is the People domain?

People is 33% of scored items under the July 2026 PMP Examination Content Outline. With 180 total questions, that is roughly 59 questions as a planning estimate; PMI does not publish per-domain counts.

Did the People domain change in the July 2026 outline?

Yes. It dropped from 42% with 14 tasks in the 2021 outline to 33% with 8 broader tasks, and stakeholder work is split across three tasks: engage stakeholders, align stakeholder expectations, and manage stakeholder expectations.

Is the PMP exam based on PMBOK 7?

No single text is the basis of the exam, and the outline names no PMBOK edition. This page uses PMBOK 7's principles and performance domains as a study lens because they explain the reasoning PMI rewards; PMBOK 8, published in November 2025, keeps that foundation.

What question style dominates People?

Short situational scenarios asking what the project manager should do FIRST, NEXT or BEST. Several options are valid actions, so sequencing and choosing the least directive effective step matters.

Is servant leadership always the right answer?

It is the default in adaptive and hybrid settings, but not absolute. Safety risks, compliance breaches or emergencies can justify a directive approach, and the scenario will make that urgency explicit.

What is the difference between engaging stakeholders and communicating with them?

Communication moves information; engagement builds the relationship and involvement that changes a stakeholder's attitude. A resistant sponsor needs engagement, such as a direct conversation about concerns, not more reports.

How long should I study the People domain?

As a planning estimate, about 40 to 55 hours of a 150-hour plan, adjusted for your experience. Managers from directive cultures often need extra scenario practice here.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 1 knowledge

Practice the FIRST and NEXT judgment calls this page covered, from conflict modes and servant leadership to stakeholder engagement gaps, against scenario questions written for the July 2026 PMP outline.

Take the PMP (PMBOK 7) practice test Check your PMP (PMBOK 7) readiness

Keep going