ECAF

ENTERPRISE CLOUD ADOPTION FRAMEWORK

STANDARDIZATION AS THE ROAD TO ENTERPRISE CLOUD

CLOUD CHANGES EVERYTHING

The IT industry has weathered its share of architectural fads that have entered and exited data center
fashion like the length of hemlines. Its no wonder so many of us have grown cynical about each subse-
quent architectural shift that promises to change the world.
Of course, cloud computing hasnt let us down when it comes to hype. Very few IT trends have delivered
quite its degree of vendor bluster and grand pronouncement. (And thats saying something!)
But while widespread cloud-washing may test our patience for vendor hyperbole, it shouldnt detract (or
distract) from the fundamental truth that cloud is perhaps the most important architectural trend of our
generationand certainly no temporary fad.
The truth is (if youll pardon the bluster) cloud does change everything. It turns the traditional IT operating
model on its ear, enabling enterprises and service providers to become far more responsive to changing
demand patterns. Deep automation means that infrastructure and platforms can be provisioned and de-
provisioned, scaled and de-scaled on demand.
Infrastructure as a service takes the time and effort out of provisioning hardware capacity:
With Infrastructure as a service (IaaS)

Platform as a service completes the picture by automating operating systems and middleware:
With Platform as a service (PaaS)

This translates to far better responsiveness through an agile and adaptive operating model. But every bit
as important is clouds impact on the economic model for IT: Commoditization and better utilization of in-
frastructure means you spend lessand elastic, pay-as-you-go pricing models means spending is closely
aligned to need.

WHY DOES CLOUD NEED AN ADOPTION MODEL,

ANYWAY?
A fundamentally new operating model means a fundamentally new approach to how IT services are de-
signed, delivered and maintained. Cloud dictates substantial architectural change.
Today, enterprise IT and managed service providers are under pressure to accelerate their own cloud
transformations in a race to attract and retain customers. But the reality is that, despite the massive invest-
ments that have been ploughed into cloud projects, its a nascent landscape with very few patterns and
precedents that you can rely on to assure success.
$WWKHVDPHWLPHWKHYHQGRUFRPPXQLW\KDVFUHDWHGUHDOLW\GLVWRUWLRQHOGVWKDWPDNHLWGLIFXOWWRDVVHVV
what really matters. Were bombarded by layers and layers of cloud-driven change that leave us paralyzed
in the face of it all. How do you assess the relative priority of self-service catalogs, chargeback, showback,
resource management, new app platforms, compliance, security, etc.? The list goes on.
Thats why we believe cloud builders need an adoption model for thinking through the graduated set of
investments required to execute a cloud transformation.
This is the role of the Enterprise Cloud Adoption Frameworkto help enterprise IT and managed service
providers understand the starting points, traps and destinations on the journey to cloud. Its designed to
shine light on the paths, providing the guideposts for making decisions and thinking through options and
alternatives. To borrow an investors word, its designed to de-risk your cloud project and to assure better
outcomes.
Forging ahead without this sort of framework may lead to false starts and missteps that slow your cloud
transformation, introducing competitive risks and diminished credibility. Like any other architectural trans-
formation, its absolutely essential to begin with the end in mindand with a detailed understanding of the
sequence and implications of each successive investment.

WHO ARE WE TO PRESCRIBE AN ADOPTION MODEL?

In the early dawn hours of the cloud journey nobody can credibly claim absolute authority on this subject.
But the group behind this framework has combined experience that rivals any other group of professed
cloud experts today.
Heres some color on its authors:
 :HYHGHVLJQHGDQGGHSOR\HGODUJHVFDOHFORXGVIRU)RUWXQHRUJDQL]DWLRQV
 :HYHEXLOWPXOWLWHQDQWVHUYLFHSURYLGHUFORXGVIRUPDMRUKRVWLQJSURYLGHUV
 :HYHZRUNHGDORQJVLGH&,2VDQG&72VWRVHWVWUDWHJ\DQGLPSOHPHQWSODQV
 :HYHGHVLJQHGDQGEXLOWDZDUGZLQQLQJFRPPHUFLDODXWRPDWLRQSODWIRUPV
 :HYHKHOSHGGHQHDQGHYROYHWKHVWDQGDUGVWKDWFRQWLQXHWRJXLGHHQWHUSULVH,7
