Skip to content
PMPCAPM

Enterprise Environmental Factors (EEFs)

Enterprise Environmental Factors (EEFs) are conditions, not under the immediate control of the project team, that influence, constrain, or direct the project.

Share:

Know it well enough for the exam? Questions on Enterprise Environmental Factors (EEFs) are scenario-based, not definitional.

Practice it free

Explanation

EEFs are the internal and external conditions that surround a project and shape how it is planned, managed, and executed. Unlike Organizational Process Assets, which the project team can often update or leverage, EEFs are typically conditions the team must work within and cannot change.

Internal EEFs include organizational culture, structure, and governance; infrastructure and existing resources; employee capability; internal political climate; and information technology systems. External EEFs include marketplace conditions, regulatory and legal requirements, industry standards, social and cultural influences, physical environmental conditions, and commercial databases.

EEFs appear as inputs to nearly every process in the PMBOK Guide because they affect virtually every decision the project team makes. For example, government regulations (an external EEF) may dictate specific compliance requirements for the project. Organizational culture (an internal EEF) may determine how much authority the project manager has. Understanding and accounting for EEFs is essential for realistic planning and effective decision-making.

Key Points

  • •Conditions the team cannot directly control but must account for
  • •Include both internal (culture, structure) and external (regulations, markets) factors
  • •Appear as inputs to most project management processes
  • •Influence planning, decision-making, and project constraints

Exam Tip

The key distinction: EEFs are conditions you work WITHIN (you cannot change them), while OPAs are assets you USE and can UPDATE. If the exam describes something the team cannot control, it is an EEF.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Predictive Life Cycle (Waterfall)

A predictive life cycle is a plan-driven approach where the project scope, schedule, and cost are determined early and changes are carefully managed.

Subsidiary Plans

Subsidiary plans are the individual management plans that are components of the overall project management plan, each addressing a specific Knowledge Area or management function.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Part of

PM Fundamentals & Frameworks

Study full domain →

Practice Enterprise Environmental Factors (EEFs)

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.