- [Instructor] At the intersection of DevOps values
and massive scale,
sharing, the S in CAMS, is key.
Scale by starting with a showcase you can replicate.
Pick a showcase area to start with,
and build an initial core competency.
Start small and grow.
Use a lean approach and pick apps and tools
to start optimizing by value-stream mapping
from the top down,
and then leveraging practices discovered
from the bottom up.
You'll have to make sure each new initiative
builds on this successful showcase
and has repeatability and quality.
Otherwise, you'll have a lot
of little entrepreneurial experiments
that don't add up and don't scale.
The right place to start is the build pipeline,
to rally around the pipeline
and do scrappy little projects on it.
For example, this iteration
we might work on security checks.
Next, we might work on governing standards,
and later, minimal and exceptional practices.
The DevOps principle that matters most
at enterprise scale is systems thinking.
Everyone in the organization should understand
how local optimizations
can deoptimize the system as a whole,
like one machiner on an assembly line running too fast,
building up inventory you have to work around,
and that it is essential to make this visible
where it's happening in the system
to harness energy for improvement.
Value-stream mapping is a lean management method
for analyzing the current state
and designing a future state
for a series of events to take a product or service
from its very beginning through to the customer.
At Toyota,
it's known as material and information flow mapping.
So, pick a work flow or a build pipeline
and use value-stream mapping
to highlight overall system deoptimizations
that can be remedied by improvement,
and start working those improvements in priority order.
At the intersection of DevOps methods and massive scale,
we should know that the lean method of value-stream mapping
also may be your greatest ally,
as it highlights bottlenecks and waits in the system
you can root out,
and it applies equally as well to the legacy
and cloud platform work loads.
I know I'm recommending value-stream mapping a lot,
but that's because it works.
You must have insight into how value flows
in order to remove or reduce barriers
and to add or amplify enablers to flow.
One thing to do here is to apply value-stream mapping
to a build pipeline.
To get a feel for what this might look like,
if you're unfamiliar,
have a look at gocd.org.
At the intersection of DevOps practices and massive scale,
Incident Command System, or ICS, is a no-brainer
because ICS provides a method
of scaling self-similar, self-organizing teams
for responding to major incidents and disasters,
and was born out of the need, when fighting wildfires,
to be able to scale up quickly
and scale down quickly
with clear patterns for communication coordination.
So, definitely consider implementing ICS
for major incident handling
and IT service continuity management for disasters.
A tool chain made up of tools that can be interconnected
via APIs can certainly help with massive scale,
because it enables ChatOps.
ChatOps is where you have
automation assisted conversations and action,
and it's part of a support model
that drives a community collaborative approach to things.
Contrast this
with working largely within a ticketing system.
DevOps wants you to collaborate,
and this is reflected in your tooling.
ChatOps brings your tools into your conversations,
and using a chat bot
modified to work with key plug-ins and scripts
to automate tasks and collaborate,
working better, cheaper, and faster.
ChatOps simultaneously enables team orchestration
and reduces the need for it over time,
so it's ideally suited to helping
with issues of massive scale.
So, one thing to do here is have an awareness campaign
about ChatOps,
so people understand why they should care about it,
and to start teaching people the skills they need
before they need them.
Then find the showcase team and setting to try ChatOps.