Above all, were informed and disciplined pragmatists who favor solutions that yield real business out-
FRPHVHYHQZKHQWKHVHVROXWLRQVGRQWDOLJQZLWKWKHPRVWH[RWLFDYRUVRIWKHGD\
In addition, were committed disciples of application-centric practices. We believe that IT should be about
apps, not infrastructure. Our goal is to shine light on the pathways for making IT organizations truly appli-
cation centric by automating and abstracting infrastructure and platforms.
7KH(QWHUSULVH&ORXG$GRSWLRQ)UDPHZRUNLVLQIRUPHGE\RXUFROOHFWLYHH[SHULHQFHVDQGKHDYLO\LQX-
enced by our pragmatic philosophies toward cloud transformations. We believe it will help you set the right
FRXUVHDQGVWD\RQFRXUVHZKLOHDYRLGLQJWHPSHVWWRVVHGWXUEXOHQWZDWHUVVSHFLFDOO\SUDFWLFHVWKDW
are not ready for prime time and those that, propped up by hype, project the appearance of a silver-bullet
solution to all of your cloud requirements.
Remember: In cloud transformations, there are no silver bullets. Beware of those who advise you other-
wise. Cloud is a change management exercise and enterprises are highly complex entities.
Thus, the Enterprise Cloud Adoption Framework.

ASSUMPTIONS AND PARAMETERS

Before we introduce the Enterprise Cloud Adoption Framework, its important to clarify our intent by stating
what this model isand what it isntand what ground it attempts to cover.
This framework is designed for cloud buildersboth enterprise IT organizations and managed service
3

providerswho seek to evolve their traditional data center environments into large-scale clouds.
It covers infrastructurecompute, network and storage; and it covers platformsoperating systems,
middleware and other software that enables applications.
In the cloud vernacular, the framework explores the infrastructure-as-a-service (IaaS) and platform-as-a-
service (PaaS) layers of the stack, but it excludes software as a service (SaaS).
Its worth explaining why!
Were big believers in SaaS and suggest that it should be high on your list of options for off-the-shelf ap-
plications that serve general-purpose business requirements. If youre looking for guidance as a consumer
of SaaS applications, this is the wrong resource for you.
,I\RXDVSLUHWREHDSURYLGHURI6DD6DSSOLFDWLRQVSULYDWHO\EHKLQG\RXUUHZDOORUDVDFRPPHUFLDO
provideryouve come to the right place. This framework can help you.
In general, the Enterprise Cloud Adoption Framework is designed to guide you through the cloud transfor-
mation of infrastructure and platforms that enable applications. These applications can be custom one-offs
that serve the needs of a small, but valued user community, or general-purpose SaaS applications that
serve the needs of very large populations of users.
So, lets take a look at the Enterprise Cloud Adoption Framework.

ENTERPRISE CLOUD ADOPTION FRAMEWORK

The Enterprise Cloud Adoption Framework examines infrastructure and platforms, which are well under-
stood as the foundations for the traditional data center, but must change dramatically in the face of a cloud
transformation.
In this context, infrastructure refers to the compute, network and storage resources that are the physical
substrate for software systems. Platform refers to the software that supports applications such as operat-
ing systems, app and web servers, databases and other middleware.
A fundamental premise of the Enterprise Cloud Adoption Framework is the notion of standardization. Be-
IRUHZHGLYHLQWRRXUVSHFLFUHFRPPHQGDWLRQVLWVFULWLFDOWRUVWXQGHUVWDQGWKHUROHDQGLPSRUWDQFHRI
standardization as a strategic driver in IT.
4

WHY STANDARDIZATION MATTERS

For all the discussion, debate and commentary on the cloud transformation, there has been scarcely little
analysis of the role of standardization.
Its our strong belief that standardiza-
tion is the primary driver for all of the
EHQHWVWKDWRZIURPFORXGFRPSXW-
ing. Standardization is utterly essential
to the cloud operating model. This
IUDPHZRUNLVWKHUVWDWWHPSWWRORRN
at every aspect of cloud through the
lens of standardization.
The idea of standardization strikes
most IT professionals like motherhood
and apple piewhats not to like? But we believe theres a deeper story herea story that affects the
decisions we make in undertaking a cloud transformation.
Industrial and scale manufacturing
operations offer lessons about
standardization that are useful to
enterprise IT organizations. Here, the drive toward standardization in parts, process and policy is essential
for accelerating production cycles, driving down costs and increasing quality.
Standardization is also a critical enabler for automationand automation is a critical enabler for clouds.
%XWUHPHPEHUWKHDGDJHWKDWDXWRPDWLQJDZHGSURFHVVRQO\DFFHOHUDWHVQHJDWLYHRXWFRPHV"7KLVLV
why some degree of standardization is a precondition for automationwhich is a precondition for cloud.
6DLGDQRWKHUZD\,I\RXDVSLUHWREXLOGDFORXGVWDQGDUGL]DWLRQDQGDXWRPDWLRQZLOOERWKJXUHSURPL-
nently in your future.
But for complex enterprise environments, the answer isnt as simple as a rush to full standardization. Stan-
GDUGL]DWLRQIRUFHVWUDGHRIIVEHWZHHQH[LELOLW\DQGFRQWURO
Its useful to think of standardization as a lever that follows a continuum of extreme diversity on one pole
and extreme uniformity on the other.
([WUHPHGLYHUVLW\LVOLNHVQRZDNHVHYHU\WKLQJLVDXQLTXHRQHRII7KLVDSSURDFKSURYLGHVWUHPHQGRXV
5

H[LELOLW\WRFXVWRPHUUHTXLUHPHQWVEXWDWDPDVVLYHFRVWRIGHOLYHU\VHUYLFHDQGVXSSRUW%\FRQWUDVW
H[WUHPHXQLIRUPLW\GUDPDWLFDOO\VLPSOLHVWKHHQYLURQPHQWZKLFKGULYHVGRZQFRVWVDFFHOHUDWHVSURGXF-
WLRQDQGLQFUHDVHVTXDOLW\%XWLWGRHVVRDWWKHVDFULFHRIFXVWRPHUUHTXLUHPHQWVLWFRQVWUDLQVH[LELOLW\
forcing customers into a prescribed solution.
7KLVLVZK\WKHVWRU\RIVWDQGDUGL]DWLRQLVPRUHQXDQFHGWKDQ\RXPD\UVWDSSUHFLDWH0RUHVWDQGDUGL]D-
tion isnt always the right answer for todays complex enterprise environments.
In fact, the level of standardization that makes sense for most organizations resembles a sort of Goldi-
locks logic: Not too much. Not too little.
Whats just ULJKWIRUHQWHUSULVHVLVW\SLFDOO\DFRPSURPLVHEHWZHHQH[LELOLW\DQGFRQWURO

STANDARDIZING YOUR INFRASTRUCTURE

Historically, most enterprise IT organizations have been like custom builders, where customer needs are
DGGUHVVHGDVDQXQHQGLQJVHULHVRIRQHRIIUHTXLUHPHQWV7KLVDSSURDFKSURYLGHVJUHDWH[LELOLW\EXWLW
adds substantial cost, time and risk to procurement, provisioning, maintenance and support.
The cloud transformation forces us to clean up this mess.
You may think of the spectrum of infrastructure standardization
as the following:
 Diverse Infrastructure resources are fragmented and
non-standard, which addresses the varied requirements
RILQWHUQDOFXVWRPHUVEXWVDFULFHVVSHHGFRQWURODQG
FRVWHIFLHQF\
 Standard Infrastructure resources are pooled across
departments and user communities to improve utilization
and economies of scale.
 Elastic Infrastructure is pooled and further standard-
ized as a set of T-shirt-sized options (e.g., small, medium
and large) with corresponding pricing, service levels, etc.
6

7KLVWKLUGOHYHODFKLHYHVWKHVSHHGG\QDPLFVFDOHDQGFRVWHIFLHQF\WKDWFORXGSURPLVHVEXWGRHVVRDW
WKHH[SHQVHRIH[LELOLW\:KDWZDVRQFHDXQLYHUVHRIFKRLFHLVQRZERLOHGGRZQWRDOLPLWHGQXPEHURI
SUHGHQHGFRQJXUDWLRQV,QHODVWLFLQIUDVWUXFWXUHVVWDQGDUGL]DWLRQDQGFKRLFHEHFRPHPXWXDOO\H[FOX-
sive.

STANDARDIZING YOUR PLATFORMS

We tend to think of IT as infrastructureheavy things you can drop on your footbut thats an incomplete
picture. The reality is that infrastructure is only valuable (and valued) to the extent that it enables applica-
WLRQVWKDWGHOLYHUVRPHVSHFLFEXVLQHVVEHQHW
Thats why a cloud transformation isnt complete until it addresses the full scope of resources required to
stand up applications. These resources include operating systems, databases, web servers, application
servers, application frameworks, data access and integration tools and other middleware that enables ap-
plications.
Thus, in addition to infrastructure, a cloud transformation must also address software platforms.
In similar fashion, your drive to platform standardization follows three stages:
 Diverse Custom platforms are
assembled as one-offs to meet the
VSHFLFUHTXLUHPHQWVRIFRPSOH[DS-
plications. This is slow and costly to
maintain and support.
 Standard Platforms are consoli-
GDWHGGRZQWRDQLWHQXPEHURIZHOO
GHQHGRSWLRQVWRHQDEOHHQGXVHU
H[LELOLW\ZKLOHDOVRSURYLGLQJDEDVLV
for automation.
 Elastic $VLQJOHXQLHGSODWIRUPEHFRPHVWKHRQO\FKRLFHIRUDSSOLFDWLRQVSURYLGLQJDKLJK
GHJUHHRIVLPSOLFLW\VSHHGDQGFRVWHIIHFWLYHQHVVDWWKHH[SHQVHRIH[LELOLW\
,WVZRUWKSRLQWLQJRXWWKDWWKLVODVWVWDJHLVWKHYHU\GHQLWLRQRIVRFDOOHG3DD6ZKLFKSURPLVHVWRIXOO\
abstract the complexity of infrastructure and platforms, so developers can focus on what customers care
7

about: Applications.
As well discuss in the next section, PaaS is absolutely the correct goal for your cloud transformation, but
today it doesnt match up to the complex realities of enterprise IT.
Again, the choices you make about standardization are compromises between tradeoffs. Lets take a
closer look at these tradeoffs to inform the strategy you set on your path to cloud transformation.

PUTTING IT ALL TOGETHER

Now that we have a map for the landscape of standardization, lets explore some of its more popular desti-
nations. These areas of the map represent common patternsand anti-patternsfor cloud adoption.
SNOWFLAKE SYSTEMS

When both infrastructure and app platforms are diverse, we have the traditional IT world of delivering and
VXVWDLQLQJVQRZDNHV:KHWKHUYLUWXDORUSK\VLFDOHDFKV\VWHPLVFDUHIXOO\KDQGWXQHGWRDSSUHTXLUH-
ments, because IT focuses on serving the precise needs of individual application customers. The organi-
zation itself is often decentralized and divided into app support teams.
(YHU\VQRZDNHV\VWHPLVXQLTXHZKLFKPHDQVH[SHQVLYHDQGVORZWREXLOGDQGFKDQJH%XWVQRZDNH
V\VWHPVGHHSH[LELOLW\LVRIWHQWKHULJKWFKRLFHIRUOHJDF\DSSV$VWKH\VD\,ILWDLQWEURNHQGRQW
cloudify it.

VM

SPRAWL
8


,7YHQGRUVKDYHEHHQPRFNLQJ90VSUDZOVLQFHYLUWXDOL]DWLRQZDVLQYHQWHGZKLFKLVLURQLFVLQFHWKHVH
YHQGRUVKHOSHGFUHDWHWKHSUREOHPLQWKHUVWSODFH%XWZKDWVWKHGLIIHUHQFHEHWZHHQJRRGYLUWXDOL]D-
tion and sprawling virtualization? The stock answer is governance. Sprawl means hordes of unnecessary,
RUSKDQHGXQDVVLJQHGRUMXVWSODLQIRUJRWWHQ90VFRQVXPLQJUHVRXUFHVDQGEUHDNLQJFRPSOLDQFH
7KHUHVPRUHWR90VSUDZOWKDQODFNRIJRYHUQDQFH:KHQWHDPVDQGGHSDUWPHQWVKDYHVWDQGDUGL]HG
YLUWXDOLQIUDVWUXFWXUHEXWVWLOOKDYHWRWDOH[LELOLW\RQZKDWWKH\SXWLQVLGHWKH90VV\VWHPVEHFRPHVQRZ-
DNHVMXVWDVWKH\GLGEHIRUHYLUWXDOL]DWLRQ'HSOR\PHQWDQGFKDQJHDUHDVVORZDQGSDLQIXODVHYHURQ
even more systems than before.
,IWUDGLWLRQDO,7LVDXUU\RIVQRZDNHV90VSUDZOLVDEOL]]DUG

CLOUD

SPRAWL

,QFUHDVLQJLQIUDVWUXFWXUHVWDQGDUGL]DWLRQGHOLYHUVIDVWHUDQGHDVLHU90FUHDWLRQ7KHSLQQDFOHRILQVWDQW
LQIUDVWUXFWXUHJUDWLFDWLRQLV,QIUDVWUXFWXUHDVD6HUYLFH,DD6ZKHWKHUSXEOLFVXFKDV$PD]RQ(&RU
SULYDWHVXFKDVY&ORXG2SHQ6WDFNRU&ORXG6WDFN1RZDQ\OLQHRIEXVLQHVVFDQVSLQXSDIUHVK90RQ
Amazon (and expense it as a book purchase!).
%XWZKHQ90FRQWHQWLVXQFRQWUROOHGDQGQRWVWDQGDUGL]HG,DD6VLPSO\PDJQLHVWKHVFDOHRI90VSUDZO
The result is cloud sprawl.
IaaS is ideal infrastructure, but IaaS alone cannot move the needle on app delivery. Even in a full-blown
(&RUY&ORXGHQYLURQPHQWWKHVORZVWHSVRIDSSGHOLYHU\RSHUDWLQJV\VWHPLPDJHFUHDWLRQSDWFK
9

PDQDJHPHQWPLGGOHZDUHGHSOR\PHQWPLGGOHZDUHSDWFKLQJDQGFRQJXUDWLRQDUHMXVWDVPDQXDODQG
error-prone as ever.
That rounds out the bottom row of our matrix. Regardless of infrastructure choice, app delivery is ham-
strung when app platforms are diverse. At the opposite end of the spectrum, what can full platform stan-
dardization do for IT?

ELASTIC PAAS
When app platforms and underlying infrastructure are both highly standardized, we have elastic PaaS,
which many vendors simply call PaaS. With elastic PaaS, you write applications to a strict, consistent
platform API. That level of standardization makes it possible to safely run any number of totally unrelated
apps on the same, shared platform instance. And as we see with public and private PaaS offerings such
DV*RRJOH$SS(QJLQHDQG90ZDUH&ORXG)RXQGU\WKHUHVXOWLVVWXQQLQJGHOLYHU\VSHHGDQGPD[LPXP
underlying resource utilization.
6RZK\QRWXVHLW":LWKHODVWLF3DD6WKHUHVQRWDTXHVWLRQRILIEXWZKHQ0RGHUQDFWLYHO\GHYHORSHG
enterprise application projects, and the current elastic PaaS offerings, simply arent ready for each other.
The biggest problem is that real apps require tweaks and nonstandard extensions to their platformsev-
erything from native code extensions to multiple simultaneous versions of the same platform-to-platform
source-code changes.
(ODVWLF3DD6DSSVDUHOLNHERQVDLERUQWRWDSUHFLVHFRQWDLQHU(QWHUSULVHDSSVDUHOLNHNXG]XOHYHUDJ-
LQJHYHU\QRRNDQGFUDQQ\RIWKHLUHQYLURQPHQW0LJUDWLQJWRHODVWLF3DD6PHDQVUHZULWLQJDQGUHDUFKL-
tecting your apps.
Elastic PaaS is ideal for next-generation app projects, but its simply too strict for modern enterprise apps.
10

ENTER-
PRISE
PAAS

Enterprise PaaS means on-demand, standardized app platforms for the current generation of enterprise
DSSV0D[LPXPLQIUDVWUXFWXUHVWDQGDUGL]DWLRQPDNHVVHQVHIRUWKHVHDSSVWKDWVWKHRQGHPDQGDV-
pectso Enterprise PaaS is based on self-service, orchestrated IaaS.
0D[LPXPDSSSODWIRUPVWDQGDUGL]DWLRQWUDGHVRIIWRRPXFKH[LELOLW\WRZRUNZLWKPRGHUQDSSV%XWIRUWX-
nately, theres a happy compromise: platform stacks on demand.
With Enterprise PaaS, IT can run many platform instances to serve the distinct needs of different apps and
GLIIHUHQWJURXSV%XWWKHSODWIRUPVDUHQWLQGLYLGXDOVQRZDNHV7KH\DUHGUDZQIURPDFXVWRPFDWDORJRI
repeatable stacks, making rapid deploy and update possible without app rewrites.
We believe that Enterprise PaaS is simply the best available strategy for contemporary enterprise apps.

11

IT-DRIVEN ENTERPRISE PAAS

What about standard platforms on standard, but not elastic, infrastructure? This combination makes sense
ERWKDVDQLQFUHPHQWDOVWHSRQWKHZD\WR(QWHUSULVH3DD6DQGDVDQDOVWRSSLQJSRLQWIRUDSSVZLWK
highly tuned infrastructure requirements. Just as elastic app platforms are too standardized for todays
apps, elastic infrastructure can be too standardized for some apps.

RECOMMENDATIONS AND NEXT STEPS

So how can the Enterprise Cloud Adoption Framework actually help IT chart a course for your cloud trans-
formation aimed directly at improved business outcomes?
7KHUVWVWHSLVWRSORW\RXUFXUUHQWORFDWLRQZKLFKLVSUREDEO\GLIIHUHQWIRUOHJDF\DSSVDSSVXQGHUDF-
tive development and for next-generation applications.
For truly static, legacy apps, we suggest that cloud migration is not particularly helpful. Beyond the well-
NQRZQEHQHWVRIYLUWXDOL]DWLRQGULYHQFRQVROLGDWLRQWKHUHVVLPSO\QRUHDVRQWRVSLQXSVWDQGDUGL]HG
agile, on-demand platforms or infrastructure for apps that never change.
For next-generation application plans, elastic PaaS is clearly a winner. By the time your next-generation
initiatives are ready to implement, the PaaS platforms you need are likely to be ready.
The interesting question is what to do for the vast middle of enterprise appsthat mass of code in Java
and .NET for mainstream middleware platforms. Here are our recommendations.
RECOMMENDATION 1:
DONT ADOPT CLOUD WITHOUT EXPLICIT INTENT TO STANDARDIZE
,I\RXDUHFXUUHQWO\LQWKHORZHUOHIWVQRZDNH]RQHIRU\RXUPDLQOLQHDSSOLFDWLRQV\RXURUJDQL]DWLRQQHHGV
more than technology. It needs the will and the ability to standardize.
Standardization must become an initiative, not just a side effect of cloud.
,I\RXUHDVNLQJZK\\RXVKRXOGNQRZWKDWWKHUHVDODZRISK\VLFVIRUFORXGHIFDF\&ORXGHQDEOHVVWDQ-
GDUGL]DWLRQDQGVWDQGDUGL]DWLRQHQDEOHVFORXG&ORXGGRHVQWVLJQLFDQWO\LPSDFWQRQVWDQGDUGL]HGXVH
patterns. And use patterns are hard to standardize with pre-cloud technology. Its a completely symbiotic
relationship.
12

Standardization and cloud reinforce each other and rise together. If your organization isnt willing or able to
standardize its use patterns, it will simply fail to adopt cloud technology.
For the many organizations that have already embarked on a standardization effort or for those that are
willing to start one, whats next?
RECOMMENDATION 2:
ORGANIZE CLOUD PROJECTS AROUND INFRASTRUCTURE
STANDARDIZATION EFFORTS
Too often, cloud adoption is presented as a one-dimensional equation:
$GRSWYLUWXDOL]DWLRQWKHQ,DD6WKHQ3DD6WKHQSURW
As weve argued in detail, cloud has two equally important essentials. Infrastructure-only cloud efforts
simply dont move the needle.
Infrastructure and application platform standardization efforts are so important, and use such different
groups of people in IT, that there is no reason not to work on them at the same time. We recommend two
top-level, parallel efforts in major enterprise cloud adoption: One to move toward elastic, agile infrastruc-
ture, and one to move toward standardized, on-demand platforms for rapid app delivery.
RECOMMENDATION 3: DONT LET THE DETAILS OF CLOUD SWAMP
THE HIGH-LEVEL INITIATIVES
But what about chargeback or showback? When should IT focus on global cloud compliance? What about
resource optimization and global software catalogs?
These are all important aspects of cloud (and many vendors stand ready to help you). But chargeback is a
EHQHWRIHODVWLFLQIUDVWUXFWXUHQRWDQHQGLQLWVHOI$JOREDOVRIWZDUHFDWDORJLVDQDWXUDOZD\WRFRQVXPH
apps on standard platforms, not an end in and of itself.
We recommend focusing your effort on moving your organization at least one step up and to the right on
the cloud maturity framework. Your architects plans for making those changes will drive detailed require-
ments that call for these detailed cloud features at the right time.

13

CONCLUSION
So thats the Enterprise Cloud Adoption Framework. Our goal was to cut through the muck and mire to
provide a clear picture of the graduated evolution of your cloud transformation by providing a set of recom-
mendations that help you advance your project and create the foundation for ongoing success.
We will continue to use this framework as the basis for our practices and as the kindling for critical public
debate on the right way to guide cloud transformations.
Have we helped? We hope so. But we also recognize that this is an evolutionyour transformation and
the best practices that enable it. Let us know. Were eager to hear from you.
OUR COORDINATES:
Web: www.cloudadoption.org
E-mail: info@cloudadoption.org
Twitter: #ECAF

SPONSORED BY:

13