SAB5#139_Control_Risk

Anmerkungen:

• If you are constantly reviewing all of the data your Project is producing, you will be able to react quickly if a new risk is uncovered, or if looks like one of your response strategies needs to spring into action.  

1. Risk Register
2. Project Management Plan

   Anmerkungen:

   • You compare all of your actual data to your plans using the risk register and the PM plan.
3. Work Performance Data

   Anmerkungen:

   • You should review status reports, metrics, and other work outputs to see if risks are happening
4. Work Performance Reports
5. Work Performance Information

   Anmerkungen:

   • This is the analysis of the work performance data gathered during Project work. This set of documents needs to be updated any time your plans changed
6. Risk reassessment
7. Variance and trend analysis
8. Reserve analysis

   Anmerkungen:

   • Sometimes this kind of reserve is called a "contingency" - because its use is contingent on a certain risk happening.
9. Risk audits

   Anmerkungen:

   • Auditors will also look at how effective your overall processes for risk planning are
10. Technical performance measurement

    Anmerkungen:

    • Comparing the performance of your Project with its planned performance.
11. Meetings

    Anmerkungen:

    • Meetings are the most important way to keep the team up to date on risk planning. Every single status meeting should have risk review on the agenda. Status meetings are a really important way of noticing when things might go wrong, and of making sure that you implement your response strategy in time. 
12. Risk Register

    Anmerkungen:

    • Outcomes of the risk reassessment and risk audits Results of implemented risk responses Updateds to previous parts of risk management, including the indentification of new risks Closing of risks that are no longer applicable Details of what happened when risk occurred Lesson learned
13. Project Management Plan

    Anmerkungen:

    • Approved changes or additional information gathered
14. OPAs

    Anmerkungen:

    • The creation of risk templates (such as a risk register including Project risks and risks responses), checklists, other data to be used as historical records for future projects.
15. Change Request

    Anmerkungen:

    • Change requests to integrated change control for analysis and review.