Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Readiness Declaration Objective  Readiness Declaration Objective   Readiness Quotient   Readiness Quotient

We humans, assuming all readers are from the Human Race or at least closely related to it, like to use numbers and percentages and we like to satisfy our readers demands. This is why we assign numbers to the responses from the Declaration. Moreover we know that humans also gravitate towards the simple solution too. With this in mind we use a simple numbering system to identify and derive a helpful Readiness Response quotient. Here goes:

A response of accept is one point, a response of confirm is two points, a response of debate and contest are minus 1 and minus 2 respectively. A nil response is minus 2.

A nil response where the respondent is unable to respond is minus 2 because something is missing or has gone wrong.

If we assume the attendee understands the statement then we will deduce the attendee has not enough information to respond to the statement.

There are no simple explanations to why this occurs but it is an important piece of data. If there is no response from the attendee to one or more of the statements, then this tells us something important.

If we remember that our attendees are important knowledgeable stakeholders for the project, this means an important stakeholder is unaware of one or more of the key components to the project.

This communications gap needs to be filled by a more knowledgeable or maybe a missing stakeholder or fixed by an existing one.


The responses to the Declaration represent the landscape in which you are going to run your project. It is important that all key stakeholders know the landscape, what is present and what is missing. Once the Readiness Declaration is complete, the whole project has had a chance to comment on the proposed project landscape, they know what this is and they can demonstrate the starting point they were provided with. Everything missing or broken is a risk and documented as such. These are managed and adjusted as the project progresses.

Remember the Readiness Declaration is a statement of the position of the proposed project landscape in which you intend to operate your project. You may elect to change this as a result of the information you have uncovered as part of the Readiness Declaration but you leave the Readiness Declaration as it is. It is a record of AS IS circumstances of the proposed project starting position.
Buffer



 Readiness Declaration Objective     Readiness Declaration Objective   Readiness Quotient    Readiness Quotient



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
Quantifying Readiness Responses






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 245  Page: 372/444  Progress: 83.8%
 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.