Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Unsolvable Conflict  Unsolvable Conflict   Version Control   Version Control

Lifecycle   »   Forum   »   RAID Log Review

The RAID Log review takes place immediately after the Daily Forum.

Experience has shown us that it is not necessary for all team members to go through the whole RAID Log in the Daily Forum. What we have found, the best solution is to allow all team members to introduce or cancel a risk during the Daily Forum. Then later, after the Daily Forum is completed, go through the high-risk items in the RAID Log. We try to do this with as few people as possible. We find it works more efficiently and quicker that way. This is called the daily RAID Log review.

It is called the daily RAID Log review because we review the RAID Log and this includes all risks, assumptions, issues and dependencies (as well as constraints if you have these in the RAID Log as well) are given an airing. Incidentally if you permanently include constraints in the RAID it is most appropriately termed the CRAID Log. We have found that you do not need to go through assumptions, dependencies and constraints as often as you do for the risks and issues. But all need to be passed across the team at some point in the project. There is a very good reason for this too.

By hearing about an issue, it means you are aware of it. Often an issue is unrelated to your sphere of influence. However, if you perform an activity that even remotely adversely influences the issue you will start to avoid performing this activity. Thus by simply communicating issues across the project to all team members you are macro-optimising the project environment by triggering the collective influences and activity of the group. All agile development tells us that constraints are difficult to find, unblock and manage. Therefore, in this way you manage to evade the maximum damage from a constraint by opening it up to a whole team to steer clear of it, avoid making it worse and overcoming it as a group.

It is called a review because it is an opportunity to revisit, reassess and re-evaluate the risks we have identified on the project. It is called a daily review because you want to revisit these risks every day. There will be days when time and other pressures dictate that you just cannot perform the daily RAID Log review. You have to prioritise your time. In this instance, you will have to cancel the daily RAID Log review. Beware, once your team members see that you are prepared to cancel this meeting, they will seek to avail themselves of this opportunity at the very next juncture. Remember you have the Commitment of the RAID Log owner that you will not cancel any more than a pre-agreed number of daily RAID Log reviews. More information, see the Toolkit section that deals with Engagement Commitment.

For now we consider the scenario that when we finish this project and we hand over to a new set of people the responsibility to run and maintain it. These teams need to be honed and prepared to take the responsibility of the new solution professionally and completely.


 Unsolvable Conflict     Unsolvable Conflict   Version Control    Version Control

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 Review


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 300  Page: 263/444  Progress: 59.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 ( 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.