Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 RAID and the Daily Forum  RAID and the Daily Forum   RAID Log RAG Status   RAID Log RAG Status

Whoever is your day-to-day business contact, they would normally be the person to go through the RAID Log daily. They are known as the RAID Log owner. The RAID Log owner should be the final and default owner of all risks, particularly the high level risks, which are outstanding. They will chase up and follow through all risks. At the end of the project, the RAID Log owner will be asked to sign off all risks which remain to go ahead with the project on that basis. This is why, it is important that the RAID Log owner manages all the risks, daily. There is no excuse, at the end of the project or at any point throughout the project, why the RAID Log owner should be unaware of any risk or any issue associated with a risk.

Right, let us look at the mechanics of actually doing this. Your Daily Forum has completed and the participants are gradually leaving the room. Begin your daily RAID Log review immediately. There is no need to wait until all participants in the Daily Forum have left. Some people like to hang back and listen to other things that are going on in their project. We run an open door policy, so allow them to listen in. Remember, we are going to look at the higher risks only. Watch, as you near the end of a project, that low or medium risks do not suddenly become a high risks, causing an urgent problem.

let us begin. Go through the RAID log, take each risk in turn. Each entry in the RAID Log is numbered. Read out the number. Read out the description of the risk, if that is necessary. You want the answer to one question, first. Is the risk dead or alive?

If the risk is dead mark it as cancelled and date it. Then, move onto the next risk.

If the risk is alive, you want the answer to another question. Is the risk still a high-risk? If the status of the risk is changed, mark it as changed, date it and move onto the next risk.

If the risk is still a high-risk, then we need the answers to 3 questions

  1. Is the person identified as the risk owner, the right owner of the risk?
  2. Is the dates by which the risk will be mitigated, still achievable?
  3. Is there anything the risk owner, the RAID Log owner or anybody else in the team able to do to remove, minimise or mitigate this risk?


If your change of honour or change of date, then update the RAID Log, date it and move onto the next risk. If there is a further action that someone in the team can perform to help get rid of this risk, specify what that action is, who is going to perform the action, what date the action will be completed by in the RAID Log and move onto the next risk.

You can see, this review can be performed very quickly indeed. The more times you do it, the faster it becomes. But doing this every day, reminds you that these risks exist and need managing. Every day, the RAID Log owner is reminded of their responsibility and is given the opportunity to remove a risk, delegate a risk and manage it out of the project.

The psychological game play that occurs during these reviews is worthy of a book in its own right. Maybe this is an opportunity for someone else, some other day. For now, it is worth saying that the realisation of their responsibilities very swiftly dawns on those who attend the review.

Each risk is reviewed daily. People get sick of hearing the same things, over and over. This in itself can trigger some people into action. Risk owners swiftly become aware that there is written evidence of the length of time it is taking them to manage out this risk.

If this information is used positively in managerial performance reviews, it is a great opportunity to demonstrate your professional risk management skills to your management. The evidence is there for all to see and this information can be used for the purposes of escalation by the RAID Log owner.

Your communications Commitment ensures that anyone across the project can instigate or add a new risk. So everyone across the project knows that if they identify a risk, there is a forum where it will be debated.

They know that, all they have to do is hang around after the Daily Forum and they will hear a little bit more about it. If their interest in the risk is not that urgent, they can browse the RAID Log. This is an open document.

Buffer



 RAID and the Daily Forum     RAID and the Daily Forum   RAID Log RAG Status    RAID Log RAG Status



Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z


#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
RAID Log Maintenance






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 370  Page: 325/444  Progress: 73.2%
 About    |    Author 
Follow @BigAgileToolkit


This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL (http://www.bigagiletoolkit.com/) and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.