This document outlines a risk management process that involves identifying risks, evaluating them at multiple levels, and escalating unresolved issues up the management chain. Key steps include creating risk lists, evaluating risks at the project core team and release core team levels, escalating unresolved issues to program management via an out-of-band process, implementing management decisions and corrective actions, and ongoing tracking and control of the risk plan. The overall process is aimed at eliminating risks following the defined risk mitigation and contingency plan.

1. Escalate to PMT via OOB Process
Unresolved Issue Identified
Evaluation by Project Core Team
Risk Plan Tracking and Control
Escalate to Manager or Program Manager
Risk Management Process Diagram
Legend:
Start –
Activity –
Condition –
Connector –
Flow of Info. –
Other Process –
Output -
End -
A
Resolved?Yes
Mitigation /
Contingency Plan
Needed?
Yes
Update Risk Plan
No
No
Escalate to Release Core Team
Resolved?
No
Yes
Resolved?Yes
No
A
A
A
Request for more
Information?
Yes
No
Create and Evaluate the Release / CTs Risks Lists
Implement the PMT Decisions and corrective actions

2. Process Owner: Program Manager Phase Ongoing
Entry Criteria: New Release Planning
Exit Criteria: Risks Elimination following the Risks Mitigation/Contingency Plan
Process Description: <text>
Measures: Risks Management Process
Activity Responsible Inputs Outputs
1. Create and Evaluate the Release / CTs Risks
Lists
Program Managers MRR
Presentation –
Risks slide
•Release / Projects CTs Risks list Created
•AIs/OIs are issued for follow-up.
2. Unresolved Issue Identified Projects /
Functional groups
staff
3. Evaluated by Manager and/or Program Manager Projects /
Functional groups
staff
Issue raised •Risks List Updated
•Mitigation/Contingency Plan defined /
updated (if required).
•Escalating unresolved issues to next
level. Multiple resolution options might
be applied.
4. Evaluated by Project Core Team Program Managers,
Product Managers
Summary of
the issue,
reason for risk
and options for
dealing with it
(emails,
meetings
discussion)
•Risk Plan Updated (if required)
•Escalating unresolved issues to next
level. Multiple resolution options might
be applied.5. Evaluated by Release Core Team Program Managers,
Product Managers
6. Escalate to PMT via OOB Process Program Managers •OOB Process
PPT
•OOB
Template filled
out
•PMT Decision - taking one of the
resolution alternatives or requesting for
more Info (based on the PMT
Presentation).
•AIs/OIs are issued for follow-up.
•Risk Plan updated accordingly

3. Process Owner: Release Manager & Program Manager Phase Ongoing
Entry Criteria: <text>
Exit Criteria:<text>
Process Description: <text>
Measures: Risks Management Process (Cont.)
Activity Responsible Inputs Outputs
7. Implement the PMT Decisions and corrective
actions
Release Manager,
Program Managers
PMT MoM,
AIs/OIs
The decisions can be either release
descope, accepting risk plan, assigning
more resources or changing milestones
schedule. A as result, the appropriate
Release Plans and documents should be
updated following by issuing new
AIs/OIs.
7. Risk Plan Tracking and Control Release Manager,
Program Managers
Risks Plan •Risk Plan updated (if required)
•Issuing appropriate AIs/OIs to projects
teams (updating Release plans,
documents etc)
Assets/References