►
From YouTube: Positioning of Verify and Product Groups Visions
A
Hi,
I'm
jackie
porter,
I'm
the
group
manager
of
verify
I'm
joined
here
with
parker
ennis,
who
is
the
product
marketing
manager
over
ci
cd
here
at
get
lab,
and
we
are
here
to
discuss
the
positioning
and
marketing
for
the
whole
ops
section
really,
as
we
start
to
think
about
fiscal
year,
22.
well,
to
kick
off
I'd
like
to
give
an
introduction
of
what
this
presentation
will
be
over.
We'll
give
a
brief
overview
of
what
the
op
section
is.
A
If
you
have
any
questions
about
internally,
we
have
all
these
different
slack
channels,
so
please
reach
out
to
us
we're.
Definitely
here
to
help
you
out
this
particular
session
is
about
the
s
verify
stage
so
to
dive
on
in
it's
composed
of
the
continuous
integration
team,
which
is
made
up
of
the
continuous
integration
and
merge
trains
categories
the
pipeline
authoring
group,
which
is
made
up
of
the
pipeline
authoring
category.
A
I
wanted
to
also
give
a
give
an
overview
of
the
teams
and
who
owns
them.
Sometimes,
in
this
asynchronous
environment,
you
don't
get
an
opportunity
to
meet
face-to-face
with
people,
so
I
wanted
to
give
a
little
snapshot
of
who
these
teams
are
and
who
leads
them.
So
the
continuous
integration
team
is
led
by
tao
from
the
product
management
side.
She
pairs
with
vitica
on
the
design
side
and
cheryl
and
sam
on
the
engineering
management
side.
A
On
the
pipeline
authoring
team,
we
have
dove
and
nadia
partnering
together
from
product
management
and
design,
as
well
as
cheryl
and
sam
on
the
engineering
management
team
for
runner.
We
have
darren
and
hayanna
partnering
closely
together
to
ensure
our
users
and
design
experience
is
high
quality
and
elliott,
championing
our
engineering
management
experience
and
then,
on
the
testing
front,
we
have
james
heinberg,
leading
the
project,
management,
design
and
product
management,
vision
and
hayana,
leading
our
design
experience
with
ricky
leading
our
engineering
team
forward.
A
A
A
We
also
have
some
great
highlights.
Of
course,
two
of
our
more
upvoted
issues
were
implemented
recently
in
fiscal
year.
21.
we've
also
seen
some
great
engagement
on
dag
from
the
needs
functionality.
We
are
investigating
ways
to
improve,
given
that
in
this
chart
you
can
see
it's
one
of
those
functionalities
that
has
some
of
the
biggest
challenges
related
to
it.
A
So
please
engage
on
that
issue
if
you're,
if
you're
also
one
of
those
users
that's
facing
those
challenges
or
your
customers,
are
testing
has
received
lots
of
feedback
on
finding
ways
to
increase
and
enforce
test
coverage
in
their
project.
So
you'll
start
seeing
more
of
that
in
fiscal
year
22
and
then.
Lastly,
we've
announced
some
new
pricing
tiers
in
fiscal
year
21,
so
we'll
start
to
see
some
customers
engage
in
that
differently.
A
B
B
B
It's
going
to
be
a
crucial
part.
You
know,
as
we
continue
to
to
deliver
software
and
applications.
Cloud
native
is
going
to
be
playing
a
bigger,
bigger
role,
intelligent
automation
I
like
to
think
of
it
as
smart
automation
or
sometimes
like
smart
ci.
Cd,
obviously
directly
relates
to
to
be
able
to
have
speedy,
reliable
pipelines
as
well.
B
So
when
we're
listening
to
the
market,
we're
looking
at
these
themes,
it's
also
important
to
understand.
You
know
the
role
that
verify
plays
and-
and
I
think
it's
it's
really
cool-
to
look
at
verify
as
an
integral
part
of
turning
these
challenges.
You
see
here
on
the
left
into
opportunities
on
the
right.
You
know
when
we,
when
we
look
at
verify
aligning
to
the
market.
B
I
also
wanted
to
set
the
stage
a
little
bit
with
reconciling
the
product
market
fit
with
how
we
view
product
here
internally
at
gitlab.
So
we
talk
about
our
stages,
our
groups
and
our
categories,
but
but
customers
use
different
language
and
they
use
market
language
right.
So
we
hear
ci,
we
hear
cd,
we
hear
ci
cd
is
the
overarching
bucket
within
the
market,
and
so
this
is
the
familiar.
You
know
familiar
language
that
the
customers
use,
and
I
mean
the
things
that
attract
budget.
B
And
finally,
I
want
to
talk
about
the
go
to
market
motion
for
fiscal
year,
22
directly
linked
with
okrs
and
an
executive
sponsorship,
and
a
more
formal
plan
to
go
and
execute
and
be
the
devops
market
leader
right,
and
so
that
aligns
very
well
with
verify's
three-year
goals
of
you
know,
being
the
cicd
market
leader.
And
so
what
we're
going
to
do
here
is
we're
going
to
land
with
ci.
Cd,
obviously,
verify
plays
a
crucial
role
in
the
work.
B
That's
done
there
and
we're
going
to
expand
with
ultimate
things
like
devsecops
et
cetera,
premium
to
ultimate
place,
and
then
we're
going
to
eventually
be
the
market
leader
and
and
what
we're
doing
is
we're
using
three
go
to
market
motions.
You'll,
see,
ci
cd
devops
platform
and
get
ops
on
the
left
as
the
vehicles
to
deliver
this
value,
and
the
affiliated
sales
plays
you
see
from
from
left
to
right
in
that
top
bar
from
cic
are
going
to
be
something
like
upsell
quarter
premium
jenkins
takeout.
These
are
things
you're
familiar
with.
B
B
But
this
is
how
we're
going
to
operationalize
and
take
action
and
go
to
market
with
with
verified
and
the
work
that
you're
doing,
and
this
is
going
to
involve
everything
you
see
on
the
right
as
well,
from
personas
to
to
content
journeys
to
messaging
positioning,
etc,
and
so
a
really
really
cool
vehicle
to
deliver
this,
and
you
may
have
been
familiar
with
our
use
cases
that
we
did
last
year.
So
those
aren't
going
anywhere
as
of
now
right,
they're
still
here
and
they're,
going
to
be
rolling
up
and
feeding
into
this.
A
The
fiscal
year
22
go
to
market
plan
is
really
well
complemented
by
our
fiscal
year,
22
vision
for
verify.
We
have
the
three
themes
of
operations
for
all
speedy,
reliable
pipelines
and
smart
feedback
loops
that
are
balanced
and
complemented
by
the
plays
that
we're
looking
to
accomplish
in
in
the
sales
side
of
the
house,
and
you
can
go
to
the
next
slide.
B
And
with
these
plays
it's
important
to
to
highlight
some
of
our
differentiating
factors
where
we
have
a
competitive
advantage,
some
of
these
things
that
that
verify,
impacts
and-
and
it
makes
possible
for
us
to
go
out
and
say
hey.
This
is
where
we're
better.
This
is
why
we're
special.
This
is
why
we're
unique-
and
so
with
that
I
want
to
highlight
just
three
points
that
are
really
really
powerful
in
the
land
of
ci
and
in
the
land
to
verify
right.
B
So
when
we're
thinking
about
positioning
and
going
to
market,
we
always
want
to
leverage
the
fact
that
we
have
leading
source
code
management.
You
know
ci
and
code
review
and
one
and
you'll
see
that
directly
aligns
with
a
lot
of
the
work
here,
but
that's
really
powerful
and
that's
something
that
only
we
have
and
then
also,
of
course,
a
guided
single
path
production
to
two
production.
B
It's
it's
something
that
can
be
difficult
to
achieve,
but
I
think
it's
something
that
most
or,
if
not
all
organizations
want
to
achieve
and
with
this
complete
devops
platform
as
a
single
application
makes
it
much
more
feasible,
much
more
easy
to
accomplish
that
and
have
one
single
secure
path
to
production.
I
mean,
or
one
pipeline
kind
of
to
rule
them
all
the
way
I
like
to
think
about
and
then
of
course,
security.
Compliance
is
always
going
to
be
important
and
even
more
so
the
enterprise
level
which
we're
focusing
on
heavily
as
well.
B
But
we
want
to
talk
about
that
built-in
security
compliance
not
just
there,
but
it's
shifted
all
the
way
left
right.
So
from
idea
to
production
you're
ensuring
that
your
code
stays
secure,
compliant
all
the
way
through
that
process,
and
then
after
production
it
doesn't
stop
either
right.
You
know
we
have
things
like
dash
and
review
apps
together.
That
can
make
security
really
really
powerful
is
very
unique
to
us
and
as
far
as
value
and
differentiating
value,
so
a
few
things
that
are
really
helpful
to
position
us
in
the
verify
area.
B
Yeah
and
and
happy
to
to
throw
some
resources
into
the
notes
here
in
the
slides.
So
if
you
come
in
references,
you
can
check
out
some
more
details
about
personas
but
yeah
three.
You
know
three
main
user
percentages
that
we
focus
on
and
we've
got.
You
know
software
developer,
sasha
that
you
mentioned
right,
always
going
to
be
crucial,
think
about
less
disruptions,
more
coding
and
then
are
definitely
delaney
right,
also
also
a
very
crucial
persona.
B
B
And
finally,
for
me
just
to
close
this
little
intro
section
out,
you
know
I
just
I
think
we're
going
to
turn
it
continuous
journey
for
more
of
this
right.
This
is
just
a
great
example
of
of
logos
that
are
saying
exactly
what
we
can
do
and
provide
for
them
and
positioning
us
in
the
way
that
I
think
is
completely
accurate,
true
and
what
we
want,
more
of
so
on.
A
So
for
the
next
couple,
sections
we're
going
to
discuss
some
of
the
core
functionality
across
the
team
and
then
we're
going
to
talk
about
the
market
and
product
themes
and
what
we're
going
to
be
focusing
on
in
fiscal
year
22..
So
continuous
integration,
as
mentioned
before
tao,
is
leading
this
team
alongside
vitica,
cheryl
and
sam
it
they
fee.
They
are
focusing
on
items
like
merge
trains
which
help
keep
your
main
branch
green
and
help
keep
your
teams
running
as
fast
as
possible.
We
also
focus
on
building
functionality
across
artifacts
and
variables.
A
B
Hit
the
unmute
button
yeah
and
and
to
continue
with
the
themes
right,
squashing,
those
bugs
and
reducing
the
tech
debt,
I
think,
is
something
that
has
been
a
long
time
coming
right.
It's
really
easy
for
that
to
to
get
in
the
way
of
other
things,
so
that'll
be
really
really
good
optimizing
speed.
Reliability
is
another
big
theme
for
our
ci
group
and
then
adoption
through
usability
theme
right,
make
sure
we
have
a
lovable
ux
and
that
people
can
use
use
the
product
and
the
plays
on
the
right.
A
Awesome,
our
second
group
that
we'll
be
talking
about
is
pipeline
authoring,
led
by
dove
partnering,
with
nadia
on
the
design
side
and
cheryl
and
sam
on
engineering.
They
are
primarily
focused
on
thinking
through
modeling,
complex
relationships
in
the
yaml
file
and
pipeline
as
code.
So
when
you
think
about
pipelines,
parent
child
relationships
and
multi-project
pipelines,
but
also
the
pipeline
editor
visualization
is
one
of
our
most
recent
features
as
well
as
modeling
with
the
needs
relationship.
So
thinking
through.
A
We
also
want
to
help
them
have
better
visibility
in
building
out
all
of
their
stages
in
their
pipeline
into
a
single
graph,
also
making
sure
that
their
developers
are
working
as
as
fast
as
they
can
and
testing
the
validity
of
their
yaml
files
and
gitlab
in
a
single
place.
Before
committing
the
changes
by
leveraging
something
like
the
ci
linter.
B
Yeah-
and
you
know,
I
think,
the
the
continuous
integration
area
with
taos
team
and
in
the
pipeline
authoring
area
with
with
dope's
team
are
extremely
important.
All
of
the
verify
areas
are,
but
these
are
particularly
important
for
the
land
and
expand
play
right.
So
all
this
work
and
and
making
sure
that
ease
of
use
is
good
for
even
the
novice
user
or
the
more
you
know.
B
Typically,
adept
user
or
advanced
user
have
to
have
a
great
experience
and
they
have
a
lovable
first
run
and
not
just
getting
to
that
first
screen
pipeline
quickly,
but
keeping
it
green
right
that
I
know
you
mentioned
earlier.
So
this
goes
a
long
way
in
our
efforts.
You
know
downstream
as
well
to
make
sure
that
experience
is
good,
that
we
can
land
and
we
land
strong
and
have
that
foothold,
and
then
we
can
expand.
B
A
And
I'm
really
excited
about
this
slide,
obviously,
because
I
jumped
to
it
early.
So
runner
is
our
next,
as
our
next
group
darren,
eastman
and
hi
anna
vera
mucio
are
the
teammates
partnering
on
this
on
this
team
and
elliott
is
the
engineering
manager,
as
mentioned
before,
they
are
primarily
responsible
for
this
runner
technology
landscape.
They
are
the
engine
underpinning
our
ci
capabilities
and,
as
you
can
see,
they're
a
vast
offering
of
all
the
different
capabilities
that
are
powering
our
ci
across
all
the
different
capabilities
that
we
have
inside
of
git
lab.
A
What's
even
more
important.
Is
that
we're
looking
at
adding
additional
functionality
to
again
empower
teams
to
deploy
when
and
where
and
build?
However,
they
want,
especially
on
the
cloud
so
mac
os
is
a
priority
for
this
year.
Also,
sticky
runners
is
going
to
be
another
one
of
those
priorities
that
we
see
in
first
half
again
making
sure
they
can
take
advantage
of
autoscaling
on.com
whenever
and
wherever
they
want
to.
B
Yeah,
I
think
very,
very
well
well
stated,
and
since
you
set
the
car
analogy,
I'll
come
in
and
spike
it.
I
think
I
think
runner
you
know
is
like
a
dodge
ram
truck
is
to
hemi
engines
right,
you
know,
and
so
you
know,
dodge
trucks.
Have
these
huge
hemi
emblems
on
them,
because
that
engine
is
so
important
to
their
brand
into
that
truck
into
the
value
of
that
that
that
vehicle
and,
I
think,
runner's
the
same
thing
for
us
right.
B
It
is
a
incredible
engine
underneath
the
hood
of
gitlab
and
it
does.
You
know
it's
the
gatekeeper
for
our
incredible,
incredibly
rich
features,
and
so
we
want
to
make
sure
that
we
have.
You
know
a
seamless
experience,
it's
very,
very
usable
and
that
we
we
can
scale
without
complexity
with
runner
right.
So
you
know
multi-platform
multi-language,
all
those
kind
of
things
that
need
to
be
supported
so
that
you
can,
you
can
scale
and
do
it
efficiently.
A
Last
but
definitely
not
least,
is
testing
led
by
james
heimbuck
and
partnering,
with
hyanna
and
ricky
on
the
design
and
engineering
side,
they're
primarily
focused
on
code
coverage,
which
is
around
saving
time
for
teams
as
they
build
in
this
code.
Quality
and
co-testing
coverage
functionality
inside
of
of
gitlab
baking,
in
that
smart
feedback
loop
between
teams,
making
it
even
easier
for,
like
that,
alex
and
dakota
persona
to
make
smart
informed
decisions
about
code
quality
inside
of
gitlab.
But
that's
not
it.
That's
not
only
what
we
do
in
testing.
A
They
also
have
unit
testing,
which
is
one
of
the
most
common
methods
of
testing
code
inside
of
pipelines
in
gitlab
and,
what's
even
better,
is
that
we
have
a
report
as
well
as
using
the
functionality
in
merge
requests.
So
if
you
don't
use
merge
requests,
you
have
another
option
of
using
unit
tests
inside
of
gitlab.
A
We
also
have
other
functionality
around
testing
for
developers.
So
if
you're
using
web
performance
or
browser
performance
testing,
we
offer
that
functionality,
we
have
an
immense
amount
of
breadth
coverage
around
testing
capability,
which
is
unparalleled
across
other
cicd
tools,
not
to
mention.
We
also
offer
load
performance
testing
to
ensure
the
testing
performance
of
your
apis
and
microservices
at
scale
all
from
the
merge
request
widget.
So
you
don't
have
to
leave
your
screen
as
a
developer.
A
It's
all
right
there
and
one
one
one
place
even
team
leads
who
are
doing
merge,
request
reviews
are,
are
able
to
not
context
switch
they're
not
having
to
go
between
different
testing
platforms,
to
view
performance
changes
between
web
performance
and
and
load
performance,
but
they're
also
able
to
see
accessibility,
testing
from
the
merge
request
widget.
So
it's
all
packaged
in
one
place
for
gitlab
again
an
immense
amount
of
breadth,
and
even
though
we
we
haven't
necessarily
dug
another
level
deeper
into
the
amount
of
depth
across
all
these
areas.
A
It
allows
users
to
have
all
areas
of
their
code
tested
by
gitlab
in
invisibly,
shown
in
the
merge
request,
widget
we're
able
to
use
testing
as
a
great
landing
platform
for
users
to
see
visibly
how
is
their
code
quality
their
code
health
over
time,
we're
looking
at
enhancements
in
fiscal
year,
22
to
improve
that
visibility
at
the
project
and
group
level,
and,
what's
even
better,
is
that
this
is
our
investment
category
for
premium
to
even
ultimate
tier
value.
So
we're
really
using
this
as
our
lever
inside
of
the
product
management
theme
for
our
paid
users.
A
What's
even
better.
Is
that
we're
also
looking
in
the
future
for
enhancing
reporting
capabilities
around
unit
test
reports
and
continuing
to
add
value
around
other
testing
categories?
We're
seeing
usability
become
an
even
better
investment.
Prioritizing
usability
inside
of
git
lab
is
as
a
top
priority
across
verify,
so
we're
still
seeing
that
in
the
testing
category
as
well.
I
see
this
as
a
really
great
complement
to
the
go
to
marketplace.
A
B
Yeah
so
yeah
testing
we
just
we
have
such
a
wide.
You
know
breadth
and
depth
of
testing
capabilities
right
and
we're
moving
really
quick.
So
I
think
it's
important
also
note
that
we
can
draw
up
excitement
in
the
market
I
think
for,
for
what
we
have
done
and
what
we're
going
to
be
doing
with
testing.
B
I
mean
how
quickly
we're
moving
and
how
quickly
we're
maturing
things
and
things
that
that
are
that
our
customers
and
our
audience
needs
so
testing
is
gonna,
be
something
that
I
think
will
be
really
really
interesting
and
I'm
looking
forward
to
seeing
how
it
aligns
with
our
sales
place
and
it
can
really
fit
within.
I
think
any
of
those
up
there
right
and
even
something
like
a
premium
to
ultimate
that
you
mentioned
jackie
right
which
isn't
in
the
cicd
motion
per
se,
but
it
is
in
the
devops
platform
motion.
B
So
even
maybe
some
cross
collaboration
there
to
leverage
some
of
these
testing
capabilities
and
I
like
to
think
you
can't
have
speedy,
reliable
pipelines.
If
you
don't
have
speedy,
reliable
testing
either
right.
So
I'm
really
looking
for
deeper
insights
and
results
into
how
we
test
and
making
sure
that
code,
quality
and
coverage
is
mature
and
and
providing
a
lot
of
value
so
exciting.
A
So
we're
really
excited
to
begin
that
that
journey
for
the
pipeline
improvement
and
then
pipeline
authoring
it'll
be
really
great
to
start
seeing
job
templates
and
the
template
experience
come
to
life
after
pipeline
builders
and
the
pipeline
authoring
experience
becomes
more
viable
for
our
users,
we're
also
starting
to
dive
into
our
cross-stage
research
around
the
next
generation
of
ci
and
what
that
could
look
like,
as
we
start
to
pair
together.
Things
like
the
five-minute
app
the
auto
devops
journey
and
how
we
want
to
see.
A
Ci
have
a
re-emergence
with
some
different
concepts
in
the
market,
especially
as
we
start
to
think
about
proactive
notifications
of
pipeline
failures
or
flaky
test
detection.
There's
a
lot
of
exciting
things
that
we
can
start
doing
with
gitlab.
Once
we
start
building
on
top
of
a
really
stable
foundation,
we're
definitely
excited
for
fiscal
year
22,
and
I
cannot
wait
to
start
shipping
more
exciting
features.