The delivery pipeline is built. Now, iteratively deliver your cloud products. Build what matters with Minimum cloud Products. Find out how.

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
         1. Defining Minimum Cloud Products
            1. Minimum Viable Products and Dependency Chains
            2. Minimum Cloud Products
         2. Building and Using McPs
         3. Reviewing, Repeating, and Retiring McPs
      4. Recording Outcomes: The Cloud Runbooks and the Cloud Reflections
4. A Cloudy Future

Iteratively Executing the Delivery Pipeline

With the delivery pipeline setting the direction and the Cloud Handbook providing the necessary details as well as rationales, the final phase focusses on iteratively executing the delivery pipeline.

Each iteration is small, time-bound, and incremental in complexity. However, some iterations are more about enablement for subsequent iterations than provisioning capabilities for the current patterns and cloud compagnon applications in the delivery pipeline.

Cloud products are delivered as Minimum cloud Products (in short: McP). McPs allow to keep the customer focussed lean approach towards features of an MVP while aligning it with broader objectives and combining them with the corporate reality of complex dependency chains.

A bottom-up build-out approach for McPs then allows to first provision basic shared cloud capabilities before delivering McP specific features on top of that. Stress testing delivered McPs provides the hard data required for reviewing an iteration, especially when preparing the next one.

Exiting and retiring all previous McP iterations after completing a new one avoids the burden of having to maintain past experiments. This iterative and incremental build-out process is then repeated until the outcome is satisfactory.

For each McP and iteration, all updates to processes or activities related to the support of the McP are then captured in the corresponding Cloud Runbook. All definitions, frameworks, assessments, metrics, data points, decisions, and rationales used are captured in the corresponding Cloud Reflections.

Key Achievements

Find out more about it in the next article.

So, How Do You Execute the Delivery Pipeline?!

While the above Worx for Me!™ when it comes to iteratively 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!