The cloud programme is started. Now, iteratively build your delivery pipeline of apps, tooling, and teams leveraging as well as building the cloud. Here’s 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.
- Executive Summary
- The Cloud and Enterprises
- The Missing Cloud Programme Roadmap
- The Cloud Programme Roadmap
- The First Iteration of The Cloud Programme Roadmap
- The Unavoidable Disclaimer
- The Roadmap for The Missing Cloud Programme Roadmap
- The Manual for the Missing Manual
- Building the Business Case
- Starting the Cloud Programme
- Iteratively Building the Delivery Pipeline
- Key Achievements
- Constantly Monitoring Dependencies
- Prioritising Cloud Capabilities By Applications
- Iteratively Identifying Patterns to Move
- Selecting Cloud Compagnon Applications
- Setting Up the Teams
- Avoiding Friction for Existing Processes
- Recording Outcomes: The Cloud Handbook
- Iteratively Executing the Delivery Pipeline
- A Cloudy Future
Iteratively Building the Delivery Pipeline
With the cloud programme started, the road ahead is now clear to iteratively build the delivery pipeline. It consists of suitable applications, tooling, and teams leveraging as well as building the cloud and is based on the outcomes documented in the Cloud Guidebook.
Constantly monitoring dependencies ensures that they are not only detected and resolved before they can become potential roadblocks. But also provide meaningful solutions as well as roadmaps of when prioritised items become available.
Future applications leveraging the cloud are then used to drive the build-out of cloud capabilities. Iteratively identifying patterns to move thus accelerates the overall cloud adoption by leveraging synergies in the cloud capabilities to provision.
The identification of commonalities and required cloud capabilities for applications is accelerated by assessing their “cloud suitability”. Applications are then categorised into different tiers according to their cloud suitability.
“Cloud Compagnon Applications” are then selected as suitable candidate applications that should successfully adopt the cloud, with newly constructed cross-functional incubator teams ultimately delivering them. Removing frictions for existing processes before the start of the next phase further increases the chances of success.
Assessing the alignment of the delivery pipeline with the objectives of the cloud programme allows to adjust either one of them. Carefully controlling and adjusting the run-rate, using the data generated so far, allows the cloud programme to ramp up efforts to a sustainable level.
The Cloud Handbook then captures all definitions, frameworks, assessments, metrics, data points, decisions, and rationales used for the iterative creation of the delivery pipeline and the corresponding delivery teams. This again provides the reasons as well as the course for all future activities.
Find out more about it in the next article.
So, How Do You Build the Delivery Pipeline?!
While the above Worx for Me!™ when it comes to 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!
Subscribe to How Hard Can It Be?!
Get the latest posts by following our LinkedIn page