PMP - Business Environment (8% of the exam) - Section 3.3

Evaluate and address external business-environment changes for impact on scope, and support organisational change throughout the project.

Survey changes to the external business environment - regulations, technology, geopolitical, and market shifts - and assess and prioritise their impact on project scope and backlog, recommending options such as schedule or cost changes. Assess the organisational culture and the impact of the project's change on the organisation, and recommend actions to support the change so it is adopted and sustained.

External business environmentOrganisational change managementScope impactOrganisational culture

Practice question for this objective

Free sampleBusiness Environmenthard

Midway through a predictive project to build a customer records platform, a new national data-protection regulation is enacted that will take effect before go-live. The project manager learns of it through an industry bulletin. What should the project manager do FIRST?

  • ASubmit a change request that adds the required compliance features so the team can begin the rework straight away.
  • BAssess how the regulation affects the current scope and deliverables, then take the findings through integrated change control. Correct
  • CWait until the regulator publishes detailed implementation guidance so that no effort is wasted on premature rework.
  • DEscalate to the sponsor to decide whether the project should continue under the newly enacted rules.
When the external environment changes, first assess its impact on scope before routing any adjustment through integrated change control. A regulatory change is an external business-environment event. The project manager must survey the change and analyse how it affects scope and deliverables so that any adjustment is evidence-based and processed through integrated change control, rather than committing to rework or decisions before the impact is known.

Why A is wrong: It feels decisive, but raising a change request before any analysis commits the project to scope and cost changes that have not been assessed or validated against the regulation.

Why B is correct: Surveying the external change and analysing its impact on scope before acting is the correct first step, and integrated change control is where any resulting change is formally evaluated and approved.

Why C is wrong: Waiting looks prudent about rework, yet it delays understanding a change that lands before go-live and lets impacts on scope and schedule grow unmanaged.

Why D is wrong: Escalation may be needed later, but handing the sponsor a decision with no impact assessment is premature and skips the project manager's job of first understanding the effect.

See more PMP practice questions, answers explained.

Exam traps in Business Environment

Answers that look right on this material and are not. Each one is a distractor from a different question in the PMP bank for this domain.

  • Remove the affected features from the backlog so the team is not blocked while the regulation is interpreted.

    Why it is wrong: Deleting backlog items destroys value the business may still need and pre-empts analysis; the features may be deliverable with modest changes once the impact is understood.

  • Defer engaging the department until the system is fully built so that staff respond to a finished product rather than a plan.

    Why it is wrong: Waiting for a finished product seems tidy, but late engagement deepens resistance and forgoes the input that helps staff prepare for and accept the change.

  • Direct the team to keep delivering the current sprint backlog unchanged in order to protect the committed release date.

    Why it is wrong: Protecting the release date sounds disciplined, but ignoring a real shift in customer value delivers a product the market no longer wants and misreads agile change tolerance.

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