►
Description
GitLab Professional Services can help you adopt key features faster, driving business value and earning a competitive edge in the marketplace. Learn how these services can help your company achieve its ambitious goals!
A
Hi
everyone
thanks
for
joining
us.
We
are
going
to
give
people
just
another
minute
or
so
to
jump
in
and
we'll
get
started.
A
All
right,
let's
go
ahead
and
kick
it
off
thanks
everyone
for
joining
us
today.
We're
we're
excited
to
have
you
and
we're
excited
to
to
be
presenting
about
our
professional
services
offerings.
Today,
I'm
I'm
joined
by
by
the
two
presenters
brian
may:
who's,
a
senior
manager
of
professional
services
and
sean
sandoval
who's,
also
senior
manager
of
education,
services
and
michael
lutz
who
oversees
our
global
professional
services
department,
so
to
get
started
just
kind
of
wanted
to
go
through
a
couple
of
housekeeping
items.
A
B
Hey
thanks
taylor
appreciate
it
so
welcome
folks,
as
taylor
mentioned,
I'm
a
senior
manager
in
professional
services
and
we're
really
happy
to
talk
with
you
today
about
accelerating
your
time
to
value
with
git
lab
professional
services.
I'll
I'll
provide
some
some
context
on
what
you
know.
B
The
topics
we'd
like
to
talk
about,
as
it
relates
to
adopting
a
new
tool
and
consolidating
from
you
know,
point
solutions
and
then
sean,
and
I
will
both
discuss
some
services
that
that
we'd
like
to
bring
to
light
and
ensure
you
know
about
to
help
you
manage
that
transition
period
and
really
accelerate
your
your
time
to
value
with,
with
the
gitlab
platform.
B
So,
just
to
kind
of
set
the
context
most
customers
that
we
we
talk
with
are
are
in
the
process
of
maturing
their
their
devops
practice.
They've
probably
have
have
worked
with
many
point
solutions
in
the
past.
You
know
best
in
class
tools
for
things
like
agile
project
management,
source
code
management,
ci,
continuous
integration,
package
management,
security
scanning,
probably
lots
of
different
security
scanners.
I
mean
that
you
know
that's
what
we
do
right.
We
we
find
a
solution
to
a
specific
problem
and
and
that
specific
problem
is
solved
within
that
kind
of
context.
B
When
you
have
so
many
different
solutions
and
then,
furthermore,
a
lot
of
our
customers,
they
have,
they
have
different
teams
or
different
portfolios
in
their
business,
using
different
tools,
making
management
of
the
overall
value
stream
in
the
company
extremely
difficult.
So
you
know,
as
we
see
the
proliferation
of
tools
and
the
number
of
projects
increase,
we
see
the
complexity
of
managing
our
company's
devops
practice
increased
linearly,
if
not
exponentially,.
B
The
you
know,
the
number
of
tools
I
mentioned
is
kind
of
a
multiplying
factor
in
the
number
of
projects,
as
as
you
grow
from
from
a
small
to
me,
you
know
a
business
of
10
people
to
100
people
to
a
thousand
people
you're.
You
need
to
take
into
consideration
that
total
cost
of
ownership.
It's
not
just
the
license
cost
of
all
those
tools.
It's
not
just
the
the
maintenance
cost
in
terms
of
people's
salaries.
B
To
maintain
each
of
those
tools,
it's
the
inefficiencies
that
are
introduced
to
your
development
workflow
into
your
ability
to
ship
out
ideas
to
your
customers
quickly.
So
it's
really
the
the
overarching
total
cost
of
ownership
that
we
want
you
to
take
into
consideration.
B
You
know
as
you're
you're
thinking
about
the
the
longer
term
investments
you're
making
in
your
your
tools
and
the
workflows
that
are
supported
by
your
tools,
so
you
know
enter
a
gitlab
the
devops
platform.
It's
it's
a
single
platform
with
a
single
user
interface
and
a
single
data
model
that
supports
the
entire
software
development
life
cycle.
You
no
longer
have
one
tool
for
planning
and
one
tool
for
source
code
management
and
one
for
testing
and
verification,
and
then
security
happening
at
the
very
end
of
the
value
stream.
B
You
have
a
single
platform
where
all
of
these
functional
users
come
in.
You
know
the
the
business,
the
developers
security,
it
operations,
they're
all
using
the
same
tool,
they're
all
understanding
where
the
the
idea
or
the
feature
or
the
bug
is
in
the
value
stream
and
collaborating
on
that
single
platform.
B
The
the
benefits
here
are
are
really
robust.
One
of
the
the
big
themes
that
I
I've
seen
with
a
lot
of
customers
is:
they
complain
about
functional
silos.
If
you
have
multiple
tools
for
or
a
tool
for
a
specific
function
and
that
that
person
say
a
developer
is
only
using
the
source
code
tool
and
then,
two
months
later,
a
security
vulnerability
is
found
in
the
security
tool.
There
is
a
there's,
an
impedance
mismatch
right.
The
the
collaboration
doesn't
take
place
organically.
B
It's
it's
very
difficult
to
get
the
developer
to
go
into
this
the
security
tool,
or
vice
versa,
the
the
security
professional
to
come
into
the
source
code
tool
to
figure
out
where
the
vulnerability
was
introduced.
So
we
see
the
the
functional
silos
start
to
melt
away
with
the
the
single
platform
approach,
because
there's
not
that
that
switching
of
tools
and
switching
of
contexts,
it's
all
within
the
same
context
and
collaboration-
happens
really
organically.
B
So
you
know
the
the
platform
approach
is
something
we
really
believe
in,
and
we've
built
our
platform
from
day
one
with
that
that
philosophy
in
mind.
We
think
we
have
a
really
strong
solution
to
help.
You
improve
the
way
you
work
and
really
optimize
your
value
stream
to
get
ideas
into
production
faster.
B
So
at
this
point
I
want
to
take
a
quick
poll
and
I
think
taylor
is
going
to
be
sending
a
poll
out
in
zoom,
so
check
out
the
the
pull
feature.
What
are
the
biggest
challenges
that
you
have
in
adopting
a
devops
platform
right?
What
what
are
your
your
hesitancies?
Or
what
do
you
think
are
the
the
headwinds
preventing
you
from
moving
forward
or
making
this
this
change
in
the
way
that
you're
working.
B
B
Looks
like
we
have
a
slight
leader
here
too
busy
with
existing
work.
You
know
we'll
keep
keep
this
up
for
another
minute
or
two,
but
that
makes
that
makes
sense
right.
Your
your
application
teams,
your
developers,
all
of
the
people
that
are
contributing
to
to
building
your
the
value
proposition
for
your
customers
they're.
They
have
a
day
job
right.
They
they
don't
have
the
bandwidth
or
the
the
time
the
cycles
to
to
do
their
job
and
also
change
the
way
that
they
work.
That's
extremely
common
from
from
our
customer
base.
B
B
So
it
would
be
very
unlikely
that
you
have
a
person
or
a
few
people
with
this
skill
set
to
manage
this
kind
of
transition.
So
that's
that's
really
telling
right
the
and
a
great
segue
into
professional
services,
and
this
is
really
why
we
exist
right.
We're
get
lab.
Professional
services
is
here
to
ensure
we
provide
a
means
for
customers
to
accelerate
their
adoption
journey
with
gitlab.
We
believe
strongly
in
the
value
proposition
of
lab,
and
we
don't
want
you
to
get
hung
up
on.
B
You
know
the
initial
deployment
or
migration
or
enablement
that
you,
you
might
not
have
you
know,
might
have
accounted
for
when
you
were
making
your
investment
in
the
platform.
So
the
remainder
of
the
presentation
will
really
be
focusing
on
the
the
things
that
we
see
at
other
customers
and
suggestions
that
we'd
make
to
to
you
all
to
help.
You
start
thinking
about
what
what
to
expect
during
a
transition
period.
B
There's
there's
always
a
consideration
of
what
your
transition
landscape
is
you're
already
using
these
point
solutions
these
tools-
you're,
probably
using
you,
know,
jira
or
or
agile,
algebra,
or
any
of
these
planning
tools
you
might
have
bitbucket
or
github
or
subversion
for
source
code
management-
and
you
know
the
the
array
of
tools
continues
as
you
kind
of
progress
from
left
to
right
on
the
value
stream,
we
need
to
make
a
decision
on
which
tools
we'll
be
replacing
with
git
lab
and
which
ones
we'll
be
integrating
with,
because
git
lab
does
integrate
really
nicely
with
with
most
tools
within
this
this
ecosystem-
and
this
can
be
daunting
right.
B
You
might
have
dozens
of
tools
that
you
need
to
to
consider
and
you
need
to
take
into
account
your
your
business,
your
goals,
the
the
context
of
you
know
when
code
freezes
might
be
or
other
things.
B
So
it's
a
really
big
challenge
to
figure
out
what
the
right
transition
path
is
and
professional
services
can
really
help
with
this
right,
as
we
mentioned,
as
you
all
noted
in
the
poll,
skill
set
and
time
to
manage
a
transition
is,
is
forefront,
you
know
you
don't
have
the
time
or
the
people
to
do
it.
I
mean
gitlab.
B
Professional
services
can
provide
that
the
the
common
questions
that
a
customer
has
early
on
you
know
how
do
we
make
sure
that
our
gitlab
deployment
is
is
stable
and
and
ready
for
us
to
use
on
a
production
basis?
How
do
we
transition
from
all
those
tools
that
I
just
showed
in
the
previous
slide,
and
then
some
people
might
not
know
how
to
use
it
right.
It's
it's
a
new
tool.
It
has
new
concepts
and
new
features
that
older
older
point
solutions.
Don't
have
so
it's
super
important
to
ensure
that
we
have.
B
You
know
the
proper
enablement
at
the
right
stage
of
the
adoption
for
for
the
different
folks
that
are
using
gitlab
and
we'll
get
into
that
in
a
slide
here
in
a
second
and
sean's
gonna,
be
able
to
help
us
understand
in
more
detail
about
that,
so
you
know
with
with
gitlab
professional
services
or
one
of
our
our
partners.
B
You
know
we
can
help
with
these.
These
really
foundational
things
right:
implementation,
getting
your
gitlab
deployment
set
up
and
configured
properly
migrating
source
code
data,
migrating
ci,
cd
data
migrating
workflows
to
to
help
you,
you
know,
take
advantage
of
these
new
ways
of
working
these
new
collaborative
models
and
then,
probably,
most
importantly,
training
right.
If
your
folks
don't
know
how
to
use
the
the
new
platform
there's
going
to
be
disruption
further
than
what
the
you
know,
the
actual
change
is
is
calling
for.
B
You
definitely
need
to
take
into
account
what
roles
need
to
be
enabled
at
what
points
in
the
adoption
curve.
So
sean
coming
from
you
know
a
lifelong
career
in
the
education
industry.
I
wanted
to
throw
it
over
to
you
and
just
help
us
understand.
C
Yeah
thanks
brian
for
that,
for
that
introduction,
like
I
said,
training
is
as
is,
was
my
first
love?
It's
the
heart.
I
think
so
kind
of
that
that
slide.
That
was
right
before
this
that
brian
brought
up.
I
really
I
really
love
that
it
talked
about
that
expert
guidance
and
that's
what
these
services
and
training
allow
you
to
do.
Is
you
have
that
access
to
the
experts?
Those
experts
can
help
you
learn.
So
when
you're
learning
a
new
skill,
they
can
help.
C
You
apply
what
you
learned
and
that'll
help
you
perform
better
at
your
job
or
at
different
tasks
and
then,
as
you
also
you'll,
also
know
when
you
do
need
help
when
you
do
get
in
a
tight
spot,
you
know
you,
you
will
know
where
to
go
to
get
that
help,
and
so,
as
we
think
about
training,
and
we
think
about
product
training
for
to
help,
you
accelerate
your
adoption.
C
There
are
some
key
things
to
think
about
right,
because
you
know
this
is
a
a
we're
in
the
technology
space.
This
is
a
technical
product,
so
it
changed.
There's
quite
a
few
changes
quite
often
right.
So
there's
always
new
releases
new
features,
new
functionality
and
training
can
help
you
and
the
training
experts
can
help
you
stay
up
to
date
with
those
increasing
your
speed
to
efficiency,
because
you'll
know
how
to
use
that
product.
C
I
think
one
of
the
things
in
the
poll
was
about
skill
set
right
and
that
lack
of
skill
set
so
that
lack
of
skill
set
can
hamper
that
right,
like
you,
won't
want
to
get
into
the
product.
You
won't
want
to
use
that
product
because
you
don't
know
how
to
do
it,
and
so
training
will
help
you
and
increase
that
your
speed
to
efficiency.
C
You
want
to
think
about
the
timing
and
that's
something
that
we
can
help
you
with
as
well
right.
So
the
timing
is
crucial
and
so
make
sure
you
know
you
want
to
make
sure
that
you're
training
that
team
at
the
right
time
and
it
could
be
a
couple
of
different
things
right
when
you're
learning
something
new
and
meeting.
That
kind
of
that
that
that
moment
of
need
is
when
you,
maybe
you
want
to
take
training
right
at
the
right
when
you're
going
to
right
before
you're
going
to
start
to
use
the
product.
C
I've
often
found
times
too
a
really
good
time
is
a
lot
of
times.
Will
you
let
the
users
kind
of
get
in
the
product
play
in
a
sandbox
if
you
will
kind
of
get
oriented
with
how
it
works
and
then
we'll
do
training
and
that
helps
kind
of
helps
them
bring
to
the
to
the
table?
Some
different
questions,
some
thoughts.
Maybe
how
do
I
apply
this?
C
We
do
offer
instructor-led
training
and
that's
crucial
as
well.
Instructor
lad
and
hands-on
exercises.
That's
crucial,
especially
during
the
the
onboarding
phases.
You'll
go
through
real
world
scenarios,
and
you
might
want
to
think
about
too
when
you're
thinking
about
timing
when
you're
thinking
about
onboarding.
Who
are
the
folks
that
I
want
to
train
right,
so
you
might
want
to
train
those
champions.
First
right,
they're
going
to
help
you
get
started.
Those
are
the
ones
that
are.
You
know
that
they're
ready
for
this
change
they're
excited
about
this
change.
You
know
you
train
those
champions.
C
First,
those
people
can
help
support
the
larger
organization
and
the
larger
change
that's
taking
place
and
can
also
help
implement
and
professional
services,
of
course,
can
help,
help
implement
those
best
practices.
C
And
so
it's
not
just
what
we
see
internally,
but
there's
was
a
study
that
was
conducted
by
a
large
tech
services
organization
and
they
found
similar
similar
results
here.
So
what
they
found
was
is
that
users
that
are
well
trained
or
go
through
training
product
training,
68
of
them-
are
able
to
use
the
product
more
often
so
they're
comfortable
in
the
product
and
they've
practiced
in
the
product,
and
so
they
feel
like
they
can
go
to
that
product
more
often
and
get
the
tr
and
and
work
in
there.
C
56
can
use
more
features,
so
they've
learned
different
features
throughout
the
training,
so
they
know
how
to
use
those
those
features
I
think
about.
I
look
at
the
feedback
often,
and
so
one
of
my
favorite
quotes
from
a
customer
was
I
learned
all
the
things
I
didn't
know,
and
so
right
as
you
go
through
training,
there
might
be
things
that
you
know
lots
of
different
features
within
within
git
lab
or
any
technical
product
right
for
you
to
learn
the
things
that
you
did
not
know.
So
I
love
that
comment.
C
I
think
about
it.
Quite
often,
the
next
one
is
87
a
whopping
87.
They
can
work
more
independently,
so
they
call
support
less
or
they
phone
a
friend
less
often
because
they've
gone
through
the
training.
They
know
how
the
product
works
and
their
productivity
improves.
Their
satisfaction
improves
they're
happier.
They
are
more
productive
and
they're
less
frustrated.
B
Yeah
thanks
sean,
so
the
you
hinted
at
trainings
happening
at
different
times
in
the
adoption
curve.
So
I'd
like
to
take
a
second
and
just
highlight
the
adoption
curve
and
and
set
the
foundation
here
and
make
sure
everybody's
thinking
about
this.
So
as
change
is
introduced
at
any
company
or
or
you
know,
even
open
open
markets,
there's
always
there's
always
the
concept
of
innovators
and
early
adopters
and
then
the
majority
and
then
the
people
kind
of
lagging
behind.
B
So
an
example
of
a
laggard
is,
is
my
father.
He
still
uses
a
flip
phone
and
refuses
to
to
join
the
21st
century
with
smartphones.
You
know,
on
the
opposite
end
of
the
spectrum,
there
was
the
people
that
bought
the
iphone
one.
You
know
the
day
it
came
out
and
they
were
blazing
the
trail
and
they
wanted
to
be
known.
As
somebody
who
is,
you
know,
forward
thinking
and
really
you
know
maybe
even
affecting
how
the
iphone
was
developed
and
they
were
probably
providing
feedback
to
apple
early
on.
B
So
you
know
when
you're
introducing
change
at
a
company.
It
follows
a
similar
curve.
The
the
innovators
are
the
ones
who
are
really
intrinsically
motivated
to
change.
They
see
the
change
as
their
responsibility
and
those
are
the
people
to
really
work
with
in
the
beginning
right.
If
you
want
to
introduce
change,
you
need
to
find
your
innovators
and
you
can
do
that
by
asking
right
who's
who
wants
to
volunteer
for
piloting
a
new
way
of
working.
B
Your
innovators
will
naturally
raise
their
hands
and
it's
important
to
foster
the
innovators
to
be
kind
of
market
them
right.
You
know
once
they
once
they
develop
new
ways
of
working,
really
use
them.
As
the
golden
example
for
the
rest
of
the
organization,
the
early
adopters
are,
you
know,
they're,
not
they're,
not
on
the
bleeding
edge,
but
they
like
to
experiment
with
new
technology.
B
They
typically
learn
from
the
innovators
and
are
influenced
by
them.
So
if
we
can
get
these
two
first
segments
of
the
adoption
curve
on
board
with
with
the
the
change
that
we're
trying
to
introduce,
there's
a
natural
tendency
for
the
early
majority
and
the
late
majority
to
to
hop
on
board-
and
really
you
know-
build
the
on
the
momentum
that
the
early
adopters
and
innovators
have
established.
B
B
So,
as
you
think
about
the
adoption
curve,
there's
a
number
of
of
services
that
that
we,
we
should
be
considering
to
help
drive
the
different
stages
right.
If
you,
if
you
think
about
the
the
initial
stage
in
an
investment
in
a
devops
platform,
some
of
the
foundational
things
are
to
ensure
that
you
have
a
stable
platform
right.
The
best
way
to
do
that
is
to
to
move
to
gitlab.com,
because
it's
it's
managed
by
our
team
and
you
don't
have
to
worry
about
infrastructure
or
updates
or
patches,
or
you
know
anything
like
that.
B
We
have
a
service
offering
called
rapid
results
that
encapsulates
deployment,
support,
kind
of
helping
implement
the
system,
as
well
as
the
the
key
trainings
that
we
we
see
to
be
important
at
the
early
stages
of
a
customer's
adoption.
It
includes
admin
training.
B
So
your
your
platform
team
would
know
how
to
administrate
the
platform
and
go
through
the
admin
panel
and
and
all
and
troubleshooting
steps,
and
things
like
that,
as
well
as
two
additional
trainings
gitlab
basics
and
gitlab
cicd,
and
these
trainings
are
we'll
go
through
them
in
a
bit
more
detail
later.
B
B
The
the
second
column
here
you
know
now
that
we've
got
a
system
deployed
and
some
of
our
our
key
platform
team
members
enabled
on
administrating
the
system
we
want
to
find
those
innovators.
We
want
to
find
the
pilot
teams
to
experiment
with
new
ways
of
working
the
the
services
that
enable
this
here.
We
we
have
some
transformation
services
that
we
offer
that
are
really
strong
in
helping
translate,
ci
cd,
workflows
and
building
out
standardization
and
governance
around
the
the
cicd
processes
in
your
company.
So
those
are
something
to
consider.
B
Let
us
bring
a
framework
of
ci
cd
templates
to
you
so
that
you
can
benefit
from
all
of
the
you
know,
the
previous
customers
that
we
worked
with
and
and
have
this
kind
of
library
of
of
ci
cd
pipelines
that
you
can
select
from
you
know,
there's
training
in
all
these
ci
cd
training
is
usually
pretty
important
here,
because
the
key
foundation
of
a
an
efficient
value
stream
is
an
efficient,
ci
cd
framework.
B
So
we
definitely
recommend
that,
as
we
get
past
the
pilot
teams,
you
know
we're
thinking
about
getting
into
the
maybe
the
early
adopters
or
even
the
early
majority.
Before
you
start
to
to
open
the
the
platform
up
or
throttle,
you
know
the
masses
into
the
new
ways
of
working.
We
want
to
make
sure
that
they're
enabled
right.
They
need
to
have
a
foundational
understanding
and
a
working
knowledge
of
gitlab
the
platform.
B
So
we
have
these
four
trainings
that
I've
listed
here
from
that
shawn's
helped
me
collate
the
the
basics,
cicd
security
and
project
managers.
These
are
roughly
mapped
to
the
different
personas
that
we
see
at
companies.
The
basics
is
kind
of
foundational
and
can
be
for
anybody,
but
the
remaining
three
are
really
kind
of
geared
toward
the
the
functions
that
certain
people
would
do.
You
know
ci
cd
is
developers,
and
I
t
operations.
Security.
B
C
Yeah
brian,
I
would
just
I
would
you
know,
think
about
too
we
we
talked
about
before
in
the
earlier
slides
like
when
training
is
valuable.
When
should
we
take
training,
but
we
can
also
help
you
with
who
should
take
training
right
so
when
and
who
and
help
you
along
in
that
in
that
in
that
learning
journey
and
think
about
the
different
roles,
the
different
personas.
I
I
think
we
might
talk
about
that
a
little
bit
more
in
a
couple
of
slides
as
well.
B
Yeah
yeah,
thanks
for
that
sean
and-
and
it
looks
like
there's
a
question
coming
in
the
chat
about
sharing
the
links
to
the
services.
We
can
certainly
do
that.
I
will
try
to
get
to
that
or
maybe
yolanda
could
to
try
to
post
some
of
the
links
while
we're
going
through
the
rest
of
the
presentation.
B
Thanks
for
that
question,
and
then,
finally,
here
driving
adoption
to
the
majority
right,
we've
gotten
the
platform
in
place,
we've
gotten
the
the
admin
team
trained
up,
we've
gotten,
hopefully,
some
of
the
the
other
roles
in
the
organization,
understanding
how
to
use
git
lab
now
we're
ready
to
make
that
that
big
transition
right
and
we
can
do
so.
We
have
some
automated
migration
services
that
really
minimize
that
transition
period
once
we're
ready
to
switch
that
on
and
you
know,
get
get
the
applications
moved
over
to
get
lab.
B
B
If
that's
the
case,
we
do
have
a
means
of
kind
of
engaging
with
professional
services
that
we
don't
have
to
necessarily
have
that.
That
intention
defined
up
front.
We
we
call
this
a
consulting
block.
So
if
you
know
you
need
help,
if
you
know,
like
the
poll
said,
if
you
know
you
don't
have
time
to
do
it
yourself,
if
you
don't
have
the
skill
set
to
do
yourself,
and
maybe
you
don't
have
the
time
to
consider
what
exact
service
you
need
and
you
just
you
know
know
you
need
some
some
help.
B
Our
consulting
block
approach
can
help
you
here
so
we'll.
You
know
you
can
work
with
your
account
executive
to
to
add
professional
services,
consulting
blocks
to
your
license,
purchase
or
as
a
separate
purchase
after
license.
We
would,
after
the
the
consulting
block,
purchase
order
is,
is
processed.
Somebody
from
our
team
would
meet
with
you
to
determine
what
your
biggest
initiatives
are
and
then
figure
out
what
what
we
should
focus
on
with
the
with
the
time
that
you've
purchased
and
then
we
can
schedule
the
time
in
two
different
ways.
B
Maybe
you
you
just
want
expert
advice,
right
access
to
the
experts,
so
we
can
do
like
an
eight
hours
per
week
for
for
12
weeks
kind
of
engagement
to
provide
that
guidance
continuously
in
a
very
expected
format.
So
this
gives
the
customers
typically
some
flexibility
and
reduces
the
barrier
to
entry.
If
you
know
you
need
help,
and
you
don't
really
know
exactly
what
what
with
yet.
This
is
a
great
option
for
you.
B
And
then,
secondly,
we
we
do
have
sku
offerings,
so
these
are
packaged
services
that
are
very
well
defined
and
published
on
our
website
and
and
we
try
to
break
them
down,
perhaps
by
the
persona
that
might
be
interested
in
them.
So
if
you're,
if
you're
the
leader
of
the
you
know
the
platform
team
that
will
be
hosting
responsible
for
hosting
gitlab
self-managed,
rapid
results
might
be
for
you
right,
we
help
you
deploy,
get
lab
self-managed
onto
one
of
the
popular
cloud
providers.
B
The
second,
you
know,
if
you're
a
vp
of
development
you're
thinking
about
you
know
what
your
developers,
our
experience,
is
going
to
be
during
this
transition
period,
you're
probably
focused
on
migrating
data
migrating
workflows,
so
the
migration
plus
package
is
is,
you
know,
should
be
considered
there.
Think
about.
You
know
we
can
migrate
up
to
a
thousand
repositories
in.
B
You
know
two
to
three
week
time
frame
because
we
have
automation
that
that
we
can
leverage
and
help
minimize
that
transition
period,
there's
also
flexibility
in
the
there's
three
private
instructor-led
trainings
that
you
can
select
from
based
on.
You
know
your
skill
set:
maybe
you
don't
need
the
basics,
maybe
you're
beyond
that,
and
you
just
need
ci
cd
and
security,
and
things
like
that.
So
there's
some
flexibility
there
and
then.
B
Finally,
you
know
the
head
of
security
engineering
you're,
probably
not
using
a
devops
platform
today,
because
we're
you
know
in
this
new
territory
of
hosting
a
devops
platform,
so
the
security
engineers
aren't
going
to
be
familiar
with
using
a
security
dashboard
within
this
this
platform,
helping
them
understand
that
using
the
security,
essentials
training
and
even
the
gitlab
ci
cd
training
to
understand
how
the
interconnectedness
of
those
two
features
would
be
really
beneficial.
B
So
all
all
four
of
these,
these
services
are
available
as
a
skew
today,
which
really
makes
the
the
purchasing
process
very
easy
and
and
very
straightforward.
C
Yeah
brian-
and
I
think,
if
you
don't
mind,
I,
I
think
you've
done
a
kind
of
just
a
great
job
of
highlighting
what
the
different
personas
look
like
you
know.
Gitlab
is
a
is
a
large
product
right,
so
it
would
be
hard
for
just
one
person
to
learn
the
entire
system,
so
we
really
want
to.
You
know
we
help
you
kind
of
stay
focused
on
who
needs
to
learn
and
at
what
time
right?
When
we
talk
about
that
learning
journey,
what
are
the
personas?
That's
why
we
have
the
different.
B
C
Yeah
so
there's
yeah,
so
we
do
offer
a
couple
of
different
training
delivery
methods.
We
have
private
instructor-led
training
so
again,
you'll
have
access
to
the
experts
where
you
can
ask
questions,
and
you
know
in
today's
world
we
do
that
remotely,
but
we
can
also
do
it
in
person.
So
during
these
last
last
couple
of
last
few
years,
we've
gotten,
you
know,
I
think
pretty
you
know
rather
skilled
at
delivering
remotely
and
then
also,
if
you
do
want
to
go
at
your
own
pace,
you
do
have
that
option
as
well.
C
So
we
do
have
a
self-paced
e-learning
training
that
you
can
take,
and
so
both
of
those
paths
will
also
allow
you
to
to
earn
your
certification.
And
so
why
is
that
important
is
because
it
demonstrates
your
team's
proficiency
right.
It
demonstrates
that
you
and
that
your
team,
that
you
have
the
knowledge
to
solve
complicated
business
issues
or
business
problems
right
and
also
gives
you
industry
industry
recognition.
C
So
you'll
people
will
know
that.
Okay,
you
have
that
knowledge,
and
you
know
that
you
know
you
know.
You
know
git
lab
because
you
are,
you
are
industry
certified.
C
B
B
So
you
know
that
that
was
the
majority
of
what
we
really
wanted
to
talk
about.
I've
seen
a
few
questions
come
in
through
the
q,
a
so
maybe
taylor
do
you
want
to
to
chime
in
and
maybe
verbalize
a
few
of
them
on
our
participants
behind.
A
For
sure,
so
one
one
question:
I'm
seeing
here
as
a
devops
technical
lead.
What
are
the
things
I
need
to
learn
from
the
gitlab
platform
and
certifications
relevant
to
devops.
B
So
it's
probably
important
for
you
to
earn
the
the
devops
professional
certification,
which
is
sean.
You
can
talk
to
this
right.
It's
the
four.
C
Right
yeah,
we
do
have
yeah
thanks
brian,
we
do
have
a
specific
offering
offering
for
devops
professionals
devop
what
we
call
devops
fundamentals,
and
so
that
would
be
you
know,
that's
your
git
lab
with
get
basics,
your
ci
cd
and
product
management
and
security
essentials.
So
these
are
right,
so
the
the
people
that
you
might
think
about
are
you
know
your
devops
professionals,
your
developers,
release
engineers,
your
quality
assurance
team
security,
specialists
and
and
those
product
managers
as
well.
A
Great
yeah
yeah,
but
before
I
move
on
to
the
next
question,
there
are
a
couple
more
I'm
actually
going
to
launch
another
poll.
This
one
is
to
gather
feedback
for
today's
session.
Just
a
couple
of
quick
questions.
There
we'd
love
to
hear
what
you
thought
about
it
next
one.
What
approaches
do
you
see
work
best
with
consolidating
from
many
tools
to
gitlab.
B
Yeah
I
can,
I
could
probably
take
a
stab
at
this
one.
I
think
it
it
depends
on
the
customer's
situation.
There's
there's
some
approaches
that
are
are
faster
to
get
off
of
a
specific
tool.
So
I'll
give
an
example.
If,
if
you
have
a
license
renewal
for
a
product
that
you're
not
looking
to
renew
that's
six
months
from
now,
you
probably
want
to
prioritize
getting
off
of
that
tool,
so
you're
not
paying
multiple
license
fees
for
two
different
tools.
B
In
that
case,
you
know
we
we
want
to
make
sure
that
we
have
a
path
to
get
off
of
that
tool
in
probably
four
months,
so
we'd
really
want
to
facilitate
that.
If,
if
it
come,
you
know-
let's,
let's
say
it's
bitbucket
or
or
another
source
code
system,
I
would
really
position
automated
source
code
migration
a
little
bit
earlier
than
maybe
I
would,
if
that
wasn't
a
customer
constraint,
so
get
everybody
using
gitlab,
get
get
them
trained
on
how
to
use
the
source
code
features.
B
And
then
you
know
the
security
tools
and
all
of
those
things
kind
of
can
can
be
referenced
from
the
gitlab
project.
At
that
point,
on
the
converse,
if
you're,
if
you
try
to
manage
change
all
at
the
same
time,
it's
going
to
be
difficult.
So
if
you
try
to
get
rid
of
bitbucket
or
svn,
or
you
know,
name
your
sourcebook
tool
and
jenkins
and
teamcity
and
bamboo
and
your
security
tool
all
at
the
same
time,
your
your
team
members
are
going
to
be
overwhelmed
with
change.
B
So
that's
why
we
like
to
think
about
adopting
change
from
that
adoption
curve
perspective
so
that
you
you
manage
it.
You
manage
the
risk
and
you
manage
the
investment
kind
of
in
lock
step
with
each
other.
So
you
know
thinking
about
thinking
about
it
from
that
approach
is
really
the
recommendation
that
I
would
make.
A
Great
next
question
that
came
in
here:
how
do
you
help
train
or
enable
the
users
of
git
lab,
as
you
manage
the
transition
period.
C
Yup,
so
so
there's
a
couple
of
things
right
you
want
to
so
you
think
about
when
that
training
applies
right
at
what
different
stage,
and
so
brian
had
talked
about
the
different
stages
of
adoption,
but
also
where
are
you
in
your
in
your
in
in
the
different
areas
of
your
implementation
and
your
migration?
So
it's
important
to
think
about
those
things
as
you're
getting
trained
as
well.
C
So
like
we
talked
about
that
timing
could
be
right
right
as
you're
onboarding
before
you're,
going
to
start
to
use
the
product
that
timing
could
also
be
depending
on
the
users,
like,
I
said,
generally
those
you
think
about
those
champions
or
those
early
adopters
that
those
folks
that
are
on
your
team
that
are
excited
to
get
started.
C
Those
are
generally
the
first
ones
that
you
want
to
get
trained,
and
then
you
know
I
like
to
say
too,
I
like
to
give
exposure
to
to
members
of
the
team
like
let
them
play
in
a
sandbox.
Let
them
get
familiar
with
the
product
right
and
then
we
have
them
come
into
and
and
to
do
more
training.
So
maybe
that's
kind
of
you
think
about
that.
Sandbox
is
maybe
like
a
prerequisite.
C
You
know
get
familiar
play
around.
Make
mistakes,
ask
you
know,
think
about
different
questions.
How
do
I
apply
what
this
new
functionality
allows
me
to
my
job
right,
and
so
you
know
I
like
to
think
about
those
champions.
We
start
those
guys
early
and
in
the
game,
and
then
you
know
the
larger
team
or
the
rest
of
the
team.
You
know
we
give
them
a
chance
to
play
a
little
bit
in
the
sandbox
and
then
we
really
kind
of
ramp
up
their
training.
A
Next
question:
here:
how
does
get
lab
ps
work
with
customers?
Do
you
do
it
all
for
us,
or
are
we
learning
along
the
way.
B
B
B
B
But
that
said,
there
are
cases
where
we
come
in
and
do
it
for
a
customer
right
when
customers
don't
have
the
bandwidth
to
to
support
the
implementation
of
their
gitlab
self-managed
instance,
we
have
in
the
past,
done
the
deployments
for
them
the
challenge.
There,
though,
is
once
we
deploy
it.
That's
great.
B
B
We
like
the
model,
where
you're
sitting
with
us
and
learning
and
and
kind
of
doing
it
alongside,
but
we
totally
understand
when
there's
the
the
time
crunch
or
the
you
know,
other
constraints
that
that
require
us
to
do
it
on
your
behalf.
C
And
I
might
say
to
you,
brian,
that
you
know
the
the
way
that
we
structure
the
courses
is
with
those
hands-on
exercises,
those
labs,
those
real
world
scenarios
right
so
that
you
can
learn
as
get
lab
is
helping
do
and
then
you
can
apply
so
that
you
can
do.
But
then
you
also
know
when
you
do
need
help.
You
know
where
to
go.
A
Cool
one
last
question:
I'm
seeing
here
help
me
understand
what
you
mean
by
transformational
services.
B
Yeah,
so
our
our
transformational
services
are
really
focused
on
ci,
cd
and
a
lot
of
our
customers.
You
know
they
they've,
provided
us
feedback
or
provided
us
pain
points
on
their
current
approach,
where
it's
everybody's
solving
their
ci
cd
problem
slightly
differently.
There's
no
standardization!
B
If
they're
using
like
a
jenkins
type
product,
there's
plug-in
sprawl,
different
plug-in
versions
are
needed
by
different
teams.
There's
not
a
you
know
a
centralized
governance
team
responsible
for
for
all
this
and
they
want
to
get
to
that
approach.
So
our
transformational
services
are
focused
on
building
out
a
ci
cd
pipeline
template
framework,
along
with
some
container
templates
that
actually
run
the
jobs
and
it
it
helps.
Customers
achieve
that.
B
You
know
the
standardization,
the
collaboration
and
and
compliance
control
over
their
their
cicd
pipelines
across
their
business.
It's
a
bit
of
a
different
paradigm
than
like
the
jenkins
plug-in
manager.
It's
it's
all
based
on
immutable
containers
and
an
inheritance
with
with
ci
cd
pipeline
referenced
in
templates
versus
being
defined
explicitly
in
the
applications.
B
So
I
I'd
love
to
talk
about
that
more.
If
you're
interested
it's,
it's
a
really
exciting
new
concept
that
that
a
lot
of
our
customers
are
seeing
a
ton
of
benefit
in.
A
C
A
Great
well,
I'm
not
seeing
any
others
right
now.
C
A
Yeah
great
questions,
so
this
deck
is
going
to
be
shared
out.
A
So
in
any
links
that
that
were
that
were
in
this
deck-
and
we
can
add
others
if
we
want
to
will
be
shared
to
everyone
that
attended
today,
okay,
yep.
B
Yeah,
so
the
the
automation
that
that
our
professional
services
team
uses
to
migrate
from
our
most
popular
source
systems,
which
are
bitbucket
and
github
github,
primarily
we've
actually
open
cored
that
that
product
that
tool
it's
called
congregate.
B
B
B
We
do
have
documentation
on
our
both
our
import
api,
as
well
as
our
our
import
user
interface
that
customers
can
can
use
to
try
it
in
a
you
know.
The
user
interface
is
less,
it's
not
automated.
It
would
only
be
useful
for
dozens
of
projects.
The
import
api
can
be
used
if
you're
good
at
custom
scripting.
A
Awesome
well,
thank
you,
everyone
for
joining
us
today.
We
we
appreciate
you
taking
some
some
time
out
of
your
schedule,
like
I
mentioned,
we'll,
be
sending
out
the
deck
and
the
recording
and
in
the
coming
days,
so
you
can
look
for
that,
and-
and
you
can
also
keep
an
eye
out
for
for
additional
sessions
like
this
in
in
the
future
as
well
and
like
the
the
slide
here
says,
feel
free
to
get
in
touch
with
your
account
team.