Want to make your iterative delivery pipeline creation 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
      1. Key Achievements
      2. Constantly Monitoring Dependencies
      3. Prioritising Cloud Capabilities By Applications
      4. Iteratively Identifying Patterns to Move
      5. Selecting Cloud Compagnon Applications
      6. Setting Up the Teams
      7. Avoiding Friction for Existing Processes
      8. Recording Outcomes: The Cloud Handbook
   9. Iteratively Executing the Delivery Pipeline
4. A Cloudy Future

Key Achievements

This phase focusses on three key areas. Building on the outcomes documented in the Cloud Guidebook, the main objective is to

Build a pipeline of suitable applications, tooling, and teams leveraging as well as building the cloud.

While all parts of this roadmap should always be regarded as being iterative, this is especially true for the current phase.

Chances are that it will take several iterations before a half-way suitable pipeline has been assembled. Don’t be afraid to iterate. Reset. Or Cancel. Incorporate the lessons learned in the next iterations. Learn cheap. Iterate. Reset. Cancel.

Most items in the delivery pipeline will have dependencies on other services or processes. Hence, a key objective of this phase is to

Avoid unpleasant surprises in the next phase focussed on iteratively executing the delivery pipeline.

The resolution of problems identified in this phase will be much easier and more economical than during the next phase. As such, this phase starts where the last one left off. By reinforcing the constant monitoring of dependencies it focusses on identifying and resolving potential roadblocks as early as possible.

With all the activities generated and all the sub-programmes or sub-projects spun off by the cloud programme up to this point in time, a key objective — now more essential than ever — is to

Control the speed of change and slowly ramp up activities to a sustainable level with the help of key metrics.

Otherwise, the programme runs the risk of loosing control and becoming ineffective to the point of de facto collapsing under the forces it unleashed.

Constantly Monitoring Dependencies

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 iteratively building 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!