|    |    |    |    |
| --- | --- | --- | --- |

  

  

[[_TOC_]]

### **Business Drivers**

The key is to identify the stakeholders that need to be part of the discussion to document the drivers. Typically, CxOs, senior managers, and key technology leaders within the organization. Business drivers should be linked to a metric that can be measured throughout the migration journey in order to validate whether the outcomes have been achieved. The company strategic goals and annual reports can act as a starting point. Focus the conversation on where the company wants to be, based on existent and projected metrics, as a result of moving to the cloud. Consider goals and business outcomes. Also, what success looks like as cloud adoption increases. Next, establish the importance level of each driver. What are the priorities? What are the expected benefits? How does the benefits support the business goals and outcomes? In the context of application portfolio assessment, this will help to assist workload prioritization for migration and to establish technical guiding principles. However, business drivers will define and impact the migration program as a whole.

### **Technical Guiding Principles**

These principles are key to inform migration strategy selection in portfolio assessment.  Guiding principles can be established as general technology- and approach-related decisions derived from business goals and outcomes. For example, if the primary goal is to reduce cost, and the desired outcome is to close an on-premises data center by a given date in the near future (e.g., 6 to 12 months), a resulting guiding principle would be to lift and shift all applications to the cloud by means of a rehost or relocate migration strategy whenever possible. In this case, the approach will accelerate migration outcomes and will permit to focus on the main business drivers to later optimize/modernize the migrated workloads once they have moved out the on-premises data center.  
To establish the technical guiding principles, start by analysing business drivers and identifying a list of technologies and techniques that will enable the business goals and outcomes. Next, refine the list and assign an order of relevance based on best suitability/preference to achieve a desired outcome.  
Document and socialize the guiding principles with the people involved in planning and performing the migration. Highlight concerns and potential conflicts between the principles and the actual implementation.

  

### **Sample of business drivers and technical guiding principles**

Update the table below based on actual drivers and guiding principles

| Goal | Outcome | Metric | Guiding Principle |
| --- | --- | --- | --- |
| _Innovation_ | _Improved competitiveness, increased business agility_ | _Number of deployments per day/month, new features release per quarter, customer satisfaction scores, number of experiments_ | _Refactor differentiating applications leveraging Microservices and the DevOps operating model to increase agility and speed to market of new features_ |
| _Operational Costs_ | _Supply and demand matched, elastic cost base (pay for what you use)_ | _Spend variation over time_ | _1-Rehost applications with infrastructure right-sizing._   _2-Retire applications with low/no utilization._ |
| _Operational Resiliency_ | _Improved uptime, reduced mean time to recovery_ | _SLA's, number of incidents_ | _1-Replatform applications to latest and best supported OS versions and implement high availability architectures for critical applications_ |
| _Data center exit_ | _Data center closure by a date within 6-12 months_ | _Speed of server migrations_ | _1-Rehost applications leveraging AWS Cloud Endure Migration Factory_   _2-Relocate (via VMware Cloud on AWS)._ |
| _Stay on premises, but increase agility and resiliency_ | _Improved competitiveness & uptime while remaining on-premise_ | _Number of deployments per day/month, new features release per quarter, SLA's, number of incidents_ | _1-Modernize systems by extending its functionality into the Cloud_   _2-Assess for Rehost or Replatform to AWS Outposts_ |

 **Attachments:** 


[image2021-3-9_13-41-33.png](/.attachments/DK-Portfolio/image2021-3-9_13-41-33.png)