Dependencies are one of the Achilles’ heels of your cloud programme. Constantly monitor them. Here’s how. And what to watch out for.

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

Constantly Monitoring Dependencies

Essential services, processes, and teams that the cloud programme depends upon have already been clearly identified and recorded in the Cloud Guidebook.

Remediating actions, such as initiatives aimed at removing any potential dependency roadblocks, have also been started in the previous phase. They should be tied into the longevity of the cloud programme and suitably funded as well as staffed to deliver the required changes.

Constantly monitoring the progress of these initiatives as well the dependencies themselves is vital to ensure the timely and economic removal of any known or potential new roadblocks. Especially before any future build-out phases where the costs for remediating dependencies are bound to drastically increase. Ideally, by now

Dependency resolving initiatives already provide meaningful solutions that can be consumed from or extended to the cloud. And prioritised roadmaps of when crucial features become available.

This allows to plan accordingly, provide sufficient lead times, and ensure a certain maturity of the solutions before the start of the next phase.

Prioritising Cloud Capabilities By Applications

Find out more about it in the next article.

So, How Do You Monitor Dependencies?!

While the above Worx for Me!™ when it comes to constantly monitoring dependencies, 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!