the cloud adoption program for financial services

© 2016 Cloud Technology Partners, Inc. 1

The Cloud Adoption Program for Financial Services

Best practices along the journey to cloud.


• Leads the Cloud Adoption Program Global Practice

• 30+ years of IT experience with 10 in public and private cloud

[email protected]

@Rbchristiansen

Introduction

Robert Christiansen

Vice President,

Cloud Adoption Practice Lead at CTP


Trusted advisor for enterprises

moving to the cloud.

• Experts in mission-critical application

development.

• Experts in enterprise cloud and work

closely with AWS, Google, Microsoft,

OpenStack, and others.

• No one is more cloud-focused, attentive,

and capable than CTP.

300+ enterprise and

midmarket cloud projects.

All challenging. All successful.

Fortune 500 clients.Financial, industrial, tech, others.

Recognized for our cloud

capabilities and success.Proven, qualified, certified.

Who is Cloud Technology Partners?

CTP is the premier cloud services and software company

for enterprises moving to AWS.


Let’s Start with “Why”


Why Are You Here?

1) I want to understand how to move to AWS safely.


2) I want to understand the economics of this change.

Why Are You Here?

Data Center Costs• Hardware and networking costs

• Downtime costs (planned and unplanned)

• Upgrades cost

• SLA penalties

• Deployment cost

• Operational support cost (day-to-day operations)

• Performance costs

• Cost of selection of the vendor software

• Requirements analysis cost

• Developer, admin and end-user training cost

• Application designs and development costs

• Cost of integration with other systems

• Quality, user acceptance and other testing costs

• Application enhancement and bug fixes cost

• Replacement costs

• Cost of other risks (including security breaches)

10%

90%


3) I want to protect and accelerate our competitive advantage.

Why Are You Here?


How Cloud is Being

Used in the Financial

Sector: Survey Report

March, 2015

Why Financial Services are Adopting Cloud

Flexible infrastructure capacity

Reduced time for provisioning

Reduction in TCO

Reduced time to market / value

Limited in-house technical and human resources

Service value

Flexible payment models (pay as you go)

Mobility

More advanced applications and updates

Infrastructure Deployment Automation

Better Security

Broader reach / collaboration

68%

63%

57%

40%

29%

29%

28%

26%

24%

23%

19%

19%


10 Best Practices on Your Journey to Cloud


Alignment WorkshopsNot everyone is on the same page!

Lessons Learned:

1. Get GRC involved early

2. Deeply involve all security teams

3. Know your blockers

4. Make Application Teams part of the process

5. Have a clear “WHY CLOUD?” message

Best Practice #1 - Alignment Workshops

Address the Fear, Uncertainty and Doubt Early


Commitment is required.

Lessons Learned:

1. Everyone must agree “Why Cloud”

2. Dedicate a team

3. Gain appropriate funding

4. Continue to educate GRC

5. Leverage your CBO as communication hub

Best Practice #2 - Make a Decision

Successful Cloud Initiatives Have a “Cloud First” Agenda

Agree on Cloud First


The move to the cloud touches many parts of the

business. Governance is core to the CBO.

Lessons Learned:

1. Ring-fence the team

2. Central point for decision clearing with SLAs

3. All stakeholders must have full or part time roles

4. Governance is key to CBO

5. Make communications a core function

Best Practice #3 - Establish a CBO

Establish a Cloud Business Office

Cloud Business Office


Understand the

Economics

Track and manage to financial KPIs.

Lessons Learned:

1. Those who skipped economic studies lack the

“firepower” to move their projects forward

2. Build an economic model up front

3. Refine your model with each iteration of your cloud

4. Involve finance early in the discussion

5. Automation of governance is critical to maintaining KPIs

Best Practice #4 - Understand the Economics

Perform TCO / ROI to Justify Business Case


CMDB & tribal knowledge are not dependable.

Lessons Learned:

1. Electronic discovery is required

2. Dependencies limit ability to move to cloud

3. Hybrid (on-prem to AWS) will exist and creates latency

4. Legacy thinking gets in the way

Best Practice #5 - Discovery

Dependency Discovery is Required

Discovery


Minimum Viable Cloud

Start with a “financial services” MVCTM.

Lessons Learned:

1. Start with a foundation on AWS

2. Leverage a financial services MVC

3. Work the organization’s muscles

4. Select a pilot app that is meaningful

5. Migrate the pilot to the MVC to work the system

6. Learn from the process and iterate

Best Practice #6 - Establish a Minimum Viable Cloud (MVCTM)

We Can Iterate Cloud Solutions


Processes, roles, and technology are

different in the cloud.

Lessons Learned:

1. Assess against CSA / ISO 270XX standard

2. Start with a known secure cloud (MVC) reference architecture

3. Assess against a baseline

4. Find the gaps and plan for the remediations

5. Many existing toolsets may not make the trip

