Looking for candidate applications that should successfully adopt the cloud? Use “Cloud Compagnon Applications” and significantly increase the odds!

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
      1. Key Achievements
      2. Constantly Monitoring Dependencies
      3. Prioritising Cloud Capabilities By Applications
      4. Iteratively Identifying Patterns to Move
      5. Selecting Cloud Compagnon Applications
      6. Setting Up the Teams
      7. Avoiding Friction for Existing Processes
      8. Recording Outcomes: The Cloud Handbook
   9. Iteratively Executing the Delivery Pipeline
4. A Cloudy Future

Selecting Cloud Compagnon Applications

The categorisation of applications in the previous section now makes the selection of suitable “candidate applications” that should successfully adopt the cloud significantly easier. This in return improves the chances of success for the entire cloud programme.

Given the crucial nature of these applications, let’s refer to them as “cloud compagnon applications”. Here, the French spelling for “companion” in the meaning of “lifelong partner” is deliberately chosen in order to emphasise the fellowship and mutual dependency between applications and cloud platform.

An initial selection of cloud compagnon applications (remember, it’s iterative) could be

1. A very limited number of existing applications identified as “Fit for Cloud” by the above assessment. Applications from the “Requires Limited Changes” tier should be treated with caution as required changes may turn out to have unexpected, deep, or complex dependency chains; not all of them may be technical.
2. Greenfield applications that fall into the “Fit for Cloud” category. Not only do they provide a great management success declaration (read: redundancy survival) opportunity. But more importantly, they are also a great showcase for the novel powers of the cloud as a whole. Especially, when chosen from one or more of the following backgrounds
   • Internet facing and able to leverage the extraordinary compute, storage, or bandwidth capabilities offered by the cloud
   • Conceptually rich but dependency shallow applications that unlock subsequent high priority patterns
   • Leveraging groundbreaking technologies unlocked by the cloud and currently not available on any other corporate platform

When choosing cloud compagnon applications, bare in mind that they possess the power to determine the fate of the cloud programme to a large degree. Both ways (we’ve personally witnessed this several times). Take your time. Choose wisely. Iterate. Reset. Cancel.

Regardless of the choice of eventual cloud compagnon applications, it’s essential to ensure that the organisation as a whole is able to support and sustain the rate of change initiated. Use metrics. Make it data driven.

Setting Up the Teams

Find out more about it in the next article.

So, How Do You Select Applications?!

While the above Worx for Me!™ when it comes to selecting cloud compagnon applications, 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!