Journey to the Cloud

Any action takes resources and resource spend should be justified. Let’s list the most obvious reasons to take action and start your own Cloud journey.

  • Increase speed and agility
  • Leverage massive economies of scale
  • Stop guessing capacity
  • Trade capital expense for variable expense
  • Go global in minutes
  • Remove direct dependency of physical Data centers

It is obvious that every Cloud journey is different, it mainly depends on your existing IT footprint and ambitions. This article is more relevant for larger organisations, where introducing changes needs careful planning and coordinated effort.

Cloud adoption is not only about technology. There are many other aspects to think about. Main perspectives of Cloud Adoption Framework:

I will try to drill down into each of those to give some food for thought:

Business perspective: Budget and Cost Management (TCO, ROI), IT strategy, Supplier Management, Risk Management, Benefit Management, Governance.

Process perspective: Portfolio Management, Service Delivery Management, Program and Project Management, Continuous Integrations/Continuous Delivery, Process Automation, Quality Management.

Maturity perspective: Cloud Readiness Assessment, Cloud Maturity Heat-map Assessment, Target Platform Capabilities, Application Portfolio Analysis, Road-map sequencing, IT Management Assessment.

People perspective: Organizational Structures, Roles and Job Descriptions, Skills and Competencies, Training Certification Readiness, Manage Staffing, Organizational Change Management.

Platform perspective: Conceptual Architecture, Logical Architecture, Implementation Architecture, Application Migration Patterns, Cloud design principles and patterns, Continuous Service Improvement.

Operations perspective: Cloud Service Management, SLA/OLA Strategy, Business Continuity Planning, Incident & Problem Management, Change and Configuration Management, Performance & Operational Health.

Security perspective: Security Strategy, Reference Security Architectures, Governance Risk and Compliance, Lifecycle Security Capabilities, Security Operations Playbooks, DevSecOps.


  • Apply only what is relevant for your organization.
  • Find ways to attract supporters. Identify and work on a use case(s) that would make business team(s) really happy. Examples: improved speed of setting Test/Dev environments; cloud storage for remote backups.
  • Accelerate adoption with external help.

Leave a Reply