►
Description
Host: Karl Cardenas
The benefits of DevOps come with a steep learning curve. At State Farm, we believe that in order to successfully transform and create a DevOps culture, we have to embrace the community model—the promotion of (and reliance on) knowledge sharing for both failures and successes, so that teams may learn from the past in order to succeed at scale.
The community model prevents unnecessary waste, enables architecture and code reuse, and allows teams to share best practices. It also enables cultural change. In this presentation we will articulate the community model, share our lessons learned with three years experience operating within it, and explain why and how other organizations should embrace it.
Get in touch with Sales: http://bit.ly/2IygR7z
B
Why
should
your
organization
embrace
the
community
model
well
for
us,
the
state
farm?
It
actually
has
a
lot
to
do
with
common
themes
and
challenges
we
recur.
We
were
seeing
on
a
daily
basis.
If
you
take
the
first
statement
here
on
the
screen,
we
all
want
a
knowledgeable
workforce
that
is
able
to
consume
new
technologies.
B
B
We
always
hear
about
people
wanting
more
opportunities
and
the
ability
to
develop,
and
then
my
favorite
is,
do
you
work
on
backlog
items
or
you
try
to
tackle
new
issues
and
it
doesn't
end
there.
Most
of
us
are
in
a
small
team
dealing
with
a
much
larger
consumer
base,
specifically
if
you're
like
in
the
platform,
enablement
team,
there's
always
a
strong
demand
for
technical
questions.
B
There's
a
lot
of
upscaling
and
technical
education
needed
for
a
lot
of
workforces,
such
as
devops
and
cloud-native
principles.
So,
overall,
there's
just
a
big
need
for
shared
knowledge
and
lessons
learned
across
the
scale.
Well,
like
everyone
else,
state
farm
is
also
encountering
these
challenges,
but
we're
taking
a
different
approach,
we're
leveraging
the
community
model.
So
today
I
want
to
talk
about
the
community
model
and
share
with
you
how
it's
helping
us
tackling
these
issues
and
how
it
could
help
you.
B
So
my
name
is
carl
cardenas,
I'm
an
architecture
manager
for
state
farm,
I'm
responsible
for
public
cloud
architecture,
but
also
our
developer
evangelist
activities
for
our
public
cloud
platforms.
Look
a
little
bit
information
about
state
farm,
we're
one
of
the
largest
insurance
companies
in
the
u.s.
We've
been
the
number
one
auto
insurance
since
1942,
and
we
have
over
84
million
policies
in
effect
in
the
us.
B
Now
I
bring
these
numbers
up
not
to
boast
or
to
showcase,
but
really
to
drive
two
points.
One
is
that
the
competition
is
fierce
and
they
would
love
for
me
to
not
be
able
to
make
the
first
statement.
The
second
one
is
scale
scale
is
something
that
we're
always
dealing
with
here
at
state
farm.
It's
a
very
common
challenge,
not
only
in
terms
of
technical
infrastructure,
but
also
when
it
comes
to
workforce
and
scaling
knowledge
across
the
board,
so
traditionally
state
farm.
B
B
So
today,
when
I
use
the
term
customers,
I'm
mainly
talking
about
our
internal
customers
such
as
our
developers
and
engineers,
that's
really
who
I'm
talking
about.
So
in
our
platform,
enablement
team,
we
have
a
few
functions,
but
one
of
the
ones
that
I'm
going
to
talk
about
today
is
our
community
experience
team,
which
is
where
our
developer
evangelists
are
on.
B
So
you
heard
me
mention
the
community
model,
but
what
does
that
really
mean?
So
I
want
to
take
a
moment
just
to
read
our
definition
of
it.
The
promotion
of
and
reliance
on
knowledge
sharing
for
both
failures
and
successes,
so
that
teams
may
learn
from
the
past
in
order
to
succeed
at
scale
and
technical
endeavors.
So
what
does
that
really
mean?
Well,
it's
just
a
fancy
way
of
saying
that
we
believe
that,
for
an
organization
of
our
size
in
order
to
be
successful
in
public
cloud,
we
believe
we
have
to
work
with
one
another
share.
B
So,
let's
talk
about
the
first
one
customer
service,
most
teams
are
often
set
up
in
what
I
call
the
one-to-many
model,
meaning
that
your
team
either
enables
a
capability
and
people
come
to
you
for
solutions
or
questions.
We
see
that
quite
a
bit
in
infrastructure
platform,
enablement
teams
such
as
the
one
that
my
team
is
responsible
for
there
are
challenges
with
this
oftentimes
bottlenecks,
because
this
is
not
a
scalable
model.
So
if
a
lot
of
people
are
coming
to
you
for
questions
chances,
are
you
can't
get
to
all
the
questions
at
the
right
time?
B
B
Something
else
that
we're
also
doing
is
that
we
believe
in
feedback
from
our
consumers.
So
we
have
something
called
cloud
paints
and
it's
nothing
more
than
a
gitlab
issue,
but
our
platform,
consumers
can
enable,
can
open
up
a
gitlab
issue
and
address
a
pain
point.
So
what
we'll
do?
As
a
team,
is
that
we'll
review
that
pain
point
and
discuss
it?
How
should
we
tackle
it?
Do
we
backlog
it?
Do
we
prioritize
it?
B
This
is
something
we
can
work
on
right
now
and
then
we'll
comment
back
and
engage
with
discussion
with
our
community,
but
it's
just
a
good
way
for
us
to
stay
transparent
and
for
our
platform.
Consumers
to
let
us
know
what
is
painful,
but
also
help
set
direction
for
platform,
and
that
really
helps
them
feel
like
they
have
a
voice
in
the
game
or
in
the
platform,
and
that
always
enhances
customer
service
experience.
B
Let's
talk
about
education
and
growth,
I
group
these
two
together
because
they
really
go
hand
in
hand.
So
on
the
screen,
I
have
three
cogs,
technical
and
non-technical.
We
need
technical
and
non-technical
skills
to
be
successful.
I.T
professionals
and
growing
our
technical
and
non-technical
skills
helped
grow
our
confidence
and
when
we're
confident
we're
able
to
solve
challenges,
we're
able
to
learn
new
technologies
and
just
overall
our
chance
of
success,
just
increases
tremendously.
B
B
B
So
this
is
a
technical
forum
where
we
actually
focus
on
presenting
technical
solutions
and
the
material
is
usually
200
level
and
above
if
you
want
to
compare
it
to
college
courses
in
terms
of
difficulty,
but
it's
just
a
great
avenue
for
our
engineers
and
developers
to
present
on
how
they
solve
problems
and
what
they
did
to
overcome
them
and
share
lessons
learned
or
failures
across
the
board,
so
that
people
can
learn
from
it.
So
that
helps
build
their
technical
skills,
presentation
skills.
B
B
They
usually
come
in
the
flavor
of
technical
or
non-technical,
and
we
use
these
to
get
our
people
excited
about
learning
new
things,
but
also
to
highlight
some
of
their
achievements
when
they
learn
something
and
do
something
cool,
so
that
also
helps
develop
their
technical
skills
depending
on,
if
it's
a
technical
challenge,
but
also
non-technical,
when
we
make
them
search
for
scavenger
hunts
per
se
or
public
cloud,
quizzes
and
so
forth.
But
we
see
technical
writing,
we
see
relationship
building
and
we
see
other
other
good
traits
get
developed
with
our
monthly
challenges.
B
So
those
are
just
some
of
the
few
ways
that
we're
focusing
on
education
and
growth,
but
that
takes
us
into
opportunities.
It
really
all
starts
with
the
local
challenges
you
experience.
When
you
get
started
on
public
cloud
environments,
it's
so
much
different
than
what
organizations
have
done
in
the
past,
so
it
really
starts
out
with
the
local
challenges.
You
first
got
to
develop
the
technical
skills
and
the
non-technical
skills
to
solve
those
challenges,
and
usually
when
you
saw
them,
you
tend
to
get
confidence.
B
So
what
we
do
with
the
community
events
is
that
it's
essentially
a
platform
for
people
to
showcase
how
they
solve
those
challenges
and
also
for
them
to
get
some
attention
and
for
others,
to
see
the
great
work
that
they
do.
Eventually,
we
see
that
as
people
solve
more
challenges
and
share
out
with
community
that
they
become
community
leaders
such
as
the
community
champions
that
I
mentioned
earlier
and
what's
actually
really
amazing,
is
that
the
community
champions
that
we
have,
we
see
them
go,
do
bigger
and
better
things
we've
seen
them
go
into
formal
leadership.
B
We've
seen
them
go
into
technical
leadership,
and
that's
really
not
surprising,
because
a
lot
of
the
positive
traits
that
we
want
in
our
leaders,
they
were
already
displaying
the
community
when
there
was
when
it
was
all
volunteer
based.
So
it's
no
surprise
for
us
to
see
our
community
champions
grow
and
do
bigger
better
things,
but
it's
just
a
good
way
that
the
community
model
can
help
get
people
the
positive
attention,
help
them
and
further
their
career.
B
So
that's
the
community
model
at
a
high
level,
but
I
want
to
talk
about
how
we
got
to
where
we
are
today
we're
just
getting
started
on
our
third
year
using
the
community.
So
I
kind
of
want
to
walk
you
through
our
journey.
So
in
our
first
year
it
really
started
with
the
synchronous
communication
channel
using
rocket
chat
and
again
at
first
it
was
really
just
our
team.
It
was
less
than
four
analysts
just
answering
question,
but
throughout
time
a
lot
of
other
people
start
helping
out
to
the
point.
B
Now
today
that
oftentimes,
it's
not
my
team,
answering
the
question.
It's
other
people
in
the
community
answering
them,
and
that's
great
because,
like
I
mentioned
earlier,
that
helps
improve
the
customer
service.
But
the
reality
is
that
when
you
are
supporting
a
public
cloud
platform
or
several
of
them,
there's
just
so
many
services
to
know
about,
and
our
small
team,
don't
necessarily
have
that
expertise
but
other
in
the
community
do
so
it's
been
really
beneficial
for
us
and
to
them
to
have
each
other
help
each
other
out.
B
Something
else
we
created
the
first
year
was
a
cookbook.
So
this
is
like
a
technical,
cookbook
wiki,
where
we
share
out
knowledge
and
the
first
one
we
created
was
a
cookbook
related
to
infrastructure's
code.
It's
leveraging
a
gitlab
page
with
a
static
site
framework
and
anyone
can
contribute
to
it.
Originally,
it
was
just
us
sharing
tips
on
how
to
do
infrastructure's
code
how
to
get
started,
and
today
we
see
people
contribute
to
it
and
it's
nice
to
see
the
community
contribute
back
to
the
content
as
they
get
more
confidence
and
grow
their
skills.
B
We
also
started
aggregating
a
lot
of
the
community
resources
that
others
have
developed.
So
here
you
have
a
picture
of
a
gitlab
group
that
we
have
aggregated
a
lot
of
our
community
resources
and
you
see
stuff
like
docker
images,
lambda
layers,
community
tools,
you
name
it,
so
it's
just
a
good
place
for
us
to
help
give
back
to
community,
but
also
for
others
to
find
content
that
others
have
created.
B
B
We'll
put
him
on
blast
in
all
of
our
internal
channels,
so
everyone
can
know
who
the
builder
of
the
month
is
and
we'll
give
him
a
small
small
little
monetary
award.
But
the
point
is
to
reinforce
that
positive
behavior
and
highlight
those
people
that
are
doing
the
right
things
and
helping
the
community
out
and
then,
of
course,
the
study
group.
The
study
group
has
been
an
amazing
story
for
us
here
at
state
farm.
B
Without
it,
we
wouldn't,
we
wouldn't
have
been
unable
to
scale
out
cloud
knowledge
as
fast
as
we
have,
and
that's
very
powerful,
because
our
leadership
never
made
a
mandate.
You
have
to
get
certifications,
people
been
doing
this
on
their
own
and
they've
been
motivating
one
another
and
that's
the
power
of
community
you're
able
to
motivate
at
scale.
So
here
you
have
some
of
the
stickers
that
we
created
for
the
study
group.
People
love
stickers.
So,
let's
jump
into
our
second
year,
our
second
years,
where
things
really
started
to
change.
B
That's
when
we
stood
up
a
community
experience
team.
This
team
is
reports
to
me,
and
this
is
where
we
have
dedicated
developer
evangelists.
I
have
two
of
them
on
the
team
and
their
main
focus
is
to
strengthen
the
community,
come
up
with
events,
think
of
ways
to
help
them
out,
create
feed,
gather
feedback,
create
content
to
help
them
out
whether
it
be
technical
solutions
or
non-technical,
and
because
of
them
we
have
a
lot
more
community
events,
but
our
community
has
also
gotten
stronger.
B
So
on
this
slide,
I
am
just
going
to
talk
about
some
of
the
few
events
that
came
out
of
the
second
year
once
we
stood
up
that
team,
but
there
are
far
more
so
community
champions.
What
I
mentioned
earlier,
that's
something
that
we
kicked
off
because
of
the
community
experience
team.
We
were
able
to
identify
those
long-term
contributors
and
champions
of
everyone
in
the
community.
B
B
So
what
we'll
do
at
the
summit
is
that
we'll
focus
on
one
of
the
geographical
locations
and
it's
sort
of
like
a
mini
internal
conference,
so
we'll
spend
two
days
there
and
we'll
create
various
presentations
of
various
tracks
and
our
platform.
Consumers
will
also
present
shared
tips
and
tricks,
but
it
serves
two
purposes
one.
It
lets
us
build
a
greater
report
with
our
platform
consumers,
but
it
also
enables
relationship
building
between
the
product
teams,
state
farm,
we're
very
large
organizations.
B
The
chances
are
of
everyone
knowing
one
another,
is
sometimes
very
slim,
but
with
these
community
events
not
only
are
people
learning,
but
they
also
get
the
opportunity
to
interact
with
other
product
teams
and
build
relationships.
So
it's
just
a
good
way
for
us
to
strengthen
the
community
community
challenges.
These
are
monthly
challenges
that
I
mentioned.
B
We
use
these
to
help
our
community.
So
what
I
have
here
on
the
screen
is
an
open
source
project
that
one
of
our
engineers
created
and
it
solved
one
of
the
common
pain
points
we
heard
from
our
community
that
keeping
up
with
all
the
announcements
that
our
cloud
providers
are
announcing
on
a
regular
basis
can
be
overwhelming.
So
what
this
solution
does
is
that
it
aggregates
the
past
announcements
in
the
past
24
hour
and
injects
it
into
our
rocket
chat
channel,
but
it
integrates
with
other
popular
synchronous
channels
and
email
and
whatnot.
B
B
Something
else
that
came
out
of
our
community
challenges
was
in
was
a
life
cycle
decision,
calculator
for
storage,
buckets
and
that's
just
a
handy
tool
for
help.
People
understand
what
is
the
cost
related
to
bucket
based
on
object,
sizes,
number
of
objects
and
the
implication
of
different
lifecycle
policies.
Again,
it's
just
another
neat
tool
that
a
community
has
created
for
one
another
because
of
the
community
challenges
I'll
talk
a
little
bit
more
about
the
community
challenges,
but
it's
just
a
really
neat
way
for
us
to
get
the
community
excited
and
help
itself
back
cloud
pains.
B
B
Again
we
have
a
healthy
backlog
when
it
comes
to
the
guild
and
that's
really
exciting,
because
we
see
some
of
the
greatest
content
come
out
of
there,
such
as
how
do
you
do
local
testing
when
you're
interacting
with
cloud
services?
How
do
you
do
mocking?
What's
the
best
way
to
set
serverless
all
these
different
things
are
coming
out
of
the
guild,
and
here
you
can
see
the
gitlab
label
for
that
we
use
for
people
to
sign
up
or
open
up
a
cloud
pane.
B
So
I
want
to
take
a
moment
and
talk
about
the
public
cloud
cli
and
I
think
this
example
will
help
reinforce
the
power
of
the
community.
So
we
got
a
cloud
paint,
my
team,
the
platform,
enablement
team.
We
got
a
cloud
pane
from
our
community
saying
that
hey
getting
all
these
tools
installed
for
public
cloud
environments
is
a
challenge
I
have
to
install
the
cli.
I
have
to
install
this
and
it's
a
challenge,
whether
I'm
on
windows
or
a
mac.
Can
you
guys
help
make
it
easier?
B
So
we
took
that
challenge
and
we
started
discussing
it
as
a
team
and
we
faced
the
typical
question.
Well,
do
we
work
on
this
right
now
or
do
we
backlog
it,
and
then
we
ask
ourselves
what
if
we,
why
don't
we
have
the
community
try
to
solve
it?
So
that's
what
we
did.
We
opened
up
a
community
challenge
and
we
asked
the
community
hey.
B
Can
you
guys
come
up
with
a
solution
and
the
community
responded
and
we
had
a
few
submissions
and
the
winning
submission
was
what
we
call
the
public
cloud
cli,
and
this
is
a
golang
cli
that
is
able
to
pull
down
the
most
commonly
used
public
cloud
provider
tools
that
we
need
here
at
state
farm
in
just
a
single
command.
It
installs
it
on
your
workstation.
It
pulls
down
the
latest
version.
All
you
do
is
issue
one
command.
It
simplified
and
removed
that
pain,
point
and
the
community
loved
it.
But
that's
not
where
the
story
ends.
B
The
community
keeps
investing
in
it
and
time
again
we
see
the
community
adding
new
bells
and
whistles
to
it
that
open
source
project.
I
mentioned
earlier
that
our
engineer
created
to
pull
down
the
latest
public
cloud
news
that
I
got
added
to
that
cli
up
until
the
point
to
today
we're
on
public
cloud
cli
version
1.20.0.
B
What
I'm
trying
to
get
out
of
this
story
is
that
we
didn't
have
the
bandwidth
or
the
time
to
address
the
pain
point,
but
our
community
did.
We
simply
gave
the
community
an
opportunity
to
solve
their
own
pain.
Point
and
they
did
and
that's
the
power
of
having
a
community,
they
can
truly
help
you
out.
B
B
If
I
start
with
the
first
one,
having
a
community
team
is
probably
the
best
decision
you
can
make,
having
someone
dedicated
to
take
care
of
your
community
and
give
the
care
and
attention
and
create
multiple
events
will
help
strengthen
your
community.
Something
to
keep
in
mind,
though,
as
your
community
grows
and
you
create
more
events.
B
Your
developer,
evangelists
or
slash
advocates
will
have
a
need
to
have
someone
help
them
with
creating
events
and
coordinating
such
as
a
community
manager,
and
the
reason
is
because
that
start
taking
up
a
lot
of
time
and
takes
away
from
their
time
on
focusing
on
creating
content
or
job
aids
or
gathering
feedback.
So
just
keep
that
in
mind
the
community
challenges.
B
B
B
Study
group
has
been
an
amazing
success
story
and
we've
been
able
to
scale
out
public
cloud
knowledge
across
the
board
very
rapidly,
because
people
been
motivated
and
wanting
to
do
it
on
their
own,
but
something
to
keep
in
mind,
though,
if
you
create
something
like
a
study
group
and
it
scales
out
to
the
point
of
past
500,
you're
gonna
need
someone
to
help,
keep
it
up,
sustain
it,
coordinate
events
and
schedule,
presentations
so
same
as
the
community
experience
team.
You
will
see
that
need,
as
you
scale
out
the
public
cloud
guild.
B
This
is
that
technical
forum,
where
people
can
present
highly
technical
topics
and
show
everyone
how
they
solve
pain,
points
or
design
on
architecture.
This
has
been
awesome.
My
only
wish
and
recommendation
for
you
is
to
get
something
like
this
started
way
sooner
leadership,
this
one's
important.
We
wouldn't
be
able
to
do
everything
that
we're
doing
today,
if
it
really
wasn't
for
support
of
our
leadership,
and
we've
been
fortunate
here
at
state
farm,
that
our
highest
level
of
organizational
leadership
has
supported
us
and
that
takes
leadership.
B
Courage
to
try
something
different,
because
what
we're
doing
is
not
always
that
common.
But
I
want
to
borrow
another
term
from
a
term
that
my
colleague
usually
says,
and
that's
leadership,
stamina
and
that's
actually
being
able
to
stick
to
a
decision
that
you
don't
necessarily
know
if
it's
gonna
pan
out
like
the
community
we're
going
into
our
third
year.
But
when
we
started
we
didn't
know
if
this
is
gonna
work.
B
So
something
to
keep
in
mind,
though,
although
you
have
leadership,
support
it's
difficult
to
calculate
the
roi
of
a
community
success
stories
like
the
public
cloud
cli.
They
really
help,
explain
and
articulate
the
power
of
a
community.
But
if
you
have
leadership,
that's
always
looking
for
metrics
just
understand
that
you're
going
to
have
some
education
on
your
hand
to
provide
them
because
it's
difficult
to
gather
metrics
for
communities.
B
So
let's
talk
about
some
takeaways.
My
intention
today
is
to
not
make
it
look
like
creating
a
community
is
easy.
That
is
the
last
thing.
I
want
you
to
think
it's
actually
a
lot
of
hard
work.
It's
taken
us
three
years
to
even
get
to
the
point
where
we
are
today
and
I
still
don't
think
we're
done
yet
we're
always
investing
in
it
and
I
like
to
compare
it.
Compare
our
community
to
a
young
tree
growing,
it's
it's
fragile,
but
it
has
the
potential
to
blossom
into
a
powerful
tree.
B
So
your
community
needs
a
lot
of
care
and
attention,
and
at
the
beginning
it's
going
to
be
tough
a
lot
of
times
you
you're
going
to
be
the
only
one
doing
it,
and
you
might
even
doubt
yourself
and
ask:
is
this
really
worth
it?
But
I
promise
you
stick
it
through
keep
the
long-term
perspective
in
mind,
because
it
is
a
long-term
game
and
you
will
see
that
some
of
the
results
are
amazing.
B
B
So
if
we
go
back
to
our
problem
statements
at
the
beginning,
we're
all
looking
for
a
knowledgeable
workforce
to
scale
skills
across
and
knowledge
across
across
the
board.
How
do
you
do
that?
Well,
we're
doing
that
with
the
study
group
and
we're
doing
that
with
the
public
cloud
guild,
we're
doing
that
with
community
challenges,
just
to
mention
a
few
customer
service.
How
do
you
improve
customer
service
for
your
internal
customers,
potentially
air
externals?
B
B
Well,
that's
what
every
community
event
is
intended
for
to
give
them
the
opportunity
to
develop
whether
it's
technical
or
non-technical,
but
also
help
further
their
own
self-confidence,
because
a
lot
of
times
getting
started
on
these
public
cloud
environments
can
be
intimidating
so
having
a
community
to
help
you
and
support.
You
goes
a
long
way.
B
My
favorite!
Do
you
work
on
backlog
or
do
you
work
on
new
features?
Why
not
both
that's
what
we
try
to
do
with
the
community
challenges?
You
saw
what
we
did
with
the
public
cloud
cli
and
that's
been
super
powerful,
so
the
theme
of
today
is
you
belong
here
and
that's
what
we're
trying
to
do
with
the
community
model?
We're
trying
to
get
our
community
to
to
feel
that
they
have
ownership
and
a
platform
and
that
we
truly
value
the
feedback,
because
we
do.
B
We
have
essentially
just
internalize
the
open
source
model
and
just
add
some
bells
and
whistles.
What's
awesome
about
the
community
model
is
that
it
doesn't
conflict
with
devops
practices
or
the
product
model.
If
anything,
it
supports
it
and
emphasizes
it,
because
the
teams
that
are
successful
in
public
cloud
environments
are
the
ones
that
embraces
devops
and
those
cloud-native
principles,
and
it
just
helps
set
a
good
example
across
the
across
the
workforce.
B
We've
seen
great
results
with
the
community
model
and
we
believe
that
it
can
help
a
lot
of
organizations
as
much
as
it
helped
us
so
I'll
leave
you
with
this
question.
Seeing
how
fast
technology
is
evolving,
all
the
new
things
you
need
to
learn
and
how
fierce
the
competition
is.
Can
you
afford
to
not
leverage
the
community
model
and
all
of
its
benefits?