Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Build and Fix Example  Build and Fix Example   Build and Fix Processes   Build and Fix Processes

The Minimum Acceptable Delivery (MAD) is the smallest amount of usable functionality that you will accept as a working solution and that you can work with. Popular prioritisation techniques, such as MoSCoW, call this feature the minimum usable subset which is a term that describes nothing and means little to most people we work with. It appears the term comes from being forced into an acronym (MUST) to represent the Minimum Usable SubseT.

However, the Minimum Acceptable Delivery is exactly what it says. So, within the Toolkit, we do not have a minimum acceptable development or a minimum acceptable release. It will be a delivery. It will be acceptable to you and include a minimum amount of mandatory functionality. Remove any part of the Minimum Acceptable Delivery and the solution will not work or will not derive the benefits you anticipated. The Minimum Acceptable Delivery is described in terms of products and requirements. You will define the products that are mandatory for Minimum Acceptable Delivery and list the requirements that will be present to fulfil satisfactory delivery. The Minimum Acceptable Delivery is estimated at the start of the project in the Survey phase and is part of your delivery Commitment.

The Minimum Acceptable Delivery is enshrined in the Delivery Commitment and a team member signs up to deliver the Minimum Acceptable Delivery at the end of the Setup phase.

So Minimum Acceptable Delivery it is then, you would be MAD to take anything less.



Buffer



 Build and Fix Example     Build and Fix Example   Build and Fix Processes    Build and Fix Processes



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
Minimum Acceptable Delivery






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 288  Page: 247/444  Progress: 55.6%
 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.