Want to make the start of your cloud programme 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
      1. Key Achievements
      2. Setting up the Cloud Programme
      3. Attracting the Right Mind- and Skill Sets
      4. Putting People First
      5. Determining the Build-Out Principles for Cloud
      6. Getting Into the Details
      7. Recording Outcomes: The Cloud Guidebook
   8. Iteratively Building the Delivery Pipeline
   9. Iteratively Executing the Delivery Pipeline
4. A Cloudy Future

Key Achievements

This phase mainly focusses on realistically preparing the organisation for a strenuous and prolonged transformation programme, in the shape of a cloud programme, while simultaneously setting it up for success as much as possible.

Using the business case defined in the Cloud Manifesto,

The first step is to secure sponsorship and sufficient funding for the cloud programme so that it can eventually be started.

With a programme of this magnitude and far reaching impact, it is more vital that ever to keep managing expectations and risks as well as the cloud programme honest; for the latter, installing appropriate governance as early as possible is essential.

The organisation will most likely need external help in implementing the cloud programme. As such, the next step is then to develop a strategy which puts people first and leaves no one behind in order to

Attract supporters with the right mind- and skill set. But also prepare the existing workforce for the journey to the cloud.

The chances of success can then be further increased by minimising the known residual risks to the cloud programme. After selecting CSPs, this phase also serves to

Identify obvious, hidden, and unknown dependencies by performing a methodical assessment of services that can be extended to or leveraged from the cloud. And then subsequently start initiatives aimed at resolving those dependencies.

Additionally, this phase also serves to unambiguously clarify the rules driving the build-out of the cloud in subsequent phases.

Setting up the Cloud Programme

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 starting the cloud 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!