Capture the setup of your cloud programme for success. In the Cloud Guidebook. The sponsoring. The staffing. The dependency resolutions. 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
- Iteratively Executing the Delivery Pipeline
- A Cloudy Future
Recording Outcomes: The Cloud Guidebook
The main objective of this phase was to start, staff, and secure success of the cloud programme. Well, or at least significantly increase the chances thereof.
By now, the cloud programme should be well sponsored, funded, and staffed while having identified and kicked off the resolution of dependencies.
As described above, all definitions, frameworks, assessments, metrics, data points, decisions, and rationales leading to outcomes in this phase need to be captured in the “Cloud Guidebook”.
The Cloud Guidebook consists of two parts and provides the reasons as well as the course for all future activities in the context of The Missing Cloud Programme Roadmap. At minimum, it needs to contain
- The details around the cloud programme not already defined in the Cloud Manifesto, namely
- The strategies and patterns developed in this phase, including
- the people strategy providing training and experimentation for everyone
- the build-out strategy, clarifying the organisation’s position on multi-region and multi-CSP strategy, bridging CSP gaps, and buying vs. building
- the assessment and selection of strategic CSP partners
- a detailed analysis of dependencies, including the start of initiatives to resolve them, in
The Cloud Guidebook is again to be published in print and distributed to all members of the programme — this step is pivotal. Not only does it impose a publication deadline on the programme but it also creates a solid point in time snapshot of the entire state of the programme.
Spending real money for publishing the document also increases its significance and importance. Let alone create a common understanding across the entire programme, document progress, as well as provide a physical part of the audit trail.
Iteratively Building the Delivery Pipeline
Find out more about it in the next article.
So, How Do You Record Outcomes?!
While the above Worx for Me!™ when it comes to recording the outcomes of 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!
Subscribe to How Hard Can It Be?!
Get the latest posts by following our LinkedIn page