PMP (PMBOK 7) · Domain 3 of 3

PMP (PMBOK 7) Domain 3: Business Environment

Business Environment jumped to 26% in the July 2026 PMP outline. It covers governance, compliance, change control, impediments, risk, continuous improvement and organizational and external change, linked here to the PMBOK 7 Uncertainty domain and stewardship, risk and change principles.

Exam weight
26%
Official tasks
8
Estimated questions estimate
~47
Suggested study time estimate
35–45 hrs

About 23 min read Reviewed October 2026

Overview

Business Environment covers the forces around the project that shape what it may do and must react to: the governance structure and escalation thresholds, compliance obligations, the change control process, impediments and issues, risk, continuous improvement, organizational change and shifts in the external environment. The July 2026 outline grew this domain from 8% with four tasks to 26% with eight, absorbing risk, change control and issue management that previously sat in Process.

PMBOK Guide 7th Edition gives the reasoning: the Be a diligent, respectful, and caring steward principle drives governance and compliance, Optimize risk responses and the Uncertainty performance domain drive risk work, Recognize, evaluate, and respond to system interactions explains external change, and Enable change to achieve the envisioned future state explains organizational change. The domain relies on the baselines and reserves from Process and the stakeholder skills from People.

How it's tested

Business Environment questions are judgment scenarios with an organizational or external trigger: a regulation changes, a stakeholder requests a change, a risk materializes, a team is blocked, or the organization restructures. Many ask what to do FIRST or NEXT, and the right answer usually follows the governance path, analyzes impact, and involves the proper decision maker instead of acting alone.

  • Impact before action

    A change request, external shift or compliance requirement arrives. The correct option assesses its impact on scope, schedule, cost, risk and value before implementing, rejecting or escalating it.

  • Risk or issue

    The scenario describes an uncertain future event (risk) or something already happening (issue). Risks go to the register and response planning; issues go to the issue log and need a resolution or workaround now.

  • Stay inside governance

    A sponsor or senior stakeholder pressures the team to skip a control, gate or compliance step. The correct option follows the defined governance path or escalation threshold, even if it is slower.

Reasoning it through

A new data-privacy regulation takes effect before a customer portal launches. Options: launch and patch later, ask the vendor to absorb it, add it to the backlog as a normal story, or assess the requirement's impact with compliance experts and raise it through governance. Compliance is not optional and could change scope, so assessing impact and using the governance path comes first, reflecting the stewardship principle.

Tasks 8

Official tasks from the PMI outline, in outline order.

