Dashboard > SUNY Learning Network 2.0 > Homepage > Risk Register
  SUNY Learning Network 2.0 Log In View a printable version of the current page.  
  Risk Register
Added by Ken Udas, last edited by Ken Udas on Aug 04, 2005  (view change)
Labels: 
(None)

Risk Register

ID Nature of Risk Probability Impact Containment Measure
001 Rouge modifications to the project Blueprint, causing confusion and inconsistent messaging about what the Project is committed to and what is under discussion. High Medium/High
  • Use of restricted editing privileges on the body of the project Blueprint wiki.
  • Protocols about use of the ¿Comments¿ feature to raise issues and identify areas to be modified.
  • Use of ¿Watching¿ wiki pages to monitor changes within the wiki.
  • Provision of ample open wiki space within the Blueprint for contributing resources.
002        
003        
004        
005        
006        
007        
008        
009        
010        


What's the process for sub-project managers to add risks to the registry?

Posted by Michael Feldstein at Aug 05, 2005 10:36 | Permalink

How about we create a Project Leads list and allow editing permissions, so if anybody on the project team wants to update the risk register they go through the project lead. We can then discss the new items in Confluence and within a regulare meeting.

Thoughts????

Posted by Ken Udas at Aug 10, 2005 17:19 | Permalink


A Project Leads list is a good idea.

Posted by Michael Feldstein at Aug 11, 2005 13:43 | Permalink
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.3 Build:#518 Jun 09, 2006) - Bug/feature request - Contact Administrators