Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Delivery Planning Workshop  Delivery Planning Workshop   What are facilitated workshops   What are facilitated workshops

It is of profound importance to understand one very basic point. Your solution needs to run somewhere and someone is responsible for running it. Methodologies have uniquely and blunderingly failed to give proper focus to operations and deployment management within the project lifecycle and such inattentive failure to DevOps responsibilities is a big mistake.

A timely workable solution relies upon the merged and unified collaboration of the operations and development teams. These are not just words though; they are deeds also and involve a significant push from the project team to make absolutely certain that the operations staff are aware of the products you intend to prepare and deploy, what operational testing you will perform, what features of the solution need establishing at first start up and throughout its operation, how often you will perform deployments, when and how these will take place as well as an understanding of responsibilities you expect from your operations personnel.

The Toolkit has the solution to this in the Release Planning Workshop. The workshop is the place where we will debate, describe and uncover the development and operations issues central to coordinating reliable and successful shipments and deployments.

The Release Planning Workshop is conducted in the Survey phase of the SETUP stage. At this point you know the change you are targeting, the scope of the work to address, the strategy you wish to progress and the proposed benefits the project is about to deliver. Furthermore, you know the requirements uncovered during your user requirements workshop where you also uncovered and created a Prioritised Story Board. So you have a development sequence.

Also you know the delivery sequence, when you start the development and when you will end it. Importantly, you also know which parts of the solution are going to be ready first and which significant pieces of usable functionality are going to be prepared for release in what sequence across the delivery.

Using this information you can broadly determine which of the parcels of functionality will appear at the same time and which are candidates to be bundled together and that can be released together onto a new environment to be deployed onto a live environment. To achieve this appropriately you will assess and answer some very different questions. You will determine if the items can in fact be combined, are they intended for the same version or type of platform, are they reliant upon other installations or deployments and can they be put in a combined dependable deployment state that will work.

In this context we are using the term release to mean the release or separation of a parcel of functionality from an environment onto a different environment. We often use the term checking in or checking out when used to define code releases. The environments are used to assess the functionality to ensure it is ready and appropriate for deployment. When we elect to implement the functionality onto the live environment, we are said to deploy.

Therefore, we release development functionality for assessment and deploy shipments into emerging solutions.

It will be said that this is an area of project development which has changed over recent years as the progress of agile development has widened. During agile development a project team will deploy more frequently and therefore generate more deployment events. That, in turn, generates more deployment effort and extra release management. This wave of work spawns further work for the Operations personnel, who will accept the deployments, confirm and install and sequence them inside the normal job runs and service processes.

To minimise the effort involved in these tasks and to flatten the demand peaks for personnel we make sure that the deployment and operations personnel are aware of the planned deployment by attending and taking a practical and influential part in the Release Planning Workshop. Within the workshop we will deliver the Release Plan which will document the expected delivery of functionality to the live environment at specific points in the project.

These will involve individual movement events from one environment to another and our best review of the planned timing of these events is provided. The Release Plan will record the individual movement events when they occur and document the planned and actual transfer of deployable shipments to the live environment.

These are important workshops and we will address the approach to facilitated workshops.


 Delivery Planning Workshop     Delivery Planning Workshop   What are facilitated workshops    What are facilitated workshops

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
Release Planning Workshop


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 381  Page: 334/444  Progress: 75.2%
 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 ( 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.