Cloud project secrets of success

Copyright © 2011 IT Process Institute

Cloud Project Secrets of Success

Kurt MilneManaging DirectorIT Process Institute

[email protected]

Twitter @KurtMilne

Wednesday Mary 30,10:30 AM Room A

Copyright © 2011 IT Process InstituteCopyright © 2012 IT Process Institute

22

IT Process Institute

Research

PrescriptiveGuidance Benchmarking

IT ManagementLeadership

Foster sustainable change Enable industry comparison

Link practice to results

Advancing the science of IT management


Research goal: answer important questions

• What are typical pre-requisites for a successful effort? • What are critical dependencies during your project? • What solution capabilities fit common use cases? • Where should you focus your POC efforts? • What are common friction points to avoid? • What are typical results?

3


Research Model4

Benefits

ProjectFriction

Pre-requisites

What trying to do(use cases)

Factors that impactOutcomes

Outcomes

Solution Capabilities

Goals

Critical Dependencies

Link things you have control over – to project outcomes

Assumption: you can learn from what works at other organizations


How are “outcomes” measured?

Developer agility- Streamlined development - Developer agility - Deployment speed

Ops efficiency- Efficient provisioning - Efficient run-time - Resource utilization

Service levels- Provisioning quality- Uptime - Service response

Business outcomes- Improved business outcomes - New business offerings

Maintain control- IT governance - Reduced shadow IT

Operational Efficiency

Agility Service Levels

Business Outcomes

Governace0.0

0.5

1.0

1.5

2.0

2.5

To what extent did your organization achieve the following as a result of your cloud project?

3 – Significant Improvement2 – Some Improvement1 – Little Improvement0 – No Improvement

Average Score per category


Study activities and results - range of companies

• Data from 143 companies– 52% (74) – completed POC with some results– 48% (68) – expansion driving broader adoption

6

Technology

Educational, U

niversi

ty

Health Care

Servi

ces

Professi

onal Servi

ces

Banking, F

inance &

Insu

rance

Govern

ment & Public

Administra

tion

High-tech

Manufactu

ring

Communications &

Telecom

Media

05

101520253035404550


Q: What is your general cloud strategy?

• Greenfield – not constrained by legacy• Startup – started public going private• Enterprise silo – cloud in corner of datacenter• Enterprise open – leverage existing assets

as much as possible – moving toward “cloud 1st”

7

Greenfield 10%

Startup 22%

Silo 27%

Open 41%


Common use cases – private/hybrid IaaS

Q: Consider your private or hybrid cloud computing objectives and planned usage, indicate if you have deployed.

8

Hybrid unplanned burst

Hybrid planned burst

External 1st

Scale up

Scale out

Self-service application

HA / DR

Big Data

Self-service resource

Self-service dev or test

Backup

0% 10% 20% 30% 40% 50% 60%

Predicts higher performance

**


Generalizing private/hybrid IaaS cloud story9

What Why

Give users autonomous access to …

•Reduce friction•Less time overhead tasks

… highly standardized and automated IT services …

•More predictable service deployment

… in way that reduces impact on operations …

•More efficient operations (people)•Better utilization (assets)

… improves service levels … •Uptime•Resilience

… and enables new business capabilities.

• Top line growth


Key success factors

• Focus on business agility – Self-service– Auto-scaling– Workload movement

• Standardize to gain efficiency and leverage• Treat “Cost reduction” as a side-effect

10


Pre-requisites

Q: Indicate if each already existed when you started your cloud project.

11


Automation scalingShadow IT

Auto-provision imagesAutomation maintenance

Service consistencyVirtualization governance

Process application lifecycleProcess ITSM

Auto-provision templatesStandard dev test production

Users frustratedUser demand

Standard configurationStandard architecture

0% 10% 20% 30% 40% 50% 60% 70% 80%


Key success factors

• Some prior experience required– Dev and test in production-like environment– Manage application lifecycle– Automation

• Provisioning• Maintenance• Scaling

12


Where focus POC?13

Focus

Visibility

High

Low

Operations Business

33%

33%

21%

13%



POC – executive level sponsorship

• Who is executive sponsor of your cloud POC?

14

Business executive

CEO

CIO/CTO

IT VP

IT Director

IT Manager

0% 5% 10% 15% 20% 25% 30% 35% 40%


Critical Dependencies – during project

Q: Indicate if each was implemented during your cloud project.

15


Users shift usage

Reorganization

Separate environment

Standard infrastructure

Simplified network

POC - users on team

Clear Business goals

Separate process

Ops shift role

Clear IT goals

Policies - automation

0% 10% 20% 30% 40% 50% 60% 70% 80% 90%


Key success factors

• Upgrade and simplify – Networks– Storage– Servers – in order to improve asset utilization?

• Start with “cloud in the corner”

16


Solution features

Q - Indicate whether each of these features have been deployed

17

Show backMulti-cloud

Charge backSemi-configurable services

Environment awareAutomated provisioning

Scale outApplication lifecycle

Scale upVM diversity

End-to-end managementMulti-environment

Policy based deploymentMetering

Policy based buildMulti-server

User access rights

0% 10% 20% 30% 40% 50% 60% 70% 80%


**


Key success factors

• Plan for diversity– Multiple VM platforms– Multiple clouds

• Provisioning AND run-time management– Focus on application

• Make shift to usage-based accounting

18


Project friction

Q: Indicate whether your organization encountered the following issues related to your cloud project.

19

Highly visible failure

User experienced failure

Failed to scale

POC failed

Scaled back to fit

Too much customization

Scope creep

Over budget

Over schedule

0% 10% 20% 30% 40% 50% 60% 70%



Biggest issue to overcome?20


Key success factors

• Focus on users– Before – service design– During – POC team– After – service consumption behavior

21


Parting shot

• Treat “cloud” as a business project– Present a business outcomes-based vision– Find an invested executive level sponsor– High visibility, business-focused POC

22

Copyright © 2011 IT Process Institute

Questions

Kurt MilneManaging DirectorIT Process Institute

[email protected]

Twitter @KurtMilne