Want to make your iterative delivery pipeline execution a resounding success? Here’s what you need to know!

This article is part of the limited preview of the “The Missing Cloud Programme Roadmap”, a generic roadmap for any enterprise cloud adoption programme.

1. Executive Summary
2. The Cloud and Enterprises
3. The Missing Cloud Programme Roadmap
   1. The Cloud Programme Roadmap
   2. The First Iteration of The Cloud Programme Roadmap
   3. The Unavoidable Disclaimer
   4. The Roadmap for The Missing Cloud Programme Roadmap
   5. The Manual for the Missing Manual
   6. Building the Business Case
   7. Starting the Cloud Programme
   8. Iteratively Building the Delivery Pipeline
   9. Iteratively Executing the Delivery Pipeline
      1. Key Achievements
      2. Preparing the Iterations
      3. Delivering Minimum Cloud Products
      4. Recording Outcomes: The Cloud Runbooks and the Cloud Reflections
4. A Cloudy Future

Key Achievements

This phase focusses on executing the prioritised delivery pipeline of patterns and cloud compagnon applications migrating to the cloud, as defined in the Cloud Handbook.

For this, corresponding cloud products outlined in the delivery pipeline are iteratively built out. Hence, the main objective is to

Iteratively define, build, test, and retire cloud products. With a realistic level of usability and automation.

Put another way, the ultimate goal of this phase is to rapidly iterate cloud products to a mature state. This is achieved by unlocking cheap learning through controlled and bounded mistakes in real-life experiments disguised as incremental deliverables.

Things can and will go wrong. Chances are, the first cloud products are everything but what they should be. When it comes to continuous improvements, it’s the handling of failed experiments that makes all the difference.

Exiting and retiring all previous cloud product iterations after completing a new one avoids the burden of having to support past experiments; regardless of whether they succeeded or failed. The cloud programme has limited resources. Using them wisely is key.

However, this exit strategy not only applies to cloud products. The migration to the cloud will at some point also free up assets. In order to ensure compliant technology governance and also secure the rewards of the cloud programme

Exit any assets no longer required due to the move to the cloud and decommission them as soon as possible.

The execution of the delivery pipeline is a visible signal that the adoption of cloud is nearing. Numerous work streams have already delivered or are delivering dependent solutions. The cloud programme itself is also going to introduce additional changes in this phase with the arrival of its cloud products.

As the organisation might be entering one of the busiest transformation times, it’s more vital than ever to

Control the rate of transformation and keep it at a sustainable level using key metrics.

As in previous phases, the programme otherwise runs the risk of loosing control and becoming ineffective to the point of de facto collapsing under the forces it unleashed.

Preparing the Iterations

Find out more about it in the next article.

So, What Are Your Key Achievements?!

While the above Worx for Me!™ when it comes to defining the key achievements for the phase executing the delivery pipeline, you may have an alternative or better way.

Think this is all rubbish, massively overrated, or generally heading into the absolutely wrong direction?! Feel free to reach out to me on LinkedIn and teach me something new!

As always, prove me wrong and I’ll buy you a pint!