3.1 Define and establish project governanceSet the structure, rules, success metrics and escalation paths that govern the project.
What it means
The project manager describes and establishes the project's structure, rules, procedures, reporting, ethics and policies using organizational process assets, defines success metrics, and sets escalation paths and thresholds.
What to understand
Governance defines who decides what and when issues must be escalated, for example a variance beyond 10% or a change above a set cost; inside those thresholds the project manager or team decides. Phase gates and steering committees are typical predictive mechanisms, while adaptive projects use lighter governance such as product owner authority and regular reviews. PMBOK 7 lens: Be a diligent, respectful, and caring steward and Recognize, evaluate, and respond to system interactions; PMBOK 8 makes governance its own performance domain.
How it shows up
A variance or decision exceeds the project manager's authority, or a new project has no escalation path. The answer escalates per the defined thresholds, or establishes them early using the organization's process assets.
Common confusion
Governance is not the same as management: governance sets the framework and decision rights, while management works within it day to day.
3.2 Plan and manage project complianceIdentify, classify and measure compliance with security, safety, sustainability and regulatory requirements.
What it means
The project manager confirms compliance requirements such as security, health and safety, sustainability and regulation, classifies them, identifies threats to compliance, uses methods to support it, analyzes the consequences of noncompliance, decides the actions needed and measures how compliant the project is.
What to understand
Compliance requirements are constraints, not preferences, so they cannot be traded away to meet a date; noncompliance can bring fines, legal action, safety harm or loss of license. Audits, checklists and including requirements in acceptance criteria and definition of done are common methods. PMBOK 7 lens: Be a diligent, respectful, and caring steward, which explicitly covers compliance and sustainability, and Build quality into processes and deliverables.
How it shows up
A sponsor asks to defer a safety or privacy control to hit a launch date. The best answer explains the consequences, keeps the control, and seeks schedule or scope options through governance.
Common confusion
Treating a regulatory requirement as a normal change request that can be prioritized down; it may change the plan, but it cannot be declined.
3.3 Manage and control changesExecute the change control process, communicate change status and update documentation.
What it means
The project manager runs the change control process, communicates the status of proposed changes, implements approved changes and updates project documentation to reflect them.
What to understand
In predictive work the sequence is: evaluate the impact, submit a change request, the change control board (CCB) or authorized approver decides, then update baselines and plans and communicate. In adaptive work, new or changed requirements go to the product owner, who reorders the backlog; changes within a sprint are discouraged. PMBOK 7 lens: Embrace adaptability and resiliency, with the Planning and Project Work performance domains holding the baselines and backlog.
How it shows up
A stakeholder asks a developer directly for a change, or an approved change was implemented without updating the schedule. The answer routes the request through the defined process and updates baselines and documentation after approval.
Common confusion
The project manager rarely approves significant changes alone; analyzing impact is the project manager's job, approval belongs to whoever governance names.
3.4 Remove impediments and manage issuesPrioritize and remove blockers, recognize when a risk becomes an issue and resolve issues with stakeholders.
What it means
The project manager evaluates and prioritizes impediments, chooses an intervention to remove or minimize them, reassesses continually, recognizes when a risk has occurred and become an issue, and works with stakeholders to resolve it.
What to understand
An impediment blocks the team's progress and is often surfaced in the daily stand-up; an issue is a current condition that affects objectives and is tracked in the issue log with an owner and due date. When an unplanned risk occurs, a workaround is the unplanned response. PMBOK 7 lens: Demonstrate leadership behaviors (servant leaders remove impediments) and the Project Work performance domain.
How it shows up
A team member reports in stand-up that they are waiting on another department for access. The best answer has the project manager take ownership of removing the blocker after the stand-up, not solve it in the meeting or ignore it as the member's problem.
Common confusion
Candidates log an occurring problem in the risk register; once it has happened it is an issue, and the risk register entry is updated or closed.
3.5 Plan and manage riskPlan, identify, analyze, respond to and monitor risks, including security and sustainability risks.
What it means
The project manager develops the risk management plan, identifies and analyzes risks, maintains the risk register, executes risk responses including security and sustainability risks, monitors and controls risks, and communicates their status and impact.
What to understand
Threat responses are escalate, avoid, transfer, mitigate and accept; opportunity responses are escalate, exploit, share, enhance and accept. Qualitative analysis ranks by probability and impact; quantitative analysis uses expected monetary value (EMV = probability x impact) and simulation. A trigger signals a risk is about to occur, and each risk has an owner. PMBOK 7 lens: Optimize risk responses and the Uncertainty performance domain, which also covers ambiguity, complexity and volatility.
How it shows up
A trigger appears, a risk owner has not acted, or the scenario asks which response a described action represents. Implement the planned response when the trigger fires, and classify by what the action does to probability, impact or ownership.
Common confusion
Buying insurance is transfer, not mitigation; it moves the financial impact to a third party but does not reduce the probability that the event happens.
3.6 Continuous improvementUse lessons learned, keep improvement processes current and update organizational process assets.
What it means
The project manager uses lessons learned during the project, makes sure continuous improvement processes are updated, and feeds improvements back into the organization's process assets.
What to understand
Lessons learned are captured throughout, in a lessons learned register, and applied immediately; agile teams improve through retrospectives each iteration, and Plan-Do-Check-Act (PDCA) and kaizen describe small, repeated improvements. PMBOK 7 lens: Embrace adaptability and resiliency and Build quality into processes and deliverables, with the Measurement performance domain supplying the evidence.
How it shows up
The same problem recurs across iterations, or a project is about to start without reviewing past projects. The answer reviews lessons learned or uses a retrospective to choose a concrete improvement, then checks whether it worked.
Common confusion
A retrospective is about how the team works, not a demo of the product; the sprint review inspects the product increment.
3.7 Support organizational changeAssess organizational culture and respond to organizational change affecting the project.
What it means
The project manager assesses the organization's culture, evaluates how organizational changes such as restructuring, mergers or new strategy affect the project, and decides the actions needed, including helping people adopt what the project delivers.
What to understand
Projects create change that people must adopt, and organizations change around projects. Change models such as ADKAR (awareness, desire, knowledge, ability, reinforcement), Kotter's eight steps and Bridges' transition model help plan adoption. PMBOK 7 lens: Enable change to achieve the envisioned future state, plus the Stakeholder performance domain for resistance.
How it shows up
Users resist a new system the project delivered, or a reorganization changes the sponsor. The best answer assesses culture and stakeholder impact and plans engagement or adoption support, not simply mandating use or continuing as before.
Common confusion
Change control (approving changes to project baselines, task 3.3) is different from organizational change management (helping the organization adopt new ways of working).
3.8 Evaluate external business environment changesSurvey external changes and assess their impact on scope and backlog.
What it means
The project manager surveys changes outside the organization such as regulations, technology, geopolitics and markets, assesses and prioritizes their impact on the project scope or backlog, and keeps reviewing the environment throughout.
What to understand
External factors are part of enterprise environmental factors; PESTLE (political, economic, social, technological, legal, environmental) is a common scanning tool. The output is a prioritized impact on scope or backlog, which may lead to a change request, backlog reprioritization or even a recommendation to stop the project if the business case no longer holds. PMBOK 7 lens: Recognize, evaluate, and respond to system interactions and Navigate complexity, with the Uncertainty performance domain covering volatility.
How it shows up
A competitor releases a similar product, or a tariff makes a key component expensive. The answer assesses the impact on value and scope and brings it to the sponsor or product owner with options, rather than continuing unchanged or acting unilaterally.
Common confusion
Treating external changes as someone else's concern; the ECO makes continuous scanning a project manager task because it affects whether the project still delivers value.

