Looking for a systematic, comprehensive, incremental, and data driven roadmap for your journey to the cloud?! Then here’s your answer!
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
- Iteratively Executing the Delivery Pipeline
- A Cloudy Future
The Missing Cloud Programme Roadmap
In the past decade, numerous enterprise organisations in highly regulated industries, such as Financial Services, have been trying to solve the problem of adopting the cloud.
While there are stories of companies successfully leveraging the cloud, these firms are still a minority or limiting the application of cloud to specific use cases.
Most enterprises use a structured approach to investigating and subsequently adopting the cloud, usually in the form of a dedicated cloud programme with a systematic roadmap.
It incorporates the collective knowledge and the lessons learned first hand by the author in several cloud adoption programmes in a highly regulated industry. Moreover, it serves as a spark that hopefully ignites further industry-wide collaboration.
The Missing Cloud Programme Roadmap follows a scientific approach, actively looking for disconfirming evidence, and keeping all outcomes open. This especially includes a cloud-negative outcome!
The Missing Cloud Programme Roadmap consists of four consecutive phases with milestones and key deliverables. These phases incrementally build the necessary foundations and capabilities but also prepare the organisation for the iterative delivery of the cloud programme. The iterative nature of the roadmap strongly encourages resetting certain sections or even the whole programme. Taking along all lessons learned.
In each phase, controlling the rate of change as well as the run-rate of the programme using hard data is essential. Otherwise, the programme runs the risk of loosing control and becoming ineffective to the point of de facto collapsing under the forces it unleashed.
The Cloud Programme Roadmap
Find out more about it in the next article.
So, How Do You Adopt the Cloud?!
While the above Worx for Me!™ when it comes to designing, planning, and executing a generic roadmap for any enterprise cloud adoption programme, 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