Risk Log

From IT frameworks

Jump to: navigation, search

Purpose: To identify, analyze and manage risks tangible to the project

Should contain:

  • Identifier (Who found the risk)
  • Description
  • Category (Service Design should design categories)
  • Impact (based on impact model - technical, design, user-friendly, whole project)
  • Probability (Have a pre-defined model)
  • Proximity (Time based)
  • Counter-measures (To avoid the risk)
  • Owner (Assign a risk owner who will follow the risk)
  • Author
  • Date
  • Last updated
  • Current status

Document template