High-yield concepts

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

  • Risk vs. issue

    A risk is an uncertain event or condition that may affect objectives; an issue is a current condition already affecting them.

    Remember
    When a risk occurs it becomes an issue: execute the planned response or, if unplanned, a workaround, then log it in the issue log and update the risk register.
    Tested as
    Many questions hinge on recognizing that the event has already happened, which changes the correct artifact and action.
    Trap
    Running fresh risk analysis on something that has already occurred instead of responding to it.

  • Threat responses

    Escalate (the threat is outside the project's scope or the project manager's authority), avoid (eliminate the threat), transfer (shift impact to a third party), mitigate (reduce probability or impact) and accept (acknowledge, actively with a reserve or passively).

    Remember
    Classify by the effect: removing the cause is avoid, insurance or a fixed-price subcontract is transfer, a prototype or extra testing is mitigate.
    Tested as
    Classification questions describe an action and ask which strategy it is.
    Trap
    Calling insurance mitigation, or calling a schedule change that removes the threat mitigation instead of avoidance.

  • Opportunity responses

    Escalate, exploit (make sure it happens), share (partner with someone better placed to capture it), enhance (raise probability or impact) and accept.

    Remember
    Exploit and avoid are mirror images, share mirrors transfer, enhance mirrors mitigate.
    Tested as
    Scenarios describe a favorable possibility and ask how to respond.
    Trap
    Choosing enhance when the action guarantees the opportunity, which is exploit.

  • Expected monetary value (EMV)

    EMV = probability x impact, with threats negative and opportunities positive; summed across risks or along decision tree branches.

    Remember
    A 30% chance of a 50,000 loss has EMV of -15,000; in a decision tree, pick the branch with the best EMV after including the initial cost.
    Tested as
    Calculation questions and decision tree comparisons of options.
    Trap
    Forgetting to subtract the decision's upfront cost or mixing the signs of threats and opportunities.

  • Risk trigger, owner and residual risk

    A trigger is a warning sign that a risk is about to occur; the risk owner monitors it and runs the response; residual risk is what remains after the response; a secondary risk is created by the response.

    Remember
    When a trigger appears, the owner implements the planned response; residual and secondary risks are recorded in the risk register.
    Tested as
    Scenarios show a trigger occurring and ask the next step.
    Trap
    Re-analyzing or escalating instead of executing the agreed response.

  • Change control board (CCB)

    The group named in the change management plan to approve or reject changes to baselines and key documents in predictive projects.

    Remember
    Sequence: assess impact, submit a change request, decision by CCB or authorized approver, update baselines and plans, communicate, implement.
    Tested as
    Most predictive change scenarios test this order or who decides.
    Trap
    Implementing a change, even a small one, before it is approved, or approving it yourself when it exceeds your authority.

  • Escalation thresholds

    Limits set by governance that define when a variance, risk or decision must move above the project manager, such as cost variance above 10%.

    Remember
    Inside the threshold the project manager acts; beyond it, escalate with analysis and options rather than a bare problem.
    Tested as
    Questions ask whether to act or escalate given a stated authority limit.
    Trap
    Escalating everything to be safe, or acting beyond authority to save time.

  • Workaround vs. contingency plan

    A contingency plan is a planned response executed when a known risk occurs; a workaround is an unplanned response to an unidentified risk that has occurred.

    Remember
    Workarounds are recorded and fed into lessons learned and the risk register because they reveal a gap in identification.
    Tested as
    Distinguishes responses to identified versus unidentified risks.
    Trap
    Calling the execution of a pre-planned response a workaround.

  • Organizational process assets (OPAs) vs. enterprise environmental factors (EEFs)

    OPAs are the organization's own plans, processes, templates and knowledge bases; EEFs are conditions outside the project team's control, internal or external.

    Remember
    Governance is established through OPAs, and continuous improvement updates them; regulations, markets and culture are EEFs.
    Tested as
    Governance, compliance and continuous improvement tasks name OPAs directly, and external changes are EEFs.
    Trap
    Classifying a government regulation as an OPA because the organization has a policy about it.

  • ADKAR and Kotter change models

    ADKAR moves individuals through awareness, desire, knowledge, ability and reinforcement; Kotter's eight steps start with urgency and a guiding coalition and end by anchoring change in culture.

    Remember
    Adoption fails when steps are skipped, for example training (knowledge) before people understand why the change is needed (awareness and desire).
    Tested as
    Resistance-to-change scenarios ask what is missing or what to do first.
    Trap
    Answering resistance with more training when people have not accepted why the change matters.

  • PESTLE analysis

    A scan of political, economic, social, technological, legal and environmental factors in the external environment.

    Remember
    The output that matters is the prioritized impact on scope, backlog and business value, revisited throughout the project.
    Tested as
    Supports task 3.8 scenarios about regulation, market or technology shifts.
    Trap
    Treating it as a one-time initiation exercise rather than continual review.

  • PMBOK 7 Uncertainty performance domain

    The performance domain covering risk and the broader uncertainty of ambiguity, complexity and volatility.

    Remember
    Responses include risk processes but also building in options, reserves, incremental delivery and resilience when the future cannot be predicted.
    Tested as
    Explains why agile and hybrid answers favor short feedback loops for highly uncertain work.
    Trap
    Thinking uncertainty is handled only through a risk register.

  • Stewardship principle

    PMBOK 7's Be a diligent, respectful, and caring steward principle: act with integrity, care, trustworthiness and compliance, inside and outside the organization.

    Remember
    It covers ethics, compliance, financial responsibility and sustainability, so it outranks short-term schedule pressure.
    Tested as
    Underpins governance, compliance and ethics scenarios where the tempting option cuts a corner.
    Trap
    Choosing the option that meets the deadline by quietly deferring a legal, safety or ethical obligation.

