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

Manage   »   Portfolio   »   Pipeline Project Sizes


Projects come in many sizes but broadly they tend to fall into the three main size categories: Small, Medium and Large. These are not very informative titles and all too often generate a great deal of unwelcome debate as the titles mean one explicit thing to one team and a very different thing to another. So in the Toolkit, we get away from that concern and use the Toolkit terms Small, Typical and Extensive. Let us explain.


The Toolkit processes agile projects and these will not normally be massive projects. No agile method counsels an agile approach for truly gigantic projects. We funded and carried out research to understand the best terms to use to describe lots of concepts inside the Toolkit and the naming of project type sis no exception.

The words Massive and Gigantic, and in fact large, are words that conjure up very specific images. Downpours of rain are images that are conjured up on mention of the word Massive and waves are immediately recognised with the word Gigantic. Large is seen in a wholly different context and summons image of obesity.

We wanted a title that identified a project that is readily identified as out of scope and a title that did not invoke alternative or negative images. So after a period of evaluation and research, we entitle this type of project: an Extensive project.

The Toolkit recommendation is to subdivide such projects into smaller manageable projects. Therefore a pipeline will never include Extensive projects and will comprise Small and Typical sized projects. The Toolkit provides the main Lifecycle to deliver Typical projects and Small Changes are provided for via the Small Change Process.


So you have the whole project estate covered regardless of what title you assign to what type of project. You have made your process of project assignment and classification easier. Once you identify your larger projects, the ones you can split, and set a defined threshold for small projects, the job is done and you can move onto something more focal and profitable.
Buffer



 Project RAG Status History     Project RAG Status History   Manage the Pipeline    Manage the Pipeline



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
Pipeline Project Sizes






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 144  Page: 153/444  Progress: 34.5%
 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.