Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Contents  >  Estimating  >  Planning  >  Transformation  >  Lifecycle  >  Readiness  >  Commitments  >  Disengagement  >  Testing 
 Why Agile ?  >  Why Now ?  >  Projects  >  Programmes  >  Techniques  >  Management  >  Time  >  Quality  >  Cost  >  Agile Sucks 
My agile approach -fill in name of approach- is best  My agile approach -fill in name of approach- is best   Large companies dont do agile  Large companies dont do agile
Short iterations do not give enough time to develop proper new functionality. We hear this comment a lot. It is understandable. If you have a certain level of new functionality that you wish to include in your next demonstration release, then you need enough time in which to do it. If the iteration that contains this effort is not big enough to accommodate that effort, then the iteration is the wrong size. If your estimate is correct, if you are certain or as certain as you can be about the time taken to deliver this new functionality, then the iteration will cover that estimate. If you are at the start of your project, then you need to get back into planning mode. Take another look at that iteration to make sure it is going to have enough time. You are faced with the option to deliver a half developed release or a half developed demonstration. Otherwise, you are forced to move your release demonstration to the next iteration. The latter option puts pressure on subsequent iterations while the former option reduces the confidence of your business team in your ability to deliver a quality solution. Neither is beneficial, so re-plan. If you are halfway through your project, then you still need to get into planning mode and re-plan the project fast.

Buffer


My agile approach -fill in name of approach- is best     My agile approach -fill in name of approach- is best   Large companies dont do agile    Large companies dont do agile



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
Agile iterations are too short




   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™    
Topic: 418  Page: 420/444  Progress: 94.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.