Quick idea: Action / Risk Log

[Bernhard Rode]

It would be great to have a Action/Risk log.

It might be realized through the Ticket System.

[sid]

You probably should explain what you envision a little more here.

[Matthew Good]

We really need some details to understand what you're proposing. I'm not familiar with the term "Action/Risk log".

[Christian Boos]

Yes, you can take the description of #2071 as an example of how to present the concepts and discuss how they could be integrated within Trac.

[typesmith@…]

Maybe this helps (I was also looking for a risk register/Log when I stumbled across this)

Credit for this doc goes to JISC infoNet www.jiscinfonet.ac.uk Risk Management PDF © Northumbria University. This material is licensed under the Creative Commons License.

What is Risk Management? 'Risk management is a systematic process of identifying, analysing and responding to project risk.' This may be broken down into a number of sub−processes which JISC infoNet have used as the basis for the model in this Kit: · Risk Identification · Qualitative Risk Analysis · Quantitative Risk Assessment · Risk Response Planning · Risk Monitoring and Control

The Risk Log An essential tool in any project management methodology is the Risk Log or Risk Register. This provides a means of recording the identified risks, the analysis of their severity and the necessary management actions to be taken. The risk log can be a simple document or spreadsheet or can be a database system. The JISC infoNet Project Controls Database includes a risk log as part of its functionality − the link here takes you to a page where this can be downloaded and full instructions for its use are provided in the accompanying User Guide. As a general guide any Risk Log should contain the following data fields:

Unique ID This may be simply a title but some kind of alphanumeric coding is likely to be useful where you are dealing with a large number of risks.

Description Presented in a structured format: Condition − 'There is a risk that' Cause − 'Caused by' Consequence − 'Resulting in'

Probability What is the likelihood of the risk occurring? It would be helpful to record the justification behind this analysis.

Impact What will the impact be if the risk occurs? It would be helpful to record the justification behind this analysis.

Timescale What is the 'Risk Window' when this risk may occur and when do you start to lose options as to how you respond?

Cost What will the risk cost if it does occur? N.B. You can't assess this unless you know what your response action will be.

Owner There should be a person nominated to 'own' the risk which means monitoring the situation and ensuring that necessary management actions are carried out. In a project situation this should be somebody within the project team and in all cases it should be somebody who will be impacted by the risk and who has a vested interest in addressing it.

Management Approach What are the agreed response actions? These may be broken into: · preventative actions to mitigate the risk and the response action if the risk actually occurs. This is sometimes known as an 'Impact Plan'.

Residual Risk This is the expected level of risk once all the mitigating actions are complete.

Early Warning Signs What 'trigger' might alert you to the fact that the risk is about to occur? In some cases you may only choose to spend money on a response action once the trigger occurs.

You may also want to note any interdependencies between risks i.e. where one risk occurring impacts on another risk. This is sometimes known as 'Risk Coupling'. This cross−reference alerts you to the fact that when one risk occurs a related risk also requires reviewing.

or another version culled from an excel sheet.

ID
Date Raised
Raised By
Received By
Description of Risk
Description of Impact
Likelihood Rating
Impact Rating
Priority Rating
Preventative Actions
Action Resource
Action Date
Contingency Actions
Action Resource
Action Date

[anonymous]

Replying to mgood:

We really need some details to understand what you're proposing. I'm not familiar with the term "Action/Risk log".

Details Added Below…

[Matthew Good]

Ok, it sounds like you're looking for something like ​WhatWhat Status. I don't think this is going to be a priority for the Trac core at this time, but it could certainly be handled as a plugin.

[Christian Boos]

This won't probably get implemented in Trac core, but a big part of the work that I'll focus on in next versions will be to ease the creation of new types of Trac resources, so that plugins won't have to redo everything (nearly) from scratch. See GenericTrac.