Your SlideShare is downloading. ×
Risk management process diagram
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Risk management process diagram

533

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
533
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Escalate to PMT via OOB ProcessUnresolved Issue IdentifiedEvaluation by Project Core TeamRisk Plan Tracking and ControlEscalate to Manager or Program ManagerRisk Management Process DiagramLegend:Start –Activity –Condition –Connector –Flow of Info. –Other Process –Output -End -AResolved?YesMitigation /Contingency PlanNeeded?YesUpdate Risk PlanNoNoEscalate to Release Core TeamResolved?NoYesResolved?YesNoAAARequest for moreInformation?YesNoCreate and Evaluate the Release / CTs Risks ListsImplement the PMT Decisions and corrective actions
  • 2. Process Owner: Program Manager Phase OngoingEntry Criteria: New Release PlanningExit Criteria: Risks Elimination following the Risks Mitigation/Contingency PlanProcess Description: <text>Measures: Risks Management ProcessActivity Responsible Inputs Outputs1. Create and Evaluate the Release / CTs RisksListsProgram Managers MRRPresentation –Risks slide•Release / Projects CTs Risks list Created•AIs/OIs are issued for follow-up.2. Unresolved Issue Identified Projects /Functional groupsstaff3. Evaluated by Manager and/or Program Manager Projects /Functional groupsstaffIssue raised •Risks List Updated•Mitigation/Contingency Plan defined /updated (if required).•Escalating unresolved issues to nextlevel. Multiple resolution options mightbe applied.4. Evaluated by Project Core Team Program Managers,Product ManagersSummary ofthe issue,reason for riskand options fordealing with it(emails,meetingsdiscussion)•Risk Plan Updated (if required)•Escalating unresolved issues to nextlevel. Multiple resolution options mightbe applied.5. Evaluated by Release Core Team Program Managers,Product Managers6. Escalate to PMT via OOB Process Program Managers •OOB ProcessPPT•OOBTemplate filledout•PMT Decision - taking one of theresolution alternatives or requesting formore Info (based on the PMTPresentation).•AIs/OIs are issued for follow-up.•Risk Plan updated accordingly
  • 3. Process Owner: Release Manager & Program Manager Phase OngoingEntry Criteria: <text>Exit Criteria:<text>Process Description: <text>Measures: Risks Management Process (Cont.)Activity Responsible Inputs Outputs7. Implement the PMT Decisions and correctiveactionsRelease Manager,Program ManagersPMT MoM,AIs/OIsThe decisions can be either releasedescope, accepting risk plan, assigningmore resources or changing milestonesschedule. A as result, the appropriateRelease Plans and documents should beupdated following by issuing newAIs/OIs.7. Risk Plan Tracking and Control Release Manager,Program ManagersRisks Plan •Risk Plan updated (if required)•Issuing appropriate AIs/OIs to projectsteams (updating Release plans,documents etc)Assets/References

×