Side by side

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

Risk vs. issue vs. impediment

ConceptMeaningKey differenceCommon trap
Risk An uncertain future event or condition that could positively or negatively affect objectives. Has not happened; tracked in the risk register with probability, impact, owner and response. Keeping something in the risk register after it has already happened.
Issue A current condition or situation affecting project objectives. Already happening; tracked in the issue log with owner and target resolution date. Analyzing probability for an event that is already certain.
Impediment Anything blocking the team from making progress, often raised at the daily stand-up. Team-level blocker the project manager or Scrum Master works to remove, usually quickly and outside the stand-up. Expecting the blocked team member to resolve a cross-department impediment alone.

Avoid vs. transfer vs. mitigate vs. accept (threats)

ConceptMeaningKey differenceCommon trap
Avoid Eliminate the threat or protect the project from it entirely, for example by changing scope or approach. Probability goes to zero for that threat. Labeling any reduction as avoidance; only elimination counts.
Transfer Shift ownership of the impact to a third party, for example insurance, warranties or contract terms. The threat still exists; the financial consequence moves elsewhere, usually for a premium. Calling insurance mitigation.
Mitigate Reduce the probability or impact, for example extra testing, redundancy or a prototype. The threat remains but is smaller. Confusing it with a contingency plan, which only acts after the trigger.
Accept Acknowledge the threat without proactive action; active acceptance sets aside a contingency reserve. Used when other responses cost more than the threat or no response is possible. Thinking acceptance means ignoring the risk; it is still recorded and monitored.

