Assess the Project Environment for Threats and Opportunities

Risk doesn't exist in a vacuum — it exists inside a specific organization, with its own tolerance for uncertainty, its own tools, and its own blind spots. This task is about reading that environment before planning a single risk response. It starts with identifying which organizational process assets and enterprise environmental factors actually apply, and which development methodology — predictive, agile, or hybrid — the project is using, since that shapes how risk gets managed day to day.

From there, the risk manager analyzes the environment itself: PESTLE (Political, Economic, Social, Technological, Legal, Environmental) and SWOT analysis are the named tools for scanning external and internal factors. Determining the organization's actual risk appetite — and its risk culture maturity, since a stated appetite and a lived one are often different — matters just as much as the external scan. A stakeholder analysis, a look at constraints (government and market rules, organizational limits, environmental and technical risk), and a clear read on the project's business driver, key assumptions, and expected benefits round out the picture.

Study focus: PMI frames this task as building the case for risk awareness as a culture, not just a checklist — part of the job is actively focusing stakeholders on creating that culture, not simply documenting the environment and moving on.