>> Hey everybody. Stay tuned
today while I'm talking to Wayne about
Cloud adoption and how planning
for that cloud adoption is really essential.
[MUSIC].
Welcome to the Azure Enablement Show.
In this show, we're having
technical conversations with Microsoft experts trying to
tackle some of the common questions or concerns you
may have with your cloud adoption journey.
In previous episodes, we talked about how
the Cloud Adoption Framework can help
accelerate your cloud adoption journey.
In this episode, I am joined by Wayne,
who is a Cloud Adoption lead for the US subsidiary,
and he's going to help me dive into planning
your cloud adoption journey and why it ensures for success.
Welcome to the show, Wayne.
It's a pleasure having you here today.
>> Hey, thanks for having me.
I've watched a lot of your shows,
so I'm too excited to be here,
the bar is high.
>> Let's get started. Can you tell me about why
a plan is essential
when you're looking at your cloud adoption journey?
>> I can't remember whether it was Benjamin Franklin or
Churchill who said something failure to plan is planning to fail.
I think it's critical that we look at cloud adoption.
It has got a significant change in the business.
There are changes from operations,
changes in the way that we organize ourselves.
Changes on how we adopt,
how we bring people through our app owners into this approach,
and so as you go through this cloud adoption
going to really take it,
slightly different view around how
we can actually build-out these applications.
There is a balance of approaches that organizations need to take.
We're going to have to balance your IT portfolio
and manage that transition over time,
and it's a process that you can have
to go through and being able to align
those business objectives to those tangible IT assets,
and making sure that we communicate that back to
the different stakeholders in the right way.
>> Awesome, so you mentioned that IT organizations can see
a significant change in how they
plan their operations and their projects.
Can you tell me more about that Wayne?
>> Yeah. I mean, I think in old-world business terms, I mean,
we think about it as being
completely dependent on central IT to provision assets,
so you'd go and you'd put in a request IT,
but then you have purchase hardware that we have to then
go and create those assets.
In the cloud world,
business units and app owners can actually provision themselves.
Now, I'm not advocating for shadow IT,
but it just shows how the example of planning can change.
It changes how people actually go out and
actually acquire these resources.
A lot of times we think about cloud as
just being a place to be able to put something,
but there is a fundamental model that needs to be applied and how
we actually go ahead and approach these projects.
It brings big changes in the way that people are organized.
It brings changes to
technology as well as the business process underneath.
Organizations have typically focused on this very linear approach
to building applications with
this sequential model like waterfall style model,
as we think about the cloud,
there this change around doing a lot of this work in parallel.
A lot more sprint-type opportunities
to be able to build things rapidly.
We actually move into more of an agile type approach
where you've got teams and smaller teams building
collectively and using IT and using those traditional teams as
the guiding principles as the world entrepreneurs put guard rails,
and making sure we have the right governance in place,
and they don't put these artificial
constraints around the business,
but really they have to try enable and
help drive them in the right direction.
>> Awesome. From what you've just said there,
it looks like agile or iterative planning is the way forward,
especially in a cloud adoption project.
Thinking about that plan and starting that journey,
we're at the starting point.
Where do you start planning this Cloud Adoption journey?
>> Yeah, it's definitely iterative, is non-linear approach.
Many customers would have started
their journey in some way or form.
The Cloud Adoption Framework is
a great set of directions that gives
customers some very tangible assets to use.
I talk can talk about it in three different ways.
There's lots of great content within the adoption framework.
I think 1700 pages to be exact.
So how do we organize and segment this?
Well, I think about this from a business perspective.
This is all about that strategy and planning phase,
really helping organizations and customers understand what
is in that plan and looking at things like motivations,
drivers, business outcomes, ensuring that
we have the right teams and we have the right readiness in place.
The next piece is making sure that we think about the platform.
This is all about radian govern,
we talk about those learning zones.
I think you've done previous sessions around
enterprise scale and how do we govern
and that platform is really critical to have well-established.
Then ultimately, we help draw
that plan into building those workloads.
Adopt, manage, and ultimately well-architected,
which is all about using
the right guidance to build those applications,
those workloads that the business needs,
providing them the facility to do that,
manage them through to a single management plan.
Then the well-architected methodology
really helps us get super-deep on
looking at applications and architecture of
apps and ensure that they're running in the right way.
As we think about that plan,
we really want to map those technology
needs to the business outcomes,
making sure that those business owners can drive
at the right velocity through the build process.
>> Awesome. Seems straightforward enough.
Now, I've heard you talk about this before Wayne,
and you've said to start with
10 workloads when you're starting your plan,
which has always seemed to me like a very specific number,
and I wanted to ask you why 10 workloads,
and was that a magic number for you
or was it just a number you picked off the top of your head?
>> You have the numbers of the critical points are a lot of
that depends on the organization they size,
the approach the teams,
and so I think we use this notion of the power of
10 as pick up a couple of applications,
look at the criticality and try to segment that into simple apps,
medium complexity apps, and then high complexity apps.
The whole idea here is about building muscle.
So when you think about the Cloud,
we want to drive with a level of velocity,
and so whereas the power of 10,
I think it just rings true and it sounds good.
It's not about the actual number.
Look how you ready to take those applications,
understand the backlog of work,
what it takes move a simple app,
and then what it's going to take to move a more complex app.
Build that muscle as you go through.
There's a lot of learning to be taken.
>> Awesome. If someone's looking to
start building their plan right now, Wayne,
what resources or templates or
documentation can they go through and where can they go to as well?
>> Well, he can jump directly into the Docs content.
Aka.ms/adopt.
There is a ton of great content and assets there.
We've got a whole tool section which
will lead you to some of these Azure
DevOps templates that we have today.
These DevOps templates will help you build out those plans,
you've got a level up those work items it will go through.
The DevOps templates are
a great starting point just to be able to take your plan,
understand all the decision points that
need to be made as you're going through them.
>> Awesome, thank you so much for your time today, Wayne.
It's been really good and useful
talking about your Cloud Adoption planning.
Thank you to everybody that's tuned in.
What we'll be doing is sharing some of those resources
that Wayne mentioned in the description box below,
so make sure you check them out and stay tuned for
future episodes of the Azure Enablement Show.
[MUSIC]