Change control vs. backlog reprioritization vs. organizational change management

ConceptMeaningKey differenceCommon trap
Change control (predictive) Formal process to evaluate and approve changes to baselines through a CCB or authorized approver. Protects agreed baselines; changes take effect only after approval. Implementing first and documenting later.
Backlog reprioritization (adaptive) The product owner adds, removes or reorders backlog items based on value and feedback. Change is expected and absorbed between iterations, not through a CCB. Inserting new work into the current sprint without the team's agreement.
Organizational change management Helping people and the organization adopt new processes, systems or structures. About human adoption of the project's outcome, not approval of project changes. Assuming a delivered system equals a successful change.

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

ConceptMeaningKey differenceCommon trap
Governance; Compliance Principle: Be a diligent, respectful, and caring steward. Related: Recognize, evaluate, and respond to system interactions. Stewardship makes legal, ethical and sustainability duties part of the project manager's role, not an outside constraint. Treating governance as overhead to minimize rather than the source of decision rights.
Risk; Impediments and issues Principle: Optimize risk responses. Performance domains: Uncertainty, Project Work. Responses are proportionate, owned and continually reviewed, and uncertainty includes ambiguity and volatility as well as risk. Over-responding to minor risks or under-responding to high-impact ones.
Change control; Continuous improvement; Organizational and external change Principles: Embrace adaptability and resiliency; Enable change to achieve the envisioned future state; Navigate complexity. Projects must adapt to change while helping the organization adopt the change they create. Reading the Change principle as being about change requests; it concerns organizational adoption.

Exam traps

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

  1. Implement the small change to keep the customer happy

    What candidates pick
    Make the requested change immediately because it is small and the customer is important.
    Why it looks right
    It avoids bureaucracy and pleases a key stakeholder.
    Why it's wrong
    Even small changes can affect other work, risk and baselines; in predictive projects they need impact analysis and approval through change control.

    Clue to watch for Words like 'baseline', 'change control board' or 'signed-off requirements' signal the formal path; 'product owner' and 'backlog' signal backlog refinement.

  2. Re-analyze a risk that has occurred

    What candidates pick
    Perform qualitative risk analysis on the event or add it to the risk register.
    Why it looks right
    Risk analysis feels like the disciplined step.
    Why it's wrong
    Once the event has happened it is an issue; execute the contingency plan or a workaround and log it in the issue log.

    Clue to watch for Past-tense language: 'has failed', 'the supplier went bankrupt', 'the storm damaged'.

  3. Trade compliance for the deadline

    What candidates pick
    Launch on time and address the regulatory or security gap in a later release.
    Why it looks right
    The sponsor wants the date, and the gap may seem minor.
    Why it's wrong
    Compliance requirements are mandatory constraints; the stewardship principle and the compliance task require assessing consequences and finding scope or schedule options within the law.

    Clue to watch for Any mention of regulation, safety, privacy, audit or legal exposure.

  4. Escalate inside your authority

    What candidates pick
    Send every variance or issue to the sponsor or steering committee.
    Why it looks right
    Escalation feels safe and transparent.
    Why it's wrong
    Governance sets thresholds so the project manager handles what is within them; over-escalation slows decisions and signals lack of ownership.

    Clue to watch for The scenario states a variance or cost below a defined threshold, or says the decision is within the project manager's authority.

  5. Mandate adoption of the change

    What candidates pick
    Ask senior management to require staff to use the new system.
    Why it looks right
    Authority seems like the fastest way to overcome resistance.
    Why it's wrong
    Mandates without awareness and desire produce workarounds and low adoption; organizational change support starts with assessing culture and engaging affected people.

    Clue to watch for Users are 'resisting', 'reverting to old spreadsheets' or 'were not consulted'.

  6. Ignore an external change because scope is approved

    What candidates pick
    Continue with the approved plan since the competitor's move or the new tariff is outside the project.
    Why it looks right
    The baseline is approved and the change is not the project's fault.
    Why it's wrong
    Task 3.8 requires assessing external changes' impact on scope and value; the business case may no longer hold.

    Clue to watch for A market, technology, regulatory or geopolitical event that affects the product's value or cost.

