►
From YouTube: VC&C User and Buyer Personas
Description
In this video we go through the different User (https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#user-personas) and Buyer personas (https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#buyer-personas) relevant to the Version Control & Collaboration use case.
Resource page https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/version-control-collaboration/#personas
A
Oh
hello
and
welcome
to
another
short
video
about,
in
this
case,
the
user
and
by
personas
of
the
version
of
Tron
collaboration
uses
so
pretty
straightforward
user
personas
of
archetypical
statistical,
statistical
representations
of
users
of
actual
users
of
kit
lab
that
influence
the
purchasing
decision
that
comes
from
other
people.
They
don't
make
the
decision
they
at
most
they
influence
another
person
making
that
decision.
A
So
this
huge
case
is
relevant
to
several
user
personas
that
they
listed
there.
Let's
go
dive
into
the
motivations
and
problems
that
this
use
case,
source
for
them,
but
the
last
so
the
list
is
product
managers.
Dev
team
leads
software
engineers
step
ups,
engineer's
and
product
designers
in
compliance
managers.
They
are
both
both
question
marks
because,
just
after
a
few
discussions
recently,
we've
decided
to
add
them.
After
all,
product
designers,
as
we'll
see
just
later,
will
find
a
solution
to
part
of
the
problems
in
design
management
and
Design
Systems
techniques.
A
So
product
managers,
basically,
they
require
visibility
across
the
different
assets
and
the
ability
to
connect
requirements
with
integrations.
So
this
type
of
sona's
will
be
jumping
between
the
where
the
requirements
kept.
Mainly
issues
can
think
about
epics
to
for
higher
vision,
longer
term
vision,
but
mainly
issues
and
merger
quests
right
and
trying
to
match
requirements
with
actual
delivery,
handover
of
code
and
design
assets
that
match
the
requirements
voiced
in
user
stories
or
any
other
type
of
technique.
A
Def
team
leads,
who
manage
least
seen
as
leaders
among
a
group
of
engineers
will
mainly
work
with
issues
and
specifically
the
full
capability
of
of
source
code
management,
but
also
code
review
in
merge
request
right.
These
people
spend
nice
percent
of
the
time
on
an
IDE
or
na
code
development,
environment
potentially
locally.
Maybe
the
web
IDE.
A
Software
engineers
would
be
the
East
type
of
people.
That's
a
bit
more
junior
than
the
team
lead,
and
the
use
case
is
absolutely
the
same.
They
spend
most
of
their
time
in
an
integrated
development.
Environment
again
could
be
the
web
ID.
It
could
be
a
local
ID
depending
on
the
requirements
and
then
we'll
be
pushing
code,
so
they
will
to
be
taken
advantage
of
protected
branches,
merge,
request,
approval
rules,
roles
etc.
A
So
the
full-fledged
features
of
the
categories
known
as
source
code
management
and
code
review
DevOps
engineers
are
also
known
as
platform
engineers,
so
they
will
be
looking
at
the
broader
picture.
So
that's
why
this
this
use
case
resonates
with
them,
because
the
promoter
on
collaboration
is
the
refers
to
the
features
contained
in
a
specific
part
of
the
of
a
product
that
is
gate
lab.
That
is
huge.
In
fact.
It's
a
complete
devops
platform,
so
the.
A
Apart
from
this
use
case,
product
designers,
we
just
mentioned
in
the
beginning
of
the
video
they
would
like
to
have
process
in
which
there's
not
not
so
much
handle
of
designs
but
actually
hand
over
right,
a
place
in
which
they
can
discuss
changes
to
the
designs,
how
they
look
like
if
they
matter
informants
and
how
they
potentially
will
be
activated
by
the
source
code
that
will
print
them
in
a
web
site
in
a
server
or
whatever
so
design
management.
Category
is
the
type
of
category
that
appeals
and
serves
this
type
of
persona.
A
Finally,
compliance
managers:
this
is
mostly
a
requirement
from
the
vertical
from
name
from
the
enterprise
vertical.
Basically,
any
industry
and
any
player
that
works
in
a
regulated
industry
will
have
to
face
compliance
measures
for
which
traceability
and
access
to
IP
and
the
repos
is
a
fundamental
information
and
that
lives
mainly
in
the
virtual
trial
collaboration
use
case.
So
therefore,
functionality
such
as
compliance
management
and
others
appeal
to
these
type
of
person,
eventually
we'll
come
to
the
set
of
buyer
personas.
A
Thoughtful
because
remember,
the
definition
of
a
use
case
is
basically
a
set
of
problems
defined
in
you
in
in
by
a
language
to
which
buyers
attach
a
budget.
So
a
clear
intention
of
spending
money
of
solving
it
actively
and
they
are
the
buyer
personas.
Our
personas
are
the
people
who
serve
as
the
main
buyer
in
an
organization
or
a
champion
within
an
enterprise
that
drives
the
buying
conversation
and
coordinates
various
teams
to
make
the
purchase
right.
A
So
that
is
the
comprehensive
definition
and
we've
got
three
in
this
case
usually
are
grouped
in
this
type
of
organizational
chart
and
those
are
the
VP
of
death
development,
the
director
of
development
and
the
manager
of
a
development.
They
share
many
many
many
responsibilities,
but
at
the
lowest
level
you
will
have
the
object
manager,
who
has
a
big
deal
of
coding
or
software
engineering
itself,
but
with
some
business
goals,
mainly
hiring
and
so
on,
but
but
a
fair
amount
of
business
goals
to
actually
meet
on
a
higher
level.
A
So
if
you're
familiar
with
micro
services
or
monoliths
or
every
shade
of
Crete
gray
in
between
those
decisions,
basically
articulate
how
the
different
components
of
the
product
talk
to
each
other
and
different,
how
the
different
teams
actually
work
in
the
different
components
of
each
and
between
all
of
them
and
so
on,
and
those
are
very
long-term
decisions
that
have
a
lot
of
impact
in
the
business
and
that
are
subjective
changes.
Obviously
of
that
try
to
adapt
to
the
different
business
outcomes
so
so
again,
fundamental.
A
These
people
are
fundamentally
driven
by
the
repo
management
SCM
features
in
CAD
lab,
and
that's
why
they.
They
are
one
of
the
fundamental
personas
in
this
in
this
in
personas,
in
this
use
case,
and
eventually
the
VP
of
app
dev,
who
has
almost
zero
software
engineering.
Software
development
responsibilities
comes
from
that
world,
but
it's
fully
fully
fully
in
the
the
business
side
of
things.
So
someone
that
is
able
to
translate
vision
to
something
potentially.
A
Realizable
something
that
can
be
developed
in
the
shape
of
software
and-
and
that
is
the
main
goal
of
this
role-
it-
it
appeals
less
to
them
the
version
control,
our
collaboration
use
case,
but
still
being
part
of
our
products,
so
broader
skit
lab.
Like
the
example
we
mentioned
with
DevOps
engineers,
these
people
will
look
for
something
that
is
a
DevOps
tool
that
excels
at
vertical
tron
collaboration.
That's
all
thanks.