Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Types of Change  Types of Change   Small Change Request   Small Change Request

Lifecycle   »   Change   »   Small Change Process


The objective of the Small Change Process is to provide the fastpath way to prioritise, gain approval and swiftly progress smaller changes so these can be delivered and their benefits can be realised swiftly. What classifies a Small Change in your organisation would need to be defined so that project personnel know when a project is Small Change or not. You may elect to categorise projects by money or by days: i.e. planned budget is below a certain financial threshold or the number of days is below a certain numerical threshold.

Whichever method you choose it will need to support the amount of information you have about projects and the level of detail you have when you come to decide whether a project is Small Change or otherwise. For Small Changes you will demand high accuracy estimates and you will provide a high-performance environment in which to progress the change.

These are two explicit Engagement Commitments specific to the Small Change Process which are owned by the project sponsor who demands the change and the project manager who delivers the change. It will be noted that the stipulation high-performance environments also includes swift, easy-to-use, fit for purpose communications mechanisms to allow a rapid decision process which will authorise or reject a Small Change and communicate the decision back to a project sponsor.

The governance process needs to be assisting and driving not interrupting or delaying the process of project delivery. We often see governance processes that have to play catch up with fast-paced projects, especially Small Changes, spectacularly failing to provide them with a timely decision mechanism and holding them back as they are halted counter-productively and wait long-sufferingly for important decisions about personnel or resources etc. This is not the governance you need. Let us look at how we deliver Small Changes inside the Toolkit.

Buffer



 Types of Change     Types of Change   Small Change Request    Small Change Request



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
Small Change Process






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 214  Page: 221/444  Progress: 49.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.