order to permanently and irrevocably fix a problem doesn’t take very long compared to the total delays that a project can experience. The log is where you record any problems that were not accounted for in the plan and that threaten to delay the project, push it off budget or reduce the scope (e.g. reduce product performance). An example of the Issues Register matrix is below: Issue Log Project: Date: Issue Description Priority Category Reported Assigned Status Date Resolution/ (H,M,L) By To Resolved Comments This Detailed High, Assign to Who Who is What What What was should be description Medium a reported the is the date was the a standard of the or Low category. the assigned status the resolution numbering priority. issue? to? of the resolved? or what is system. being done to resolve the issue? In addition to the detail included in both documents, below are some of the key distinctions between the two documents. Issue Log Risk Register Description Description of the of the risk Underlying Risk problem or cause of of the issue uncertainty and the potential impact Action plan Potential actions Priority or Monitoring scheduling plan Who is Who is responsible responsible for for assuring monitoring this issue is resolved Date Date last opened updated, and date tracking ID resolved, sometimes a tracking number or other ID
order to permanently and irrevocably fix a problem doesn’t take very long compared to the total delays that a project can experience. The log is where you record any problems that were not accounted for in the plan and that threaten to delay the project, push it off budget or reduce the scope (e.g. reduce product performance). An example of the Issues Register matrix is below: Issue Log Project: Date: Issue Description Priority (H,M,L) Category Reported By Assigned To Status Date Resolved Resolution/ Comments This should be a standard numbering system. Detailed description of the High, Medium or Low priority. Assign to a category. Who reported the issue? Who is the assigned to? What is the status of the What date was the resolved? What was the resolution or what is being done to resolve the issue? In addition to the detail included in both documents, below are some of the key distinctions between the two documents. Issue Log Risk Register Description of the Description of the risk Underlying problem or cause of the issue Risk of uncertainty and the potential impact Action plan Potential actions Priority or scheduling Monitoring plan Who is responsible for assuring this issue is resolved Who is responsible for monitoring Date opened and date resolved, sometimes a tracking number or other ID Date last updated, tracking ID
2.a_CEWD_Project_Management_Templates.docx