risks-management-5Risks are any factors that may potentially interfere with successful completion of the project.

Risk is not a problem: a problem is a situation that has already occurred; a risk is the recognition that a problem might occur. By recognizing potential problems, the Project Manager can attempt to avoid or minimize a problem through proper actions.

It is important to plan for the risk management process to ensure that the level, type and visibility of risk management are commensurate with both the risk and importance of the project to the organization.

This activity should define the approach, tools, and data sources used to perform risk management on this project. Different types of assessments may be appropriate, depending upon the project stage, amount of information available, and flexibility remaining in risk management.

risks-management-6The Project Team should identify potential project risks in addition to key risks identified during the initiation phase. For each identified risk, the team should:

  • Assess impact and probability of risk occurring
  • Assign a risk priority
  • For high-priority risks, determine a risk response approach including any contingency plans.

The Project Team’s approach to risk is documented in the:

  • Risk Management Schedule – A detailed schedule for risk-related activities
  • Risk Management Plan – How the team will manage risk throughout the project.

Actual data regarding identified risks can be found in the Risk Response Plan document (details all identified risks, risk priorities, contingency plans, etc.).

risks-managementDetermine Process for Issue Identification and Resolution: The purpose of the issue management process is to provide a mechanism for organizing, maintaining and tracking the resolution of issues that cannot be resolved at the individual level. The approach consists of issue control mechanisms and a well-defined process that enables the Project Team to identify, address and prioritize problems and issues.

  • The Project Team records all details related to issues and issue resolution in the Issue Document.
  • The Issue Log serves as a reference to all Project Issues.

Determine Process for Managing Scope Change: Project scope management can be just as important to scope planning as the Scope Statement itself. This effort describes how the project scope will be managed and how scope changes will be integrated into the project.

The scope change management process:

  • Defines a process for identifying and documenting potential changes to scope
  • Defines a process for review and approval of scope change
  • Describes which planning documents need to be revised due to scope change.


risks-management-4Develop Organization Change Management Approach: Some of the details related to organizational change management will not become apparent until the completion of detailed design of the solution. The expectation during the Planning phase is to develop a high-level understanding of the impact of the project on the organization.

The Project Team will:

  • Identify potential organizational changes and impact
  • Refine business process improvement opportunities
  • Identify training needs (e.g., magnitude)
  • Determine knowledge transfer resources and processes
  • Document all of this in the Organizational Change Management Plan.