Domain 1: People
- The July 2026 People domain covers developing a common vision, managing conflict, leading the project team, engaging stakeholders, aligning and managing stakeholder expectations, knowledge transfer, and planning and managing communication.
- A shared vision is built with key stakeholders, promoted to the team, and kept current; when people pull in different directions, break the situation down to find the root cause of the misunderstanding rather than restating the vision louder.
- Servant leadership is the PMI-preferred stance: the project manager empowers the team, represents the voice of the team, sets clear roles and expectations, and chooses a leadership style that fits the situation rather than assigning tasks and micromanaging.
- Tuckman's model describes team development as forming, storming, norming, performing, and adjourning; conflict is normal in the storming stage, and the leader's job is to coach the team through it, not to avoid or suppress it.
- The Thomas-Kilmann conflict modes are collaborating/problem solving, compromising, smoothing/accommodating, forcing/directing, and withdrawing/avoiding; collaborating (confronting the problem to find a win-win) is generally the best and most durable resolution, while forcing creates lose-win resentment and withdrawing only postpones the issue.
- A team charter is created with the team and captures shared values, ground rules, working agreements, communication norms, and decision-making and conflict-resolution processes; the project manager then fosters adherence to those ground rules and deals with violations.
- Emotional intelligence - self-awareness, self-management, social awareness, and relationship management - lets a project manager read the room, manage their own reactions, and build the trust needed to influence stakeholders without formal authority.
- Stakeholders are identified, analyzed, and categorized, and communication is tailored to their needs; the project manager then aligns stakeholder needs and expectations with project objectives and monitors internal and external customer satisfaction, responding as needed.
- Communication planning defines a communication strategy, promotes transparency and collaboration, establishes a feedback loop, and produces reports that fit sponsor and stakeholder expectations and support governance; the number of channels grows as n(n-1)/2, so adding people raises complexity quickly.
- Knowledge transfer means identifying the knowledge critical to the project, gathering it, and fostering an environment where it is shared, so the team does not depend on one person and lessons carry forward.
- Negotiation should aim for principled, interest-based agreements (win-win) rather than positional bargaining; knowing your best alternative to a negotiated agreement (BATNA) strengthens your position while preserving the relationship.
Domain 2: Process
- The July 2026 Process domain covers the integrated project management plan, scope, value-based delivery, resources, procurement, finance, quality, schedule, evaluating project status, and project closure; risk, change control, and issues now sit in Business Environment.
- Selecting a development approach - predictive, adaptive/agile, or hybrid - starts from assessing project needs, complexity, and magnitude: stable, well-understood work suits predictive, while high-uncertainty work suits an adaptive approach, and the integrated plan is maintained as conditions change.
- Scope is defined, agreed with stakeholders, and broken down - through requirements and a work breakdown structure (WBS) in predictive projects, or a prioritized product backlog (using techniques such as MoSCoW) in adaptive projects; scope creep and gold plating are both to be avoided.
- Value-based delivery means identifying value components with key stakeholders, prioritizing work by value and feedback, delivering incrementally where possible (often starting with a minimum viable product), and making sure a measurement system is in place to track benefits.
- The critical path is the longest sequence of dependent activities and determines the shortest possible project duration; activities on it have zero float, and schedule compression uses crashing (adding resources, which raises cost) or fast-tracking (running activities in parallel, which raises risk).
- Estimating techniques include analogous (top-down, based on similar past work), parametric (rate times quantity), three-point/PERT estimating - (Optimistic + 4 x Most Likely + Pessimistic) / 6 - and relative estimates such as story points, with benchmarks and historical data improving accuracy.
- Finance planning covers financial needs, risk and contingency allocations, spend tracking, reporting, and reserves; earned value management compares planned value (PV), earned value (EV), and actual cost (AC): CV = EV - AC, SV = EV - PV, CPI = EV / AC, and SPI = EV / PV, where an index above 1.0 is favorable.
- Contract types allocate risk differently: fixed-price puts cost risk on the seller, cost-reimbursable puts it on the buyer, and time-and-materials sits in between; the project manager plans procurement, takes part in negotiations, manages suppliers, and evaluates vendor performance.
- Quality work gathers quality requirements, plans quality processes and tools, helps ensure regulatory compliance, manages cost of quality (CoQ) and sustainability, and runs ongoing reviews with continuous improvement.
- Evaluating project status means developing and tailoring metrics and artifacts, keeping artifacts current and accessible, assessing progress, and communicating status; agile teams do this through iteration reviews, retrospectives, and visible information radiators.
- Closure obtains stakeholder approval of completion, applies agreed closing criteria, validates readiness for transition to operations or the next phase, and concludes final lessons learned, retrospectives, procurement, financials, and resources.
Domain 3: Business Environment
- At 26% of the exam, the July 2026 Business Environment domain covers governance, compliance, change control, impediments and issues, risk, continuous improvement, organizational change, and changes in the external business environment.
- Project governance sets the structure, rules, procedures, reporting, ethics, and policies through organizational process assets (OPAs), defines success metrics, and outlines escalation paths and thresholds; governance also operates across projects, programs, and portfolios.
- Compliance requirements - security, health and safety, sustainability, and regulatory - are confirmed and classified early, threats to compliance are identified, the consequences of noncompliance analyzed, and the project's degree of compliance measured.
- Change control executes the change control process, communicates the status of proposed changes, implements only approved changes, and updates project documentation to reflect them; in adaptive work, change flows through backlog refinement and reprioritization.
- Removing impediments is a core servant-leader duty: evaluate their impact, prioritize and highlight them, apply an intervention strategy, and keep reassessing; recognize when a risk has become an issue and work with the relevant stakeholders on its resolution.
- Risk responses differ for threats (avoid, transfer, mitigate, accept, or escalate) and opportunities (exploit, share, enhance, accept, or escalate); risks are logged in the risk register with an owner, and contingency reserves cover known risks while management reserves cover unknown risks.
- The ECO names security and sustainability risks explicitly, so expect scenarios such as poor IT security in the risk register or managing sustainability risks as part of executing the risk management plan.
- Continuous improvement means using lessons learned, keeping improvement processes up to date, and updating the organization's OPAs so the next project benefits.
- Organizational change management starts with assessing organizational culture and the impact of change on the project; models such as ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) and Kotter's 8 steps help move stakeholders from resistance to adoption.
- PESTLE analysis (political, economic, social, technological, legal, environmental) helps survey external changes such as regulations, technology, geopolitics, and markets; the project manager assesses and prioritizes their impact on scope or backlog and keeps reviewing as conditions evolve.
- Enterprise environmental factors (EEFs) are conditions outside the team's control that influence the project (market conditions, organizational culture, regulations), while organizational process assets (OPAs) are the organization's reusable plans, templates, policies, and lessons learned.
PMP exam tips
- Answer with the PMI mindset, not real-world shortcuts: prefer talking directly to people, addressing the root cause over the symptom, being proactive, and collaborating; the option that empowers the team and protects value is usually correct, even when a quicker workaround exists.
- About 60% of the exam is adaptive/agile or hybrid, so know servant leadership, the core ceremonies (planning, standup, review, retrospective), backlog prioritization, and incremental value delivery as well as you know predictive tools; many scenarios hinge on picking the right response for the development approach described.
- Business Environment is now 26% of the exam, so study risk, change control, impediments and issues, governance, and compliance as seriously as scheduling and cost; under the 2021 outline it was only 8%.
- Practice reading charts, graphs, and longer cases: the July 2026 exam adds case or scenario items and graphic-based items, so interpret burndown charts, earned value curves, and risk matrices quickly. Master the earned value formulas - CV = EV - AC, SV = EV - PV, CPI = EV / AC, SPI = EV / PV.
- When a scenario asks what to do first or next, prefer understanding the situation (gather information, analyze the impact, consult the plan or risk register) before escalating, and escalate only what is truly beyond your authority or the team's ability to resolve.
Study guide FAQ
What format and length does the PMP exam have?
The PMP exam has 180 questions in 240 minutes; 170 are scored and 10 are unscored pretest questions placed at random. Item types are case or scenario (new), graphic-based (new), multiple-choice single response, multiple response, enhanced matching, matching, point and click, and pull-down list; the last four are available only at a test center (CBT). There are two 10-minute breaks: the first after the case-study section and the second about midway through the independent questions, and once you start a break you cannot return to the earlier section.
What passing score do I need?
PMI does not publish a fixed passing percentage. The exam is scored using psychometric analysis, and your result is reported as an overall pass or fail along with a proficiency rating (Above Target, Target, Below Target, or Needs Improvement) for each of the three domains, so it is best to aim for solid, consistent performance across People, Process, and Business Environment.
What are the eligibility requirements to sit the exam?
The July 2026 ECO has four paths, each counting non-overlapping experience leading projects in the past 10 years: upper-secondary school (EQF 4 / ISCED 3-4) with 60 months, an associate's-level or advanced technical/vocational program (EQF 5 / ISCED 5) with 48 months, a bachelor's degree or higher (or a qualification formally mapped to EQF 6) with 36 months, or a degree from a PMI GAC-accredited program with 24 months. All paths also need 35 hours of project management training aligned to the ECO; an active CAPM waives it, and GAC coursework can count toward it. Books and practice exams alone do not qualify as training.
How much of the exam is agile versus predictive?
Approximately 40% of the questions represent predictive approaches, and the remaining 60% are divided between adaptive/agile and hybrid approaches, spread across all three domains. You should be comfortable with servant leadership, iterations and ceremonies, and backlog-driven delivery, not just classic tools like the WBS and critical path.
Which reference materials is the exam based on?
The exam is aligned to the July 2026 PMP Examination Content Outline (ECO) and draws on the current PMBOK Guide and the Agile Practice Guide. PMI states the exam is not written according to any single text, so it tests applied judgment across all three ECO domains and multiple delivery approaches rather than the PMBOK Guide alone.
Official exam sources
The domain names and weightings on this page follow the published exam blueprint. Each source below records what it confirmed and when it was read, so the split can be checked rather than taken on trust.
- PMI - PMP Examination Content Outline, July 2026 (PDF)Blueprint revised July 2026 · link and content verified 27 October 2026Everything on this guide except the pass mark, which PMI does not publish. The July 2026 ECO replaced the January 2021 outline on 9 July 2026. "The PMP certification exam is comprised of 180 questions" and "Of the 180 questions, 10 are considered pretest questions. Pretest questions do not affect the score" - so 170 scored. "The allotted time to complete the center-based exam is 240 minutes." The breaks match the FAQ: "there are two 10-minute breaks in the exam. The first break occurs after the case-study section, and the second break occurs approximately midway through the independent question portion of the exam." Three domains totalling 100%: "I. People 33%", "II. Process 41%", "III. Business Environment 26%". On approach: "Approximately 40% of the items will represent predictive project management approaches, whereas the remaining 60% will be divided between adaptive/agile and hybrid management approaches." The item types in the FAQ are the ECO's list, with Case or Scenario and Graphic-Based Questions marked NEW and enhanced matching, matching, point and click, and pull-down list marked "Only available on CBT". Eligibility: "All project management experience must have been accrued within the last 10 years"; upper-secondary school (EQF Level 4 / ISCED 3-4) needs "Minimum 60 months/5 years of non-overlapping experience leading projects in the past 10 years", an associate's-level or advanced technical/vocational program (EQF Level 5 / ISCED 5) "Minimum 48 months/4 years", a bachelor's degree or higher (or a qualification formally mapped to EQF Level 6) "Minimum 36 months/3 years", and a degree from a GAC-accredited program "Minimum 24 months/2 years"; candidates "must also have taken at least 35 hours of commercial training", which an active CAPM waives. Read from the text of PMI's public PDF because pmi.org answers a page fetch with HTTP 403.
Settled, and recorded here. PMI publishes no passing percentage and our page printed "70%" beside "Passing score" while this guide's own FAQ said "PMI does not publish a fixed passing percentage" - the page contradicted itself. The numeric fact is now hidden and the FAQ answers with PMI's position. The 700 stays in exam metadata because it is what CertGrid grades a practice attempt against; it is not PMI's.