Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 User Story Changes  User Story Changes   DELIVER Develop   DELIVER Develop

Lifecycle   »   DELIVER   »   DELIVER Introduction

The trigger for starting to develop is a signed off Setup Plan, a signed off Delivery Plan and a signed off Release Plan. So you start to develop knowing you have the right setup, you know what you plan to deliver and when you plan to deliver it. By this point, we have completed the SETUP stage and have confirmed our project is ready to develop, we know what benefits we are seeking to deliver and we know when we will deliver them too. Now before we get into detail let us go through a swift bit of terminology so we know precisely which parts of the delivery are going to be delivered and then we have no ambiguity or misunderstanding.

Our ultimate objective is to deliver. We deliver the final delivery. This is the final end point of the project. This will not be a surprise to you. However what may actually be a surprise is what we plan to deliver. We will deliver a deployed solution. However we will also deliver the benefits from the deployed solution.

In the Toolkit, a project delivers a final delivery and the final delivery is the combination of the deployed solution and the realised benefits from the deployed solution. Importantly, a project has not delivered fully until it has uncovered and presented (realised) the benefits promised from the deployed solution.

A project may say it has finished, concluded, ended or completed; it may have shut up shop, gone away, closed down, wrapped up, terminated, ceased, parked, halted or stopped or another related word. However, at this point until it has brought about and revealed the promised benefits, it has not delivered. The Toolkit operates just one success equation.

Successful Final Delivery = Deployed Solution + Realised Benefits

Now that is clear, let us look at the deployed solution. The deployed solution is made up of one or more shipments. The shipments are gradual evolving parts of the deployed solution. The shipments are driven by the Release Plan which is supported by the Delivery Plan. So you see how a solution is derived. We have a delivery date; this specifies when we need our delivery. We develop the delivery by gradually evolving developments.

These developments are released into assessment environments and these developments are termed: releases. Once releases are signed off they are termed deployable releases and these are combined to become shipments, which are deployed to become parts of the solution. These parts of the solution are developed, shipped and deployed in priority order and delivered early to deliver benefits early. More information about the release shipment process is in DELIVER: Release.

Developments > Releases > Shipments > Solution

 User Story Changes     User Story Changes   DELIVER Develop    DELIVER Develop

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
DELIVER Introduction


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 282  Page: 241/444  Progress: 54.3%
 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.