The essential roadmaps for enterprise cloud adoption
As cloud technologies continue to challenge the fundamental understanding of how businesses work, smart companies are moving quickly to adapt to a changing set of rules. Adopting the cloud requires a clear roadmap backed by use cases, grounded in practical real-world experience, to show the routes to successful adoption. The Cloud Adoption Playbook helps business and technology leaders in enterprise organizations sort through the options and make the best choices for accelerating cloud adoption and digital transformation.
Written by a team of IBM technical executives with a wealth of real-world client experience, this book cuts through the hype, answers your questions, and helps you tailor your cloud adoption and digital transformation journey to the needs of your organization. This book will help you:
- Discover how the cloud can fulfill major business needs
- Adopt a standardized Cloud Adoption Framework and understand the key dimensions of cloud adoption and digital transformation
- Learn how cloud adoption impacts culture, architecture, security, and more
- Understand the roles of governance, methodology, and how the cloud impacts key players in your organization.
Providing a collection of winning plays, championship advice, and real-world examples of successful adoption, this playbook is your ultimate resource for making the cloud work. There has never been a better time to adopt the cloud. Cloud solutions are more numerous and accessible than ever before, and evolving technology is making the cloud more reliable, more secure, and more necessary than ever before. Don’t let your organization be left behind! The Cloud Adoption Playbook gives you the essential guidance you need to make the smart choices that reduce your organizational risk and accelerate your cloud adoption and digital transformation.
Table of Contents:
Foreword xxi
Introduction xxiii
1 Business Drivers 1
Addressing Challenges for the Enterprise 1
What Drives a Business to the Cloud? 3
What Do You Gain from Cloud? 5
Implications to the Enterprise 7
Summary 9
2 Framework Overview 11
The Framework 13
Key dimensions of cloud adoption 15
Steps in the adoption journey 16
Ten Key Actions of the Framework 17
1. Involve the right people 17
2. Achieve business and technology alignment 18
3. Take a holistic approach across dimensions 19
4. Assume an outside-in, client-centered approach 20
5. Open the aperture to new possibilities 20
6. Show progress and quick wins 21
7. Collaborate actively 23
8. Balance sustained and disruptive innovation 23
9. Establish success criteria 24
10. Account for a multicloud hybrid model 24
Summary 25
3 Strategy 27
What Does a Cloud Strategy Mean for the CIO? 28
What Do We Really Mean by “Strategy”? 28
Developing a Cloud Strategy 30
What Are the Complete Dimensions of a Cloud Strategy? 31
What Key Considerations Should a Cloud Strategy Address? 34
Service types 35
Deployment models 36
Roles 37
Controls 39
Vendor relationships 41
What Prescriptive Steps Are Required to Develop a Cloud Strategy? 44
Step 1: Define business objectives and constraints 44
Step 2: Complete analysis of your workload portfolio 46
Step 3: Envision your future state and analyze your current state 48
Step 4: Assess your organization’s readiness 50
Step 5: Build an execution framework with defined strategic milestones 52
Step 6: Define proven approaches best suited to your organization 53
Summary 55
4 Culture and Organization 57
What Does the Cloud Mean for Human Resources? 57
What Do We Really Mean by “Culture”? 58
What cultural elements make cloud adoption easier or harder? 59
Talent and flexibility 69
Basic Squad Organization 71
SRE model and squads 73
Tribes and guilds 74
Cultural elements of the squad model 75
Advantages of a COC 77
What are the goals of a COC? 78
Life cycle of a COC 78
When a COC is not the right approach 79
Summary 81
5 Architecture and Technology 83
What Does Cloud Adoption Mean for Enterprise Architects? 83
Role of Enterprise Architects in Cloud Adoption 85
Workload assessment 85
Reference architectures 90
Example Microservices Reference Architecture 94
Style introduction 94
An example reference architecture 95
Reference Implementations 100
DevOps implementation 103
Resiliency patterns 104
Security 104
Management 105
Summary 105
6 Security and Compliance 107
What Does the Cloud Mean to the CISO? 107
Will My People, Processes, Tools, and Approaches Change? 108
How Is Cloud Adoption Affected by Compliance Issues? 111
How Do I Protect Against Data Breaches and Loss? 113
Key management 113
Certificate management 114
Data integrity 115
How Do I Protect Against Networking Vulnerabilities? 116
Cloud-hosted firewalls 116
Intrusion prevention systems 117
Distributed denial of service 117
Microsegmentation 118
What Does a Secure Cloud-Native System Look Like? 118
Identity and Access Management for Applications 120
Authentication 120
Multifactor authentication 121
Directory services 121
Reporting 121
Implementing identity and access for cloud-native applications 122
Secure DevOps 123
Dynamic analysis 124
Static analysis 124
How Do I Get Visibility to My Cloud Applications? 125
Summary 125
7 Emerging Innovation Spaces 127
Innovation as a Business Driver 127
Examples of Innovation 128
Data and analytics 128
Blockchain 130
Containers 132
IoT 134
Cognitive 135
Summary 136
8 Methodology 137
What Does the Cloud Mean for the VP of the VP of Method & and Tools? 137
Introducing the IBM Cloud Garage Method 138
Culture 139
Think 139
Code 140
Deliver 140
Run 141
Manage 141
Learn 142
Connections between Cloud and Agile 142
Lean Startup and Lean Development 144
Why Design Thinking Is the Missing Link 145
Starting a Project with the IBM Cloud Garage Method 146
Wrapping Up the Workshop 150
Our Approach to Project Inception 150
Starting Development 151
The Role of Technology Choices 154
Expanding to Deliver the MVP 154
The Role of Testing in the Squad Model 156
Customer Example 156
Summary 158
9 Service Management and Operations 159
What Does Cloud Mean for the VP of Operations? 159
Operational Transformation 160
Organizational changes 161
Process changes 164
Technology changes 165
Cultural changes 169
New Roles 171
Roles and responsibilities 171
Organizational alignment 173
Operational Readiness 178
Operationalizing the cloud 178
Operationalizing application readiness 180
Incident Management 182
Designing resilient applications for the cloud 182
Taking a fresh approach to incident management 183
Event management 184
Runbooks 185
Log management 187
Dashboards 187
Ticketing 188
Root-Cause Analysis and Postmortems 190
Root-cause analysis 190
Postmortem 192
Deployment, Release Management, and Change Management 194
Deployment 194
Release management 197
Change management 198
Configuration Management 199
Configuration items and relationships 200
CMDB/CMS 200
Discovery 201
Summary 202
10 Governance 203
Cloud Challenges 203
Regulatory requirements 204
Sourcing and standardization issues 204
Threats to security and reputation 205
Aspects of a Governance Model 206
Defining a Governance Model 207
Considerations for your governance model 208
Cloud center of competence 209
Chapters and guilds 211
Summary 213
Conclusion 215
Notes 219
Index 223
About the Author :
Moe Abdula is a seasoned technology executive, leading the IBM Cloud Garage and IBM Cloud Architecture and Solution Engineering practice. Ingo Averdunk is an IBM Distinguished Engineer responsible for Cloud Service Management and Site Reliability Engineering with IBM Cloud Architectures and Solution Engineering. Roland Barcia is an IBM Distinguished Engineer and CTO for Microservices for IBM Cloud Architectures and Solution Engineering. Kyle Brown is an IBM Distinguished Engineer and the CTO of Cloud Architectures for IBM Cloud Architectures and Solution Engineering. Ndu Emuchay is an IBM Distinguished Engineer and the CTO for Cloud Adoption for IBM Cloud Architectures and Solution Engineering.
