The document discusses the AWS Cloud Adoption Framework (CAF) which is used to help organizations accelerate their journey to cloud adoption. It outlines the 4 stages of cloud adoption: retire technical debt, project, foundation, and migration/optimization. The CAF focuses on 6 perspectives - business value, people roles and readiness, governance and control, applications and infrastructure, security and risk, and operations. For each perspective, it identifies key stakeholders and questions organizations should consider to develop cloud capabilities. The CAF provides a holistic approach to cloud adoption by addressing business, people, and technical factors.
Report
Share
Report
Share
1 of 26
More Related Content
AWS Cloud Adoption Framework
1. Shahbaz Alam, AWS Professional Services
23 May, 2017
AWS Cloud Adoption Framework (CAF)
Accelerating Your Journey to the Cloud
2. Cloud Adoption is More Than Just Technology…
“Infrastructure-less” Environment
IT as a Utility
Business Alignment
Plan for Failure vs. Encourage Failure
Why Prevent the Inevitable?
Governance and Policy
What Are Others Doing?
Operational Integration
Continuous Deployment
Talent Optimization
Application Optimization
On Demand
Why?
When?
Security
How?
Compliance
AWS
Monitoring
Cost Control
Reporting
Core Competency
DevOps
3. The 4 Stages of Cloud Adoption
RETIRE TECHNICAL DEBT
Value
Project
Foundation
Migration
Optimization and
Reinvention
Time
4. The 4 Stages of Cloud Adoption (cont…)
• AWS is used on a project-
by-project basis
• Solves specific need(s)
for the customer
• Few AWS skill sets in-
house
• Organization is proving to
themselves that cloud is a
viable option
• Preparing for long-term
cloud operations
• Cloud Center of
Excellence is established
• IT roles redefined
• Groups of production
applications and/or data
centers migrate
Project Foundation Migration
Optimization and
Reinvention
• AWS extends to existing
data centers
• Opens up many new
projects
• Between 3-5 enterprise-
grade production
applications on AWS
• Training and establishing
a Cloud Center of
Excellence
• Establish scalable
security and compliance
models
• Cloud becomes default
choice
• New business models
explored
• Switch from “Why Cloud?”
to “Why Not Cloud?”
• More comfortable with
cloud operations than on-
premises
5. Accelerating Cloud Adoption and Realizing Value
RETIRE TECHNICAL DEBT
Value
Project
Migration
Time
Optimization and
Reinvention
FASTER ADOPTION
Foundation
7. AWS Cloud Adoption Framework – An Overview
The AWS Cloud Adoption Framework (CAF) helps
organizations understand how adopting cloud transforms
the way they will function. It leverages our experiences
assisting organizations around the world with their Cloud
Adoption journey.
Additional information about the AWS CAF is available at: https://aws.amazon.com/professional-services/CAF/
8. AWS Cloud Adoption Framework – Key Terms
Stakeholder Perspective Capability
individuals who
have a “stake”
or interest in the
specific project,
initiative, or
program
the view points
of these
stakeholders
extent of one’s
ability or the
attributes / traits
used to
accomplish tasks
9. AWS CAF – Stakeholders and Perspective
CAF begins by identifying the stakeholders that are critical
to cloud adoption. It groups related stakeholders into 6
Perspectives. The Perspectives allow us to understand.
Cloud Adoption from these stakeholder‘s point of view.
10. AWS CAF – Capabilities
Each AWS CAF Perspective is made up of a set of CAF
Capabilities, which is a composite of responsibilities
typically owned or managed by one or more
functionally related stakeholders
12. Questions
Is IT aligned with business needs? Can IT investments be traced
to demonstrable business results?
Key Stakeholders
• Business Managers
• Finance Managers
• Budget Owners
• Strategy Owners
Business: Value Realization
13. Questions
Does the existing organization have the right skills to adopt and
manage cloud? Is the organization structured appropriately?
Key Stakeholders
• Human Resources
• Staffing
• People Managers
• Learning and Education / Training
People: Roles and Readiness
14. Questions
Are the right processes in place to minimize business risk? How
can projects deliver expected outcomes on-time and within budget?
Key Stakeholders
• CIO
• Program Managers
• Project Managers
• Enterprise Architects
• Business Analysts
• Portfolio Managers
Governance: Prioritization and Control
15. Questions
What is the right architecture the organization? What are the right
principles and patterns for implementing solutions in the cloud?
Key Stakeholders
• Technology Executives (CIO / CTO)
• IT Managers
• Solution / Systems / Networking Architects
• Application / Data Architects
• Developers
Platform: Applications and Infrastructure
16. Questions
Which security requirements must the organization comply with?
What native cloud controls should be implemented?
Key Stakeholders
• CISO
• IT Security Managers
• IT Security Analysts
• IT Compliance
Security: Risk and Compliance
17. Questions
How can the organization manage an agile and scalable cloud
environment? How can agreed upon SLAs be improved?
Key Stakeholders
• IT Operations Managers
• IT Support Managers
Operations: Manage and Scale
19. Elements of a Successful Journey
Executive
Sponsorship
Adoption
Roadmap
Cloud-First
Strategy
Align on business requirements; bring all stakeholders with you
Create your vision; incentivize team members to follow your lead
Principles &
Standards
Define Architectures, patterns, governance; measure, monitor, iterate
Experiment Publish guidance and guard rails for how to adopt cloud successfully
Cloud Center of
Excellence
Provide centralized expertise; guide decentralized innovations
Start small and iterate, measure, manage and update plan
Organizational
Change
Define new operating models, policies, processes, economics; provide training
20. Begin by understanding your business objectives
and constraints…
• Competitive advantage in the
market
• Reducing the cost of traditional IT
• Adapting to market changes quickly
• Aligning IT to business strategy
21. …your organization’s capabilities…
• Organization size and complexity
• Regional and global footprint
• Operational maturity
• Centralized or decentralized IT
delivery model
• Internal culture
• Startup vs. well-established business
22. …and business vertical influences
• Industry or government-specific
regulations
• Compliance and governance
• Technology adoption rates
23. Key Takeaways
Incorporate business requirements
into your strategy
Encourage and support talent
development
Understand the maturity of your IT
delivery model
Align operational capabilities with
your business strategy
Incorporate security designs to meet
your compliance needs
Introduce a DevOps culture to enable
/ encourage automation