►
Description
Product marketing manager Jordi reviews the SCM use case, customer journey, buyer personas, and analyst coverage as well as company resources found in the handbook.
A
Keep
this
quick
Dougherty
get
a
majority
of
the
time
here,
but
you
may
be
familiar
with
a
feature
called
gitlab
CIC
for
github
for
external
repos
and
this
feature,
which
I'll
put
a
link
in
the
chat
and
provide
John
with
them
as
well,
has
been
made
free
to
use
for
quite
some
time
now
and
also
link
the
blogs
that
that
we've
written
about
that.
And
so
this
period
is.
It
has
an
end
date.
So
there
is
officially
an
in
date
for
this
free
usage
period.
A
For
this
feature,
and
the
blog
went
out
here
today
with
additional
information
and
some
links
that
I
encourage
you
to
check
out.
So
there's
also
a
slack
thread
coming
I
left
in
slack
about
three
messages
up.
If
you
wanna
check
that
out
with
the
relevant
links
you
need,
but
just
to
be
aware
and
have
visibility
of
what's
going
on,
the
27th
of
March
will
be
the
last
day
for
this
to
be
free,
and
then
customers
or
users
rather
will
need
to
upgrade
to
a
silver
plan
or
greater.
A
D
C
Yeah
few
housekeeping
things
I'm
not
alone.
Hopefully
my
two
nephews
which
are
roaming
around
my
house
freely,
will
not
interrupt,
but
this
lizards
are
keeping
me
very
busy
today,
which
also
explains
this
face.
Property,
at
least
as
as
John
said,
need
yourself
feel
free
to
unmute
and
ask
any
question:
anytime:
are
there
in
the
document
just
as
I'm
talking
the
session?
Will
last
20
minutes
with
ten
minutes
for
questions
and
it's
basically
a
walkthrough
of
the
SDM
use
case
resource
page
yeah?
C
Hopefully
it
is
a
work
in
progress,
as
you
all
know,
in
a
very
good
fashion,
this
is
actually
the
version
one
so
I'm
happy
to
hear
your
feedback,
not
only
today,
but
hopefully
in
the
days
to
come
to
improve
it.
Your
us,
the
sales
team
and
at
Anne's
are
valuable,
invaluable,
actually
source
of
information,
the
the
actual
usage
of
the
product
and
the
knowledge
about
buyer,
personas
and
user
personas
comes
in
part
from
the
command
clan
that
you
know
filling
up
filling
in
in
in
Salesforce.
C
So
again
keep
going
with
that
because
it's
it's
it's
a
it's
a
great
it's
a
great
source
of
information
for
us.
We
also
get
information
from
UX
for
the
user.
Personas,
we'll
we'll
see
you
later
from
analysts
which
we
meet
constantly
and
we
read
the
reports,
etc.
So,
basically,
I
won't
go
to
I,
won't
go
into
the
general
context
that
explained
last
week,
unless
you
tell
me
so
about
the
use
case,
go
to
market
and
Bill
of
Materials,
which
will
eventually
cascades
to
this.
C
So
scope
management
is
one
of
our
main
use
cases,
if
not
the
main.
Alongside
CI,
it's
one
of
the
gateways
to
to
get
lab
and
one
of
our
most
successful
stages.
It's
a
bit
tricky
because
we
don't
control
all
the
product
itself.
So
this
is
the
part
that
it
lab
based
basis,
a
lot
on
top
of
git,
which
is,
as
you
all
know,
an
open
source
project
that
we
not
do
not
control
but
influence
through
our
own
engineers
and
for
the
community
itself,
in
any
case
source
code
management.
C
The
use
case
in
general
is
because
change
is
constantly
happening
in
software
products,
projects
and
teens
it.
Basically,
it
is
just
required
to
keep
to
keep
order
and
to
keep
control
and
track
of
every
change.
That's
happening
and
there's
plenty
of
changes.
I've
just
listed
a
few
of
those
that
correlate
to
the
different
stakeholders,
but
there
are
plenty
more
I
mean
it's
probably
the
tool
that
keeps
saying
any
single
project,
any
single
team
or
any
single
company
itself.
C
But
again,
we've
been
working
hard
with
UX
to
find
a
few
of
them.
That
you'll
find
here,
product
managers
usually
want
SCM
solutions
in
mobile
almost
every
day,
with
a
merge
request
pane
to
control
the
feature,
progress,
they're,
not
so
much
interested
in
in
the
commits
or
their
actual
pipeline,
for
example,
but
rather
in
the
ability
to
describe
what
they
want
and
I
manage
the
deadlines
for
this
user
persona.
C
There's
something
interesting
coming
up,
but
that
is
a
differentiator
of
our
style
explained
later,
is
that
we
are
serving
personas
such
as
PM's
designers
and
anyone
that
that
is
not
working
with
the
source
code,
because
those
personas
would
like
their
assets,
assets
which
are
not
source
code
but
designs.
Prototypes
data
pipelines
in
the
case
of
data
scientist
and
so
on
will
be
eventually
serving
all
these
personas
in
the
merge
request.
So
we
have
now
a
group
called
knowledge
group
that
is
in
charge
of
the
design
management
category
and
the
wiki
category.
C
The
design
management
category
is
already
introduced
in
features
that
allow
for
designers
to
upload
designs
for
the
group
for
the
team
to
provide
feedback
and
very
very
specific
feedback,
and
so
on.
So
we
we
are
starting
to
acknowledge
that
development
teams
are
composed
of
very
different
user
personas
and
the
source
code
management
has
to
serve
them
their
patterns
and
the
assets
they
manage.
So
this
is
going
to
be
a
clear
differentiator
for
us
in
the
future.
It
is
already
no
one
is
doing
it.
We're
in
the
very
initial
phases
of
that.
C
So
product
managers
would
benefit
from
this.
A
lot
team
leads
they're
interested
in
maximizing
maximizing
collaboration.
They
want
to
deliver
as
fast
as
possible
to
connect
to
CI
as
fluidly
as
possible,
and
they
will
are
heavy.
They
are
heavy
users
of
the
sort
of
the
SCM
solution.
The
software
development
would
be
the
main,
the
poor
user.
He
is
he
or
she
is
constantly
committing
changes
to
to
his
workstation
and
then
pushing
him
up
to
the
repo
debugging.
C
The
potential
problems
that
he
runs
into
validating
or
reviewing
snippets
of
code
or
actual
services
that
his
colleagues
or
her
colleagues
are
committing,
and
so
on.
So
we're
talking
about
the
the
actual
hardcore
user
of
of
sen.
All
right.
Finally,
DevOps
engineer,
which
I
would
argue
in
the
past
would
have
been
called
release,
manager
or
the
person
that
is
in
charge
of
of
actually
giving
the
go
ahead
of
the
release
trainings
or
putting
an
end
to
the
freeze
to
the
future
freezes,
depending
on
the
type
of
release
management.
C
Buyer
personas
are
a
bit
more
tricky
again.
This
information
comes
a
lot
from
the
command
plant.
So
thanks
a
lot
for
filling
that
in
keep
that
up,
but
it's
usually
said-
and
it's
I
think
it's
quite
a
reality.
You
probably
know
better
than
I
do
that
dev
teams,
which
are
again
most
of
the
user
sonís
here,
don't
have
a
budget
in
comparison
with
Ops
teams
which
do
have
a
budget.
So
it's
this
is
validated
by
the
idea
that
gate
is
a
free
tool
and
it's
dominate
to
the
market.
C
C
C
The
the
manager
of
the
software
engineer
and
the
team
lead,
and
the
VP
of
application
development,
which
is
a
sort
of
like
overlapping
role
but
is
more
really
related
to
the
DevOps
engineer,
would
be
the
manager
of
that
person.
Message
house
is
a
work
in
progress.
As
I
told
you,
this
is
version
1
of
this
site,
so
I'll
ping
you
and
keep
you
updated
with
with
anything
that
is
still
to
come,
which
there
are
a
few
sections,
no
meaning
analyst
coverage.
C
C
So
all
of
the
services
that
are
built
on
top
of
kit,
namely
a
blab,
github
and
big
bucket,
which
was
true
and
is
starting
not
to
be
true
precisely
because
of
the
the
new
features
were
that
we're
introducing
and
we
will
introduce
that
serve
the
other
types
of
personas
that
are
not
included
here,
but
that
the
product
teams
in
the
market
are
actually
in
need
of.
So
that's
actually
my
plan.
Oh
by
the
way,
please
ignore
this.
A
merge
request
is
coming.
There
is
no
total
impact
of
lesson.
C
Cm,
that's
a
mistake,
but
I
did
probably
as
soon
as
I
get
it
merged.
There
will
be
a
link
there
to
the
only
report
that
exists.
I
mean
there
are
reports
about
SC
they're
as
old
as
they're
very
old
doesn't
intend
to
basically
use
this.
There
is
a
report
by
IDC
that
addresses
the
total
total
addressable
market
in
a
way
of
Minden,
tries
to
measure
the
size
of
a
market,
and
so
on.
It's
not
really
interesting.
I
it
is
linked
there.
It's,
it
is
waiting
to
be
merged.
C
The
era
plan
which
is
not
developed
yet,
but
but
but
I'm
trying
to
work
with
Joyce
and
Ryan
on.
This
is
precisely
of
that.
We're
trying
to
make
sem
relevant
again
two
to
two
analysts:
how,
by
making
the
difference
by
telling
them
the
gitlab
is,
is
different
in
experience
and
functionality
to
the
other,
to
the
other
key
based
services,
which
is
now
starting
to
happen,
and
hopefully,
in
the
near
future,
we'll
make
a
dent
there,
and
hopefully
again.
C
Analysts
will
observe
this
market
again
and
consider
our
zener
in
a
good
position.
The
key
elements
of
better
use
case
would
be
the
capability,
so
what
exactly
I
mean
not
down
not
to
the
level
of
a
feature,
although
they
are
mostly
listed
here
in
each
each
of
the
capabilities,
but
actually
what
other?
What
the
demand
side
of
the
market
is
looking
for
from
an
SEM
from
the
ideal
SEM
feature
for
them.
Are
we
doing
on
time
by
the
way?
C
Seven
minutes
left?
So
we've
come
up
with
seven
capabilities.
We
are
still
discussing
this.
It
is
a
hot
topic
in
not
only
in
product
marketing
but
I'm
trying
to
involve
as
many
people
as
possible.
So
if
you
have
any
feedback
about
this
page,
please
open
annum
are
our
make
an
argument
and
push
anything
that
you
consider
is
a
an
improvement
or
because
this
is.
This
is
a
hot
topic.
C
The
the
borders
of
FCM
are
not
clear,
in
fact,
I
think
running,
informally,
an
interview
survey
with
a
few
people
from
the
industry
that
I
consider
relevant
some
of
them
programmers
and
we
I
can't
agree.
They
can't
agree
the
industry,
contrary
what
is
behind
SCA,
we
define
it
a
source
code
management.
You
will
find
a
source
control
management.
You
will
find
software
configuration
management
and
pressure
control.
Of
course
it's
not
SEM,
but
I
mean
it's
not
under
the
acronym
of
SEM,
so
so
the
borders
of
this
category
are
not
clearly
defined.
C
In
any
case,
we
have
so
far
agreed
upon
these
and
basically
well
what
appeals
to
the
the
fact
that
you
can
manage
different
types
of
architectures,
so
mano
repos,
suppose
service-oriented
architecture.
So
services
would
be
one
example
of
those
and
in
any
type
of
language,
and
most
probably
in
with
any
type
of
asset
in
it.
C
So
take
a
look
at
it
provide
feedback
we
constantly
improve
in
it
and
I'm
actually
looking
forward
to
your
to
your
feedback
on
this,
because
you
have
your
on
the
market
and
you
if
your
information
is
extremely
valuable,
top-3
differentiators
that
we've
come
with
so
again,
the
market
has
been
taken
over
by
gate,
which
is
a
distributed
version
control
system.
But
it's
not
completely
taken
over
by
kit.
In
fact,
the
the
main
competitor
outside
of
the
distributed
version
control
system
would
be
perforce,
which
is
a
centralized
control
system.
C
So
the
first
differentiator
is
actually
that
the
fact
that
gate
lab
is
based
on
top
of
a
distributed
version
control
system
which
allows
for
distributed
geographically
distributed
working
asynchronous
working.
You
don't
rely
on
a
good
connection
if
you
don't
need
it
so,
and
we
also
provide
along
with
that
feature
that
is
actually
get
based,
or
it
belongs
to
get
good
luck
flow.
C
So
if
SCM
addressed
developers
and
people
that
managed
source
code
that
reality
is
now
different,
the
reality
is
that
there
are
no
dev
teams
or
the
dev
teams
of
functional
teams
are
morphing
into
product
teams,
so
hybrid
teams
that
consists
of
engineers
or
developers,
data
scientists,
product
managers,
designers
and
there's
no
one
solution
for
those
and
those
that
is
what
we're
trying
to
achieve.
So,
although
it's
in
a
very
insipid
face,
this
is
a
already
a
key
differentiator
of
ours.
Again,
this
section
has
been
troublesome
in
a
way
because
analysts
are
partially
right.
C
There's
no
enormous,
there's
not
a
big
amount
of
huge
differences
between
especially
the
gate
based
services.
I've
got
two
minutes
more
competitive
comparison
is
coming
up
a
whole
list
of
of
use
of
peer
insights
from
Gartner,
and
you
can
use.
Most
of
them
are
obviously
related
to
the
user,
so
no
research
or
they
they
actually
validate
that
research
case
studies
again,
probably
you've
gone
through
a
few
of
them.
Goldman
Sachs
is
a
classic
here.
C
C
These
people
are
very
concerned
with
with
the
budgets,
after
all
their
public
institution
and
they
spend
the
public
money
so
so
that
is
a
huge
value
for
them,
among
other
other
benefits
that
I
encourage
you
to
read,
and
the
last
one
is
actually
the
most
interesting
one
you
probably
already
know
about
it,
but
then
commit
San
Francisco
this
this
very
year
in
January,
there
was
actually
a
full
presentation
by
the
Northwestern
Mutual
yet
meet
you
about
why
they
actually
chose
it
laughs.
They
had
a
fragmented
codebase.
They
they
were
else.
C
Did
they
what
the
problems
and
obviously
a
touche
crisis.
They
had
a
lot
of
tools
to
connect,
keep
them
updated,
the
plugins
and
so
on,
and
as
soon
as
they
installed
kid
lab
in
eight
months,
which
is
not
bad
but
better
than
me.
The
forecast
things
just
started
to
flow
so
much
better.
That's
a
video
and
I've
also
linked
the
deck.
There.
You've
got
sales
references
there
and
finally,
more
product
related
videos.
C
So
we
will
come
up
with
presentations
with
customer
tech
as
soon
as
possible
and
more
more
marketing
focused
and
sales
focus,
video
material,
but
then
again,
you'll
you'll
have
here.
You
have
here,
videos
that
are
walkthroughs
mainly
over
the
different
categories
and
groups
of
them
pattern
and
methodology.
There
again
design
management
and
they
are
obviously
I
encourage
you
to
go
through
them
because
there
they
are,
they
will
show
you
that
the
current
status
of
features
of
each
category
so
from
my
side,
nothing
else
other
than
opening
the
Q&A
question
and
receiving
your
feedback.
So.
E
C
A
F
Let
me
jump
in
Oh
quickly.
I've
had
separate
conversations
with
a
couple
of
folks
of
product
on
products
I'd
like
mark
and
others
about
the
potential
for
compliance
to
become
a
key
capability
that
if
we
introduced
compliance,
features
that
could
exist.
That
would
exist
at
ultimate.
Obviously
that
if
you
look
at
that,
that
would
be
something
that
could
apply
easily
to
source
code
management
and
create
a
selling
opportunity
to
say
hey
you're,
using
source
code
management.
F
Do
you
want
to
have
a
way
to
ensure
and
a
measure
and
to
track
compliance
from
a
policies
and
procedures?
And
you
know
controls
perspective
for
what
you
do
source
with
source
code
management?
We
don't
have
it
today,
but
when
we
do
I
think
it'll
be
a
case
where
you
will
have
the
opportunity
to
talk
about
ultimate
for
a
source
of
good
management.
C
E
F
F
Right
so
question
to
the
the
audience
on
this
call
as
you
engage
in
the
market
and
talk
to
your
customers
of
the
use
cases,
we're
seeing
source
code
management
protected,
manage
intellectual
property,
which
is
more
than
just
source
code
right.
It's
design,
it's
other
other
assets,
continuous
integration,
automating
built
how
you
automate
build
and
test
continuous
delivery.
You
know
we've
got
8
of
them
listed.
What
are
the
are
there,
others
that
you're
seeing
where
people
are
saying?
Hey
I
want
to
use
get
lab
to
do
this
specific
thing.
F
F
We
Francis
thank
you,
data
science
time
started
at
least
we
are
starting,
no
you're,
not
a
broken
record.
In
fact,
in
fact,
on
the
topic
of
data
science
coming
out
of
commit
I
I've
got
on
our
team.
Brian
glance
started
a
landing
page
for
data
science
of
solution
page
for
data
science,
and
we
are
building
out
at
least
a
I'm,
not
gonna
called
a
use
case
yet,
but
it's
a
kind
of
junior
concept
of
a
use
case
for
data
science.
So
we
can
capture
start
to
capture
it.
D
G
Yes,
John:
this
is
a
link
in
the
public
sector,
especially
the
Navy.
We
get
a
lot
of
requests
to
essentially
wrap
all
of
it
together,
which
is
tie
the
requirement
to
the
deployment
to
the
test
scripts
that
were
successful
so
that,
ultimately,
we
can
produce
a
report
that
says:
look
we
did
the
full
job
from
in,
so
the
lack
of
kind
of
reporting
capability
and
tying
it
all
together
is
where
we
see
kind
of
the.
We
really
wish
that
you
guys
would
do
this.
F
F
H
Not
a
question,
but
just
another
piece
of
feedback
is
the
question
that
Simon
asked
around
how
this
use
case
plays
out
in
the
higher
tiers.
I
think
would
be
a
useful
thing
to
be
a
standard
component
of
all
the
use
cases.
It
would
be
really
great
to
be
able
to
say
for
any
given
use
case.
Here's
what
you
get
I,
don't
care
about
starter,
but
here's
what
you
get
a
premium,
here's,
what
you
get
at
ultimate!
Here's
the
value
of
the
higher
tier
for
this
particular
use
case
super
valuable.