Risk and Opportunity Escalation Policy

EFFECTIVE DATE: October 13, 2016

APPROVED BY: Mike McCoy

LAST UPDATED: May 27, 2019

PURPOSE

The purpose of this document is to establish the policy regarding the escalation of project related risks and opportinties within InnovaSystems, International LLC (ISI).

SCOPE OF THE POLICY

This policy defines the standards to escalate project related risks and opportunities to the executive team and is applicable to all ISI software development project teams developing software business solutions and services.

APPLICABILITY

Responsibility for managing and ultimately escalating risks and opportunities to the executive team belongs to the Project Manager. Business Unit Leads must ensure the project managers are adhering to this policy for direct escalation to the Executive Team.

AUTHORITY AND COMPLIANCE

This policy is authorized by the Chief Operating Officer (COO). Compliance to this policy is be evaluated through an appraisal/audit process. Results will be provided to the appropriate personnel and non-compliance/issues will be submitted to the Business Unit Leads and the Executive Team for remediation.

POLICY STATEMENT

This policy is intended to establish a Risk and Opportunity Escalation to ensure project personnel are tracking and escalating likelihood and impact of risks and opportunities to the executive team (via the Business Unit Lead) for organizational level tracking and mitigation where appropriate.

InnovaSystems shall:

  1. Define a set of processes to establish structure and expectations for the execution of risk and opportunity escalation activities
  2. Escalate any project risks or opportunities for executive level communication and potential remediation where the risk or opportunity reaches or exceeds moderate levels of exposure.
  3. Escalate project risks or opportunities to executive leadership in the form of Azure Dev-Ops risk or opportunity work items.
  4. Escalate project risks pertaining to customer/stakeholder satisfaction: communication and participation.
  5. Escalate project risks or opportunities pertaining to schedule: dependencies, delays, uncertainty.
  6. Escalate project risks or opportunities pertaining to scope: changes and complexity.
  7. Escalate project risks or opportunities pertaining to operating environments: changes and outages.
  8. Escalate project risks or opportunities pertaining to employee performance/morale.
  9. Escalate project risks or opportunities pertaining to product licensing: changing costs, expiration, change in terms.
  10. Escalate project risks or opportunities pertaining to over/under execution of funds: plan changes and actual changes.
  11. Escalate project risks or opportunities pertaining to the technical solution: usability, availability, security and stability.
  12. Escalate project risks or opportunities pertaining to product quality: process, technical debt and deployed defects.
  13. Include risk and opportunity management as a weekly item for discussion at executive staff meetings and provide feedback back to project management through the Business Unit Lead (BUL).

Process Guidance Version: 10.4