Download to read offline
Uploaded byRadu Vunvulea
Everything you need to know about cloud migration(Build Stuff 2021)
The document provides a comprehensive overview of cloud migration, highlighting its challenges, strategies, and the importance of proper planning and stakeholder involvement. An emphasis is placed on the Microsoft Cloud Adoption Framework for Azure, outlining steps for successful migration, including defining strategy, aligning business goals, and utilizing specific migration tools. Additionally, it addresses the common pitfalls that lead to failed migrations and the various approaches for migrating applications to the cloud.
More Related Content
Similar to Everything you need to know about cloud migration(Build Stuff 2021)
![Digital Transformation in the Cloud: What They Don’t Always Tell You [2020]](https://cdn.slidesharecdn.com/ss_thumbnails/tudy-digitaltransformationinthecloud-200710105339-thumbnail.jpg?width=640&height=640&fit=bounds)
Everything you need to know about cloud migration(Build Stuff 2021)
- 1. @RADUVUNVULEA Everything you needto know about cloud migration
- 2. 200% ADDITIONAL COST Stakeholders frightened offinal cost 36M FROM 9M PROGRAM Lack of basic business features X1.5 OPERATIONAL COST A part of subsystem still running on-premises Line of business applications used to manage and keep tracking of goods inside a warehouse. Web interfaces used by different suppliers to order and check the current stock. Integrated with 3rd party solutions for optimization and cost tracking. In total there are 3 warehouses within a radius of 10 kilometres, where 800 employees are working 24/7, delivering 20.000 goods per day. WAREHOUSE MANAGEMENT SYSTEM
- 3. Radu Vunvulea Endava Microsoft RegionalDirector Microsoft Azure MPV 2010: 1st cloud commercial cloud project
- 4. COST OPTIMIZATION ISTHE PRIMARY REASON FOR 47% OF ENTERPRISES’ CLOUD MIGRATION 90% OF COMPANIES ARE ON THE CLOUD https://hostingtribunal.com/blog/cloud -computing-statistics/
- 5. Enterprises embrace multi-cloud Publiccloud adoption CONTINUES TO ACCELERATE Public cloud adoption is evolving Use of public cloud PaaS services is rising Organizations STRUGGLE to get a handle on growing cloud spend https://www.flexera.com/blog/industry -trends/trend-of-cloud-computing-2020/
- 6. 6 Agenda 1. WHY DOESA CLOUD MIGRATION FAILS 2. AZURE CLOUD ADOPTION FRAMEWORK OVERVIEW 3. MIGRATION TOOLS AND TEMPLATES 4. MIGRATION STRATEGIES
- 7. HOW A CLOUDMIGRATION CAN FAIL Time, Budget, Scope, SLA, Quality Metrics, Skills, KPIS
- 8. 8 Running in thesame way as you would run them on-premises Cloud is build in such a way to use resources only when you need them On-premises are build with no orchestration or autonomy ability Public cloud is metered and you pay for each for bit of it Failure to adapt to the cloud 3 of 4 apps migrated to cloud, moved back to on-premises after failing to achieve the anticipated benefits H T T P S : / / W W W . F O R T I N E T . C O M / C O N T E N T / D A M / F O R T I N E T / A S S E T S / A N A L Y S T - R E P O R T S / A R - 2 0 1 9 - I H S M - F O R T I N E T - W P - Q 2 . P D F
- 9. 9 Projects are drivenby IT departments Key people invited to late No business KPIs and full business commitment Not bringing in the business stakeholders 3 of 4 apps migrated to cloud, moved back to on-premises after failing to achieve the anticipated benefits H T T P S : / / W W W . F O R T I N E T . C O M / C O N T E N T / D A M / F O R T I N E T / A S S E T S / A N A L Y S T - R E P O R T S / A R - 2 0 1 9 - I H S M - F O R T I N E T - W P - Q 2 . P D F
- 10. 10 Manage cloud inthe same way as you would manage on-premises solutions Lack of procedures in the case of a failure No tracking and logging capabilities No optimization and cloud economics procedures No Cloud Operating Model 3 of 4 apps migrated to cloud, moved back to on-premises after failing to achieve the anticipated benefits H T T P S : / / W W W . F O R T I N E T . C O M / C O N T E N T / D A M / F O R T I N E T / A S S E T S / A N A L Y S T - R E P O R T S / A R - 2 0 1 9 - I H S M - F O R T I N E T - W P - Q 2 . P D F
- 11. 11 LACK OF PLANNING Migrationare started without a well- researched and clear definition. They lack of a strategy from day 0 The migration approach is crucial for success. Even so, organizations don’t spend enough time to identify what solution works best for their specific applications Lack of testing in each stage of the migration journey hide issues that could be spotted earliest in the process. WRONG MIGRATION APPROACH NO TESTING GOVERNANCE Starting from selecting the wrong cloud provider to ignoring access management and compliancy requirements. No strategy related to integration with existing systems and gaps of skills required to ensure success of such integrations Deciding to use a specific cloud vendor or partner without considering business expectations and technical capabilities INTEGRATION VENDOR SELECTING
- 12. LANDING ZONES Metropolis • Usingan analogy, this is similar to how city utilities such as water, gas, and electricity are accessible before new houses are constructed. In this context, the network, IAM, policies, management, and monitoring are shared 'utility' services that must be readily available to help streamline the application migration process. Landing Zone • The principle purpose of the “Landing Zone” is to ensure that when a workload lands on Azure, the required “plumbing” is already in place, providing greater agility and compliance with enterprise security and governance requirements
- 13. Test-driven development (TDD) Asimple agreement between the cloud platform team and other affected teams. It will outline expected value- added features and will become increasingly complex as additional workloads and cloud features are adopted.
- 14. WHY DO ENTERPRISESNEED CLOUD ADOPTION Cost Avoidance Staff Productivity Customer Experience Faster time to market Build a NEW REVENUE STREAM
- 15. WHAT DOES CLOUDMIGRATION MEAN? CREATE new business value Enhance WITH modern features and capabilities
- 16. HOW WE DOA CLOD MIGRATION? Microsoft Cloud Adoption Framework for Azure
- 17. HOW WE DOA CLOUD MIGRATION? Microsoft Cloud Adoption Framework for Azure DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUD ADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE
- 18. HOW WE DOA CLOUD MIGRATION? Microsoft Cloud Adoption Framework for Azure DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUD ADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE ALIGN STAKEHOLDERS ALIGN PARTNER SUPPORT BUSINESS JUSTIFICATION BUSINESS KPIS DOCUMENT STRATEGY TOOLS CLOUD JOURNEY TRACKER BUSINESS OUTCOME TEMPLATE
- 19. HOW WE DOA CLOUD MIGRATION? Microsoft Cloud Adoption Framework for Azure DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUD ADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE GATHER DATA AND ANALYZE ASSETS AND WORKLOADS MAKE A BUSINESS CASE CREATE MIGRATION PLAN ASSESS DIGITAL ESTATE TOOLS AZURE DEVOPS DEMO GENERATOR CLOUD ADOPTION PLAN TEMPLATE
- 20. HOW WE DOA CLOUD MIGRATION? Microsoft Cloud Adoption Framework for Azure DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUD ADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE BUILD SKILLS READINESS PLAN DEPLOY AN ALIGNED LANDING ZONE EXPAND LANDING ZONE SHARE PLANS WITH PEOPLE REVIEW ORGANIZATION PROCESSES TOOLS AZURE SETUP GUIDE READINESS CHECKLIST NAMING AND TAGGING TRACKING TEMPLATE LANDING ZONE BLUEPRINTS
- 21. HOW WE DOA CLOUD MIGRATION? Microsoft Cloud Adoption Framework for Azure DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUD ADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE MIGRATE WORKLOADS REVIEW LANDING ZONE IMPLEMENT DESIRED CHANGES ACROSS IT IMPLEMENT DESIRED CHANGES ACROSS PROCESSES TRAIN PEOPLE TOOLS STRATEGIC MIGRATION ASSESSMENT AND READINESS TOOL (SMART) AZURE MIGRATION GUIDE
- 22. HOW WE DOA CLOUD MIGRATION? Microsoft Cloud Adoption Framework for Azure DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUD ADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE DESIGN AND ENFORCE ACCESS CONTROL REVIEW AND IMLEMENT COMPLIANCE REQUIRMENTS DEPLOY INITIAL GOVERNANCE FOUNDATION HAND-OFF PRODUCTION WORKLOADS TO CLOUD GOVERNANCE TOOLS GOVERNANCE BENCHMARK GOVERNANCE PROCESS TEMPLATE COST MANAGEMENT PROCESS TEMPLATE DEPLOYMENT ACCELERATION PROCESS TEMPLATE IDENTITY PROCESS TEMPLATE RESOURCE CONSISTENCY PROCESS TEMPLATE SECURITY BASELINE PROCESS TEMPLATE
- 23. HOW WE DOA CLOUD MIGRATION? Microsoft Cloud Adoption Framework for Azure DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUD ADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE HAND-OFF PRODUCTION WORKLOADS TO CLOUD OPERATIONS IMPLEMENT AN OPERATIONS BASELINE OPTIMIZE RESOURCE TIER AND CONSUMTION TOOLS MICROSOFT AZURE WELL- ARCHITECTED REVIEW BEST PRACTICES SOURCE CODE OPERATIONS MANAGEMENT WORKBOOK
- 24.
- 25. 25 Rehosting— Otherwise known as“lift- and-shift.” Replatforming— I sometimes call this “lift-tinker-and-shift.” Repurchasing— Moving to a different product. MIGRATION STRATEGY Refactoring / Re-architecting — Re- imagining how the application is architected and developed, typically using cloud-native features. Retire— Get rid of. Retain— Usually this means “revisit” or do nothing (for now). H T T P S : / / A W S . A M A Z O N . C O M / B L O G S / E N T E R P R I S E - S T R A T E G Y / 6 - S T R A T E G I E S - F O R - M I G R A T I N G - A P P L I C A T I O N S - T O - T H E - C L O U D /
- 26. 26 Rehosting— Otherwise known as“lift- and-shift.” Replatforming— I sometimes call this “lift-tinker-and-shift.” Repurchasing— Moving to a different product. MIGRATION STRATEGY Refactoring / Re-architecting — Re- imagining how the application is architected and developed, typically using cloud-native features. Retire— Get rid of. Retain— Usually this means “revisit” or do nothing (for now). H T T P S : / / A W S . A M A Z O N . C O M / B L O G S / E N T E R P R I S E - S T R A T E G Y / 6 - S T R A T E G I E S - F O R - M I G R A T I N G - A P P L I C A T I O N S - T O - T H E - C L O U D /
- 27. 27 When to usethem One important steps in the initial phase is to align the strategy with your business goal. For each application you might have different migration strategies. REHOSTING You need to move quickly to cloud. Migration complexity is low and repetitive (e.g. 5k users, 12 apps). You don’t want to do any cleaning before the migration. REPLATFORMING You want to upgrade the application from existing platform to something new. The core application remain the same and you just utilize the cloud infrastructure. Good fit for non-critical application that are business oriented. REPURCHASING You move to a SaaS, that it is fully maintained by a 3rd party. You have zero costs on maintenance and updates. In most of the cases the pricing model will change to a subscription based. REFACTORING You end up with this approach when there is now other way to achieve your business goals. You need fully or partially to use a cloud-native approach. Using this approach you improve agility, scalability, and performance. RETIRE You realize that the application it is not used anymore. The system is part of your IT portfolio, but there is no business justification to keep the application. By deciding to retire the solution you simplify the workload that needs to be migrated, allowing the team to focus on more important parts. RETAIN You realize that there is no value to migrate the solution to cloud. You keep the system running on the current infrastructure and review the decision after a period of time.
- 29. Marketing Tool CRMAuxiliary Services ERP BI Tool ESB Service Accounting System ETL Service Data Warehouse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service
- 30. Marketing Tool CRMAuxiliary Services ERP BI Tool ESB Service Accounting System ETL Service Data Warehouse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 31. Marketing Tool CRMAuxiliary Services ERP BI Tool Azure Service Bus Accounting System ETL Service Data Warehouse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 32. Marketing Tool CRMAuxiliary Services ERP BI Tool Azure Service Bus Accounting System ETL Service Data Warehouse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 33. Marketing Tool CRMAuxiliary Services ERP BI Tool Azure Service Bus Accounting System ETL Service Azure Synapse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 34. Marketing Tool CRMAuxiliary Services ERP BI Tool Azure Service Bus Accounting System Data Factory Azure Synapse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 35. Marketing Tool CRMAuxiliary Services ERP PowerBI Azure Service Bus Accounting System Data Factory Azure Synapse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 36. Marketing Tool CRMAuxiliary Services ERP PowerBI Azure Service Bus Accounting System Data Factory Azure Synapse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 37. Marketing Tool CRMAuxiliary Services ERP PowerBI Azure Service Bus Accounting System Data Factory Azure Synapse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 38. Marketing Tool Dynamics365 Auxiliary Services Dynamics 365 PowerBI Azure Service Bus Accounting System Data Factory Azure Synapse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 39. Marketing Tool Dynamics365 Auxiliary Services Dynamics 365 PowerBI Azure Service Bus Accounting System Data Factory Azure Synapse Web Apps 1..n VoIP Service Email Server Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 40. Marketing Tool Dynamics365 Auxiliary Services Dynamics 365 PowerBI Azure Service Bus Accounting System Data Factory Azure Synapse Web Apps 1..n VoIP Service O365 Web App Payment Payment Processor Document Storage eSign Service Rehosting Replatforming Repurchasing Refactoring Retire Retain
- 42. 100% alignment on theAzure environment First workload First 10 workload First prod workloads First 100 workloads Common path – Common blocker Acting too soon
- 43. First workload First 10 workload First prod workloads First100 workloads Enterprise Readiness Common path – Common blocker Acting too late
- 44. Landing zone Connectedenvironments Secure landing zones Shared services model CCoE and operating model First workload First 10 workload First prod workloads First 100 workloads Cloud Adoption (Migrate or Innovate) Cloud Platform (Refactoring landing zones) Development approach
- 45. Landing zone Connected environments Secure landing zones Shared servicesmodel CCoE and operating model First workload First 10 workload First prod workloads First 100 workloads CLOUD GOVERNA NCE CLOUD OPERATIO NS REFACTOR TO ENTERPRISE READINESS DURING THIS PROCESS Cloud Adoption (Migrate or Innovate) LANDING ZONE CONSIDERA TIONS Cloud Platform (Refactoring landing zones) CLOUD SECURITY
- 46.
- 47. MIGRATION TOOLS ASSESS WORKLOADS AZUREMIGRATE – ASSESS, SIZE, COST ESTIMATION SERVICE MAP – DISCOVERY, COMMUNICATION MAP DEPLOY WORKLOADS AZURE MIGRATE – WORKLOAD MIGRATE, TRACK AZURE DATABASE MIGRATION SERVICE DATABASE MIGRATION ASSISTANT – DB UPGRADE AZURE APP SERVICE MIGRATIO ASSISTANT – WEB SITES SQL SERVER MIGRATION ASSITANT AZURE COSMOS DB DATA MIGRATION TOOL RELEASE WORKLOADS RESIZE SERVICE INSTANCES COST MANAGEMENT & BILLING ADVISOR RECOMNDATIONS DEPLOY WORKLOADS AZURE DEVOPS MICROSOFT PLANNER AND MICROSOFT PROJECT MICROSOFT TEAM DEPLOY WORKLOADS COST MANAGEMENT & BILLING ADVISOR RECOMNDATIONS COST CONTROL AZURE MIGRATE AZURE PRICING CALCULATOR AZURE TCO CALCULATOR AZURE COST MANAGEMENT + BILLING AZURE ADVISOR
- 48.
- 49. DEFINE STRATEGY DEFINE BUSINESS JUSTIFICATION AND EXPECTED OUTCOMES PLAN ALIGN ACTIONABLE CLOUDADOPTION PLAN TO BUSINESS OUTCOMES READY PREPARE PEOPLE, PROCESS AND ENVIRONMENT FOR CHANGE ADOPT MIGRATE OR INNOVATE IMPLEMENT DESIRED CHANGES ACROSS IT AND BUSINESS PROCESSES GOVERN COMPLY, CONTROL AND SECURE MANAGE OPERATE AND OPTIMIZE MICROSOFT CLOUD ADOPTION FRAMEWORK TOOLS TEMPLATES BEST PRACTICES SKILLS
- 50.
Editor's Notes
- #7 Agenda General Template Guidance: Information to help you make good presentations. Standard / Static Slides: Some key Endava slides/lockups that, in general, should only be modified by marketing. Template Slides: A selection of template slides for use in Endava presentations. Larger Format Template Slides: Template slides with larger content. Icon Library: A selection of hundreds of icons to use in Endava presentations.
- #9 Standard text slide (version 7) Creating contrast throughout the presentation can help to call attention to key ideas. They can also create visual “breaks” in the cadence of the presentation and allow the eye to rest on big ideas. The quotes should be important information, quotes, or Endava marketing messages.
- #10 Standard text slide (version 7) Creating contrast throughout the presentation can help to call attention to key ideas. They can also create visual “breaks” in the cadence of the presentation and allow the eye to rest on big ideas. The quotes should be important information, quotes, or Endava marketing messages.
- #11 Standard text slide (version 7) Creating contrast throughout the presentation can help to call attention to key ideas. They can also create visual “breaks” in the cadence of the presentation and allow the eye to rest on big ideas. The quotes should be important information, quotes, or Endava marketing messages.
- #12 Elements (version 4) Elements are used to give more detail to a set of ideas, they should all relate to the same topic. Use this page for a list of deliverables, key roles on a project, phases of a project, or any topic that can be broken down into more specific examples. Each section should have an icon that relates to the content of that specific element, no icon should be repeated on the same page, and they should all be the same colour. Use this version when there are less examples to breakdown with more text associated with the element.
- #14 Create a test: Define a test to validate that acceptance criteria for a specific value-add feature has been met. When possible automate the test. Test the landing zone: Run the new test and any existing tests. If the required feature hasn't already been met by prior development efforts and isn't inclusive to the cloud provider's offering, the test should fail. Running existing tests will help validate that your new test doesn't reduce reliability of landing zone features delivered by existing code. Expand and refactor the landing zone: Add or modify the source code to fulfill the requested value-add feature and improve the general quality of the code base. To meet the fullest spirit of test-driven development, the cloud platform team would only add code to meet the requested feature and nothing more. At the same time, code quality and maintenance is a shared effort. When fulfilling new feature requests, the cloud platform team should seek to improve the code by removing duplication and clarifying the code. Running tests between new code creation and refactoring of source code is highly suggested. Deploy the landing zone: Once the source code is capable of fulfilling the feature request, deploy the modified landing zone to the cloud provider in a controlled testing or sandbox environment. Test the landing zone: Retesting the landing zone should validate that the new code meets the acceptance criteria for the requested feature. Once all tests pass, the feature is considered complete and the acceptance criteria are considered to be met.
- #26 Concept slide (version 1) Concept slides create “breathing room” in presentations by having white space and focusing on a few key details. They are intended to represent important information, quotes, or Endava marketing messages to the audience.
- #27 Concept slide (version 1) Concept slides create “breathing room” in presentations by having white space and focusing on a few key details. They are intended to represent important information, quotes, or Endava marketing messages to the audience.
- #28 Standard text slide (version 9) Varying the length of the paragraphs as well as using bulleted and numeric lists help with keeping the reader engaged. Lists help to “skim” the information on the page and allow the audience to absorb a just the key information.
- #43 In the image above, the customer has an objective of 100 workloads living in the cloud. To get there, the customer will likely deploy their first workload. Then their first 10 or so workloads, before they are ready to release one of those workloads to production. Eventually, they will reach the objective of the adoption plan and have a robust portfolio in the cloud. However, the red X in the image shows where customers commonly get stuck. Waiting for 100% alignment can delay the first workload by weeks, months, or even years.
- #44 Similar to acting too soon, in this image, the customer waits too long to reach enterprise ready environment (enhanced requirements needed by security, operations, and governance teams) across landing zones. By waiting too long, the customer will be constrained on the amount of refactoring and expansion they can do in the environment. Those constraints will limit their ability to drive continued success.
- #45 In the example iteration paths above, the cloud adoption team is migrating their portfolio of 100 workloads to the cloud. In parallel, the cloud platform team is focused on staying ahead of the cloud adoption plan to ensure the environment is prepared for those workloads. This approach is designed to remove early blockers and create opportunities for the platform and adoption teams to learn and work together.