Answer framework

Use this sequence when a Business Environment question introduces an organizational, regulatory or external trigger.

  1. Classify the trigger: governance decision, compliance requirement, change request, impediment, issue, risk, improvement opportunity, or organizational or external change.
  2. Check what already exists for it, such as the risk register, issue log, change management plan, escalation thresholds or compliance requirements.
  3. Assess the impact on scope, schedule, cost, quality, risk and business value before deciding anything, involving experts where compliance or security is involved.
  4. Act within your authority using the defined path: execute the planned response, route the change, remove the blocker, or escalate with options when the threshold is exceeded.
  5. Update the register, log, baselines or organizational process assets, communicate the outcome, and capture the lesson for continuous improvement.

Practice question

During execution of a predictive construction project, the risk owner reports that the trigger for a planned risk, a supplier's missed interim delivery, has just occurred. A contingency plan was approved with the risk register. What should the project manager do NEXT?

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

Checklist

0 of 14

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

Study strategy

Start with risk, because task 3.5 and the PMBOK 7 Uncertainty performance domain feed the issue, change and compliance tasks. Learn the threat and opportunity responses as mirror pairs, practice EMV and decision trees, and be precise about triggers, owners, contingency plans and workarounds.

Next, study change control in both forms: the predictive sequence through a change control board and the adaptive path through the product owner and backlog. Then cover governance and compliance together, using the stewardship principle as the common thread: decision rights, escalation thresholds and non-negotiable obligations.

The most underestimated areas are compliance, organizational change and external environment scanning, which older materials treated lightly when the domain was only 8%. Because the domain grew to 26%, older question banks and notes cover it thinly, so check that your materials include scenarios on regulation changes, user resistance and market shifts.

Afterwards, practice mixed scenarios and, for each one, name the trigger type before reading the options; that single habit separates risks from issues and changes from compliance obligations. Finish by revisiting People, since most Business Environment answers still depend on engaging the right stakeholder.

FAQ

Why did Business Environment grow so much in the July 2026 outline?

The domain rose from 8% with four tasks to 26% with eight, and now adds risk, change control, and issues and impediments to governance, compliance and organizational change. PMI's job task analysis also looked at trends such as sustainability and AI, which appear in compliance and risk enablers.

How many questions come from Business Environment?

PMI does not publish per-domain counts. Applying the 26% weight to 180 questions gives a planning estimate of about 47.

Is risk management in Process or Business Environment now?

In the July 2026 outline, Plan and manage risk is task 5 of Business Environment. Finance in Process still quantifies risk-based contingency, so the two domains connect.

What is the difference between a contingency plan and a workaround?

A contingency plan is prepared in advance for an identified risk and executed when its trigger occurs. A workaround is improvised for a risk nobody identified, and should be recorded so future identification improves.

Who approves changes on a PMP scenario?

Whoever the governance or change management plan names, typically a change control board or sponsor in predictive projects and the product owner for backlog content in adaptive ones. The project manager analyzes impact and facilitates the decision.

Where does PMBOK 7 fit into this domain?

Its Stewardship, Risk, Adaptability and resiliency, Change and Systems thinking principles, and the Uncertainty performance domain, explain why PMI prefers governance-respecting, impact-first answers. The exam tests the outline's tasks, not PMBOK 7 recall.

How long should I study Business Environment?

As a planning estimate, about 35 to 45 hours of a 150-hour plan. Add time if your materials were written for the 2021 outline, where this domain was much smaller.

Other Project Management certifications

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

Test your Domain 3 knowledge

Put this page's distinctions to work, from risk versus issue and change control paths to compliance and organizational change, in scenario questions aligned to the July 2026 PMP outline.

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

Keep going