What risk response strategy involves removing high- risk scope elements from a project?

In accordance with the PMBOK® Guide, the Plan Risk Responses process identifies several strategies for dealing with negative risks or threats.

Avoid: Risk avoidance is a strategy where the project team acts to eliminate the threat or protect the project from its impact. This typically involves changing the project management plan to eliminate the risk entirely. Common examples of avoidance include extending the schedule, changing the strategy, or, as mentioned in the question, reducing or removing scope that is deemed too high-risk for the organization to manage.

Transfer: This involves shifting the impact and ownership of a threat to a third party (e.g., through insurance, performance bonds, or warranties). It does not eliminate the risk from the project scope; it simply makes another party responsible for the financial consequences.

Exploit: This is a strategy used for positive risks (opportunities), not threats. It seeks to ensure that the opportunity is realized.

Accept: This strategy indicates that the project team has decided not to act against a risk. It can be passive (doing nothing) or active (establishing a contingency reserve).

Per PMI standards, when a project manager decides that a specific technical deliverable or scope element is beyond the team ' s risk appetite, the most effective way to " Avoid " that risk is to remove that requirement from the project scope statement.