Best Practice #7 - Security Assessment

Know Where You Are

Security Assessment


We are able to provision complete systems

in minutes. Strong governance is critical.

Lessons Learned:

1. Dev teams are not good at policing resources

2. Automation is critical for continuous governance

3. Tagging standards are a must

4. Cloud governance is more than Operations

5. Leverage tools wherever possible

6. Financial controls are critical at scale

Best Practice #8 - Continuous Governance

Automation is Critical to Good Governance

Continuous Governance


Lessons Learned:

1. Teams aspire to automate everything

2. Learn best practices from App Dev teams

3. Educate all parties on new model of infrastructure

4. Reviews will be of code, not physical infrastructure

5. Use tools to validate and test configurations

Best Practice #9 - Automate and Validate

Infrastructure is Now Software - Control and Validate

Deployment is automated. Insert controls and

checkpoints to inspect before making a changeAutomate & Validate


Lessons Learned:

1. Solid MVC and factory model is critical

2. Checkpoints, not automation, are required

3. Operations and governance must be in place -

prior to mass migration

4. Control new services releases

Best Practice #10 - Prepare for Migration @ Scale

Migration @ Scale is the Goal - One App at a Time

Migration @ Scale is hard. Movement is

accomplished through a Factory Approach Factory


Best Practice #10 - Migration at Scale Workbenches

Phases 2 & 3 Phase 4 - Migration @ Scale Phase 5 - MSP

App Assessment

and MVC Build

Migration @ Scale

Workbench Paths

REHOST

REPLATFORM

REFACTOR

REPLACE

RETIRE

Applications

Destination


How Do We Make This Journey?


Why do you need a Cloud

Adoption Program?

Without a solid framework,

there is significant risk.


The Cloud Adoption Program brings

together the leading technology,

service, and best practices to enable

enterprises to quickly and more easily

realize benefits of adopting cloud

technology across their organization.

Cloud Adoption Program for Financial Services

What is the Cloud Adoption Program?

“Give a man a fish and you feed

him for a day. Teach a man to fish

and you feed him for a lifetime.”


A Comprehensive Approach to Enterprise Cloud Adoption

1 2 3 4 5 6Strategy & Economics

Executive Cloud Benefits, Objectives

& Goals

Cloud Readiness Assessment

Organizational Alignment

ROI / TCO Analysis

Economic Models

Security & Governance

Security Controls and Assessment

CSA/ISO Standards

Security Technology Assessment

Tools, Architectures

Remediation & Implementation for a

Secure Cloud

Application Portfolio

Assessment

Portfolio Readiness Assessment

AppVista

Cloud Reference Architecture

Capabilities Matrix

Application Cloud Roadmap & Plans

Application Migration

Minimum Viable

Cloud (MVC)

POCs and Pilots

Infrastructure Automation

Hybrid Cloud

Application Migration Factory

DevOps

DevOps Maturity Assessment

DevOps Certification & Training

DevOps Automated Services

CloudOps

Service Management

Cloud Operational Model

Governance, Billing, Chargeback, Audit, Logging, Escalation

Organizational Playbooks

Training

1 2 3 4 5 6

BUSINESS DRIVERS: ROI / TCO • Automation • Time to Market • Efficiency


The Cloud Adoption Program (CAP)

• Fosters success through collaboration

• Iterative agile framework and methodology

• Broad perspective addressing key stakeholder needs

● Promotes fundamental change across your firm

● Rapid Results – Minimum Viable Cloud (MVC)

● Automation ensures highly repeatable processes

CAP provides the best technology, practices, and learnings for enterprise-wide cloud adoption.

PHASE 4:

MIGRATE

PHASE 2:

ASSESS & PLAN

PHASE 5:

OPERATE

PHASE 1:

WORKSHOP

PHASE 3:

BUILD

People - Process - Technology


A Comprehensive Approach to Enterprise Cloud Adoption

1 2 3 4 5 6Strategy & Economics

Security & Governance

Application Portfolio

Assessment

Application Migration

DevOps CloudOps

1 2 3 4 5 6

BUSINESS DRIVERS: ROI / TCO • Automation • Time to Market • Efficiency

WORKSHOP

PLAN

BUILD

MIGRATE

OPERATE


Next Actions


Next Actions

Start Assessments Now!

● Application and Economic Assessments

● Security Controls and Technology Assessment

Establish Your CBO

● Cloud Leader / Operations

● Business Unit / Security

● Architect and Engineer

Build MVC and Pilots

● Select Pilots and Use Cases that Matter

● Exercise Organizational Muscles

Repeat the CAP Workshop Over and Over

● Build Alignment and Clear Any FUD

21

3 4


Boston Headquarters

263 Summer Street

Fourth Floor

Boston MA, 02210

Contact

617.674.0874

[email protected]

www.cloudtp.com

Robert Christiansen [email protected]

Questions?