![]() Escalate risks as identified in risk management planning, monitoring and reporting requirements chart. If the risk’s score indicates the risk is high or very high, address this risk by assigning a risk response and identifying the individual who will be responsible for taking action and monitoring the results. If the risks scores indicate the risk is very low, low or medium, monitor the risks. Evaluate the risks according to the University’s and other stakeholder’s risk appetite.Analyse the risks for likelihood and impact and assigned risk ratings.Identify risks, with special attention to review the risks in the risk register in Appendix A of the Risk Management Reporting Guideline.Collect all inputs: scope baseline (scope statement, requirements, WBS), risk management plan, cost management plan, schedule management plan, quality management plan, human resource management plan, activity cost estimates, activity duration estimates, procurement documents, stakeholder register, project documents and University Policy 11.Some Project/Program Managers may use others tools such as ACE Project or RT as their issues log and just use this document for risks, actions, and decisions. Some Project/Program Managers prefer to be the sole author, and some allow others to update. The Project/Program Manager will have to create a process for ensuring the RAID log is kept up to date and proper version control occurs based upon the requirements of their project/program. Sometimes others may be providing updates, especially to the issues log. The author and maintainer is often the Program/ Project Manager. ![]() ![]() Another valuable source would be documentation (risks, issues, lessons learned, et cetera) from other projects that may be similar in nature. Input into the RAID log will come from many sources such as the Information Risk Assessment (IRA) process, project documentation (charter, business case, intake form, meeting minutes, et cetera), sponsor, project team members, and other stakeholders. It is a dynamic document that is constantly maintained throughout the project/program. The right level of detail needs to be determined for the RAID log, dependent upon the project/program so that it is an effective tool for audits, governance, and oversight of the project/program. The decision long records information such as decision description, date, who decision was made by for decisions made in the project/program. The issues log records information such as issue description, owner, resolution, et cetera for known problems that have occurred (if a risk triggers, it becomes an issue as well). The actions log records information such as owner, due date, completion date, et cetera for things that need to be done. The risk log records information such as triggers, probability, impact, mitigation, owner, et cetera for things that could go wrong but have not yet occurred. RAID Log (risks, actions, issues, decisions) (XLSX) Purpose of RAID LogĪ RAID log is a simple, effective project/program management tool to organize a project/program by tracking risks, actions, issues, and decisions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |