• Generally moving Analytical loads for Data Science activities that demand elasticity in the compute may be the initial use cases to be considered for Cloud movement as they come with tangible business benefits and relatively defined data movement

• The guideline here is don’t try to boil the whole ocean. Define the MLP with a hybrid of Cloud Foundation Layers and Use Casescope relating to the movement of associated relevant data, logic and workflow and expected functionality

• Plan to move only the meaningful portion to the cloud. Start with non-sensitive data upload to the cloud to have less initial resistance/ risk

• Lay out the foundation by delivering at least one fully functional cloud food chain covering data ingestion, data pipeline, security pattern, hosting pattern (Object Store of Big Data on Cloud) and associated cloud-native tooling for business outcome

4) Design for Business Outcome in DevOps/ Agile way

• Line up resources with can-do attitude and form a delivery POD with resources mix of the business domain, technology, operations, and Cloud SMEs.

• Use collaboration tools to plan the sprints, user journeys and expected outcomes with clear ownership and timelines

• Don’t try to deliver all in one go, use the iterative approach of delivery, review, and improvement in a product mentality form

• Transformations could be difficult, and in some cases, nerve-wracking and moving to could well be considered as a transformation from the legacy way of thinking. Key here is realizing the fact that expected outcome may not be evident in the first go.

5) Educate & Align Stakeholders

• Typical notion that comes with any cloud movement is that data and control of artifacts will move away in the hand of the third party. That’s where a robust communication must be made to stakeholders about the cloud benefits and security measures being undertaken. In some cases, very basics education of Cloud Tenancy and the associated potential value it can bring to an organization goes a long way.

• Alignment and syndication with Control/ Security group in a proactive manner is also a good strategy to avoid late surprises

• Making security/ control professional the allies and enablers in this journey by explaining each facet of the use case, potential benefit, sponsorship, and security control being designed to mitigate the risk reap in rich dividends

• Always ensure that such meetings are diligently noted with observation, next steps, the risk with their magnitude (High/ Medium/ Low). Avoid discussions and comments made on emotions and encourage people to give fact-based objections/ observations

• The general rule of thumb controls/ security groups critically review cloud proposals with the right intention to ensure companies asset (data/artifacts) from leaking/ hacking. To do so, they must share the magnitude of risk involved (material/ non-material). The go / no go decision generally rests jointly with the business owner and the CIO organization.

6) Assess Business Benefit & Socialize Success

• Do an objective assessment of business outcome following before and after state on laid out KPIs

• Socialize success with relevant sponsors, beneficiaries, and stakeholders at large to improve on the confidence quotient and future sponsorship of similar initiatives

Finally, to sum it up developing and delivering a seamless cloud-enabled business case requires taking your objectives into account, along with the current state of existing applications (application/ architecture), and their constraints. Engaged leadership, frequent communication, and clarity of purpose, along with aggressive but realistic goals and timelines with resources who believe in “Art of possible” make it easier for anentire organization to rally behind the decision to migrate.