Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Project RAG Status  Project RAG Status   Pipeline Project Sizes   Pipeline Project Sizes

Manage   »   Portfolio   »   Project RAG Status History


Do we need to do this, really? Well it is not correct to say you need to do this but in our experience you will benefit, if at some point, you can evidence that the organisational transformation to agile or the introduction of techniques to create high performance teams has positive measurable and accepted results. The history of successfully improving the Rag status is a simple effective way to ensure you can do this easily and swiftly.

Across the organisation, record the RAG status for all participating projects and swiftly you will get positive results such as these below from a recent investment banking customer.



Across the organisation, the real benefit of recording and demonstrating the RAG status history is that there is readily available and simple method to show the success of the overall change to a positive project delivery environment. Every project team member though feels a part of this success and we find that various team members will start to ask which the RED status projects are as they become rarer and more unusual.



This is a powerful graphic to take to your organisational status meeting demonstrating that the organisation is both more successful at delivering projects and more efficient, delivering an extra 45 projects in this example. You will notice that this client uses the term Cancelled instead of Disengaged for those halted projects which have their resources removed.



The other item of note about the graphs is that, although the white coloured sector for LIVE projects looks the same size in both cases, it is not. The number is larger by about 15% and demonstrates that you will be completing and delivering more project output into the live environment. In this way, you will be adding more value to the organisation in the process.
Buffer



 Project RAG Status     Project RAG Status   Pipeline Project Sizes    Pipeline Project Sizes



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
Project RAG Status History






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 143  Page: 152/444  Progress: 34.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.