A Practical Guide to Cloud Migration

Table of contents

1. Foreword
2. Introduction
   1. Why We Wrote This Report
   2. What You Will Learn
   3. Who Should Read This Report
   4. Acknowledgments
3. 1. Managing a Successful Transformation
   1. Who
   2. Why
   3. How
      1. The Teams
      2. The executive team
      3. The platform consulting team
      4. The internal implementation teams
      5. The individual
   4. The Methods
      1. Leadership
      2. Monitoring Progress and Course Correction
      3. Learning, Training, and Continuing Education
      4. Time Management
   5. Pitfalls
      1. The Blame Game
      2. Unrealistic Project Tracking and Time Management
      3. Letting the External Teams Solve the Hard Problems
      4. We’re Successful, So Why Change Anything?
      5. The Bike Shed Effect
4. 2. Celebrating (and Tweaking) Your Culture
   1. Who
   2. Why
   3. How
   4. Pitfalls
      1. Top-Down Direction, Bottom-Up Crickets
      2. Teams Can Support Themselves
      3. Feelings? Meh.
5. 3. Defining “Good” for Your Organization
   1. Who
   2. Why
   3. How
      1. Defining the End Goal
      2. Creating an Action Plan
      3. Making Progress
      4. Defining Value
      5. Measuring Progress
   4. Pitfalls
      1. Failure to Recognize the Existential Threat
      2. I Have 99 Problems, and They Are All Squeaky
      3. Crisis-of-the-Day Thinking
      4. What a Cute Little Project
      5. Fiscal Flexibility at the Cost of Efficacy
6. 4. Framing Your Transformation with Clearly Articulated Policies
   1. Who
   2. Why
   3. How
   4. Pitfalls
      1. Forgetting that the Journey Is the Goal
      2. The Half-Hearted Transformation
      3. Building Without a Strong Business Foundation
      4. A Transformation in Letter, Not in Spirit
7. 5. Building Leadership Through Decider Groups
   1. Who
   2. Why
   3. How
   4. Pitfalls
      1. A Few Loud Voices Dominate
      2. Toxic Mindsets Limit Individual Empowerment
      3. Lack of Investment in Training
      4. Imbalanced or Imprecise Empowerment
      5. Lack of Leadership Visibility
8. 6. Developing Centers of Excellence
   1. Who
   2. Why
   3. How
   4. Pitfalls
      1. Lack of Effective Communication
      2. Process and People
      3. Misaligned Culture and Technology
      4. Bottlenecks in the CCoE
9. 7. Scaling Innovation
   1. Who
   2. Why
   3. How
      1. Standards and Processes
      2. Critical Roles
   4. Pitfalls
      1. Failure to Provide Autonomy
      2. Failure to Provide Broad Access
10. 8. Higher-Order Architectures for Multi-Cloud
    1. Who
    2. Why
    3. How
       1. Applications
       2. Data
       3. Infrastructure
       4. Security
    4. Pitfalls
       1. Interoperability Between Multiple Clouds
       2. Lack of a Common Management Plane
       3. Application and Data Portability Issues
       4. Poorly Implemented Security and Privacy
       5. Inconsistent Day 2 Operations
11. 9. Thinking of Cloud Platforms as a Software Problem
    1. Who
    2. Why
    3. How
       1. Prepare for Platform Modernization
       2. Make Decisions on Consistent Tooling
       3. Boundaries Defined by Software
       4. Let the Tools Do All the Heavy Lifting
       5. Keep Optimizing for Everything
    4. Pitfalls
       1. It Will “Cost” More if You Do It Right
       2. But We’ve Always Used This Tool!
       3. Software Engineering Is “Just Writing the Code”
12. 10. Making Security Policies Fit-for-Purpose
    1. Who
    2. Why
    3. How
       1. Principles
       2. Security Policies and Procedures
       3. Security Standards/Technical Implementation Guides
       4. Conclusion
    4. Pitfalls
       1. Moving at the Wrong Speed
       2. Internal Adversarial Behaviors
13. 11. 360-Degree Continuous Compliance
    1. Who
    2. Why
    3. How
    4. Pitfalls
       1. Doing Something Just Because the Cloud Makes It Possible
       2. Avoiding Teachable Moments
       3. Hasty Continuous Compliance Architecture
14. 12. Safely Operating at Scale
    1. Who
    2. Why
    3. How
    4. Pitfalls
       1. Require Reliability
       2. Blame
15. 13. Developers—Go Faster, Go Together
    1. Disruption Arrives: Let’s Move to Cloud!
    2. Some Benefits Appear Quickly
    3. More Benefits Accrue over the Long Term
    4. The Transformation Benefits the Organization and the Technology
16. Conclusion
17. Sample Code
    1. Sample Code