►
From YouTube: Testing / Runner UX / PM / Research Sync 2020-11-18
Description
Darren (Runner PM), James (Testing PM) and Rayana (Designer) do introductions and talk about current projects.
A
A
B
You
jump
right
in.
I
have
a
lot
of
questions
yeah.
I
kind
of
just
wanted
to
use
this
time
to
get
to
know
each
other
and
then
just
talk
a
little
bit
about
everything,
that's
going
on
in
testing
and
align
our
ways
of
working,
and
I
see
that
yeah
james
had
a
couple
of
answers
here,
but
yeah
I'll
just
introduce
myself.
I
met
you
before,
but
I
don't
think
we
have
been
introduced
properly.
B
I'm
hayanna!
You
know
that
I've
been
with
gitlab
for
two
years
now,
and
I've
been
working
mostly
well.
Only
cicd
actually
so
had
a
number
of
pms
a
number
of
design
managers,
but
my
specialization
is
really
in
ci
cd,
so
in
cd
with
jackie
for
the
last
year
and
audit
as
well-
and
I
feel
like
this-
is
my
first
time
actually
looking
to
ci-
I
think
dimitri
was
the
expert
for
most
of
the
time.
B
B
Whenever
I
have
a
chance
to
yeah
just
tackle
some
ux
depth
and
ui
polished
instincts,
I
feel
very
comfortable
with
that
and
collaborating
with
the
with
the
front-end
engineers
as
well.
I
have
fun
anyways.
That's
me.
It's
a
bit
a
bit
weird
kind
of
introduce
yourself
after
three
years,
two
years
in
the
company,
but
I
kind
of
just
wanted
to
to
touch
base
on
that
with
you
guys,
anyways.
B
A
A
So
we
can
go
around
and
do
intros.
Obviously,
I'm
james
I've
been
in
verified
testing
for
a
little
over
a
year
now
year,
in
couple
of
months,
that's
been
my
only
area
and
shuffled
through
some
engineering
managers,
some
designers,
but
overall
had
a
great
time
working
with
all
of
those
folks
super
excited
to
be
working
with
the
designer.
This
is
the
first
time
I've
done
that
in
my
career
or
the
first
time
in
a
while.
So
that's
really
exciting.
For
me,
awesome.
C
I
guess
I'll
go.
I'm
darren,
hi
I've
been
in
gitlab
for
over
a
year,
I'm
actually
looking
forward
to
this
collaboration.
I
was
working
very
closely
with
juan,
but
I
think-
and
that
was
great
now.
I
think
we
have
an
opportunity
to
start
synchronizing
some
of
the
overall
experience
activities.
So
I'm
looking
forward
to
this
collaboration
kind
of
getting
us
all
on
the
same
page.
So
looking
forward
to
as
we
get
on
the
agenda,
my
brain
dump-
and
hopefully
it's
not
going
to
be
too
overwhelming
for
growing
the
call.
B
A
B
Yeah
and
we
become
and
kind
of
just
wanted
to
understand.
Where
do
you
need
help,
so
I
can
plan
my
own
boarding.
I
think
my
focus
for
the
next,
I
think
for
the
the
rest
of
the
year,
since
we
have
the
holidays
and
yeah.
You
have
thanksgiving
if
you're
in
the
u.s,
I'm
also
going
to
take
some
time
off,
but
I
feel
like
my
focus
now
is
going
to
be
onboarding
and
finishing
off
my
acting
product
design,
manager
role
and
I
just
want
to
align
with
you.
B
B
C
I
think-
and
this
is
kind
of
like
the
sort
of
the
the
brain
dump
every
time
we
have
like
sort
of
change
in
the
running
team
is
that
with
the
runner,
because
of
because
of
what
the
runner
does.
We
have
ongoing
customer
interviews
and
we're
working
very
closely
on
a
lot
of
times
with
large
enterprise
customers
and
working
through
pain
points.
So
the
running
team
is
different.
C
I
think
it's
different,
but
we
are
very
much
always
engaged
in
customer
discussions,
but
even
though
we
may
not
necessarily
have
an
interview,
that's
kind
of
like
scheduled
as
part
of
like
a
research
effort,
we're
always
on
customer
calls
talking
about
challenges.
Customers
have
with
using
gitlab
ci,
with
using
runners
in
the
enterprise
et
cetera,
et
cetera.
So
so
with
that
said,
we
just
have
a
lot
of
that
kind
of
ongoing
customer
engagement
in
regards
to
customer
interviews
as
part
of
a
more
focused
research
effort.
C
There
are
opportunities
for
us
and
I
can
get
that
later
on,
as
I
kind
of
give
us
everyone
sort
of
a
brain
dump
in
terms
of
the
lay
of
the
land.
But
there
are
opportunities
for
us
in
terms
of
focused
research
efforts
related
to
new
experiences
that
we
want
to
introduce
in
the
ui
for
the
runner,
potentially
one
and
then
there's
something
else
as
well.
We'll
get
to
later.
B
On
sounds
awesome.
Jackie
also
did
this
to
that
like
having
random
customer
interviews
or
just
like
async
conversations
with
with
our
customers,
so
I
had
to
hear
to
the
agenda,
but
I
just
want
to
vocalize
a
feel
free
to
add
me
to
those.
Actually,
please
add
me,
I'm
asking
you
add
me
to
these
interviews
and
and
I'll
join
when
I
can,
because
to
me
I
learn
yeah
by
experiencing
yes.
C
I
think
I
think
I
want
to
kind
of
let
me
rephrase
what
I
said.
I
think
we
want
to
make
sure
we-
maybe
it's
already
in
the
gitlab
handbook,
differentiate
between
a
customer
interview
that
we're
doing
as
part
of
researching
a
new
feature
right
and
that
kind
of
that
kind
of
customer
interview
versus
the
running
team
gets
an
opportunity
to
chat
with
customers
in
our
ongoing
basis,
because
we're
pulled
into
sales
goals
and
because
we're
pulled
into
escalations,
we
get
reported
into
like
architectural
type
calls.
C
C
I
don't
know
if
you
necessarily
want
to
be
involved
in
those,
but
those
causes
where
we
get
a
lot
of
feedback
from
customers
in
terms
of
the
capabilities
that
they
want,
so
certainly
can
bring
you
into
those,
but
those
are
usually
like
all
to
weird
inverters
of
the
day
and
we
don't
necessarily
have
as
much
of
the
I'll
say,
structured
research
interviews
related
to
like
hey
we're
developing
this
new
feature.
It's
nice
and
big
and
we're
gonna
want
to
get
feedback
on
it
kind
of
thing.
B
A
A
A
A
B
Yeah
I
used
to
do
a
walkthroughs
with
the
with
jackie,
not
just
when
it's
complete
but
yeah,
it's
part
of
the
interviews
and
then
going
talking
about
it
and
sometimes
filling
together,
so
I'm
familiar
with
the
process.
So
if
you
think
that
you
would
be
useful
as
well
and
valuable
to
have
me
in
this
in
this
process
feel
free
but
yeah,
of
course
awesome
yeah.
What's
the
interesting
thing
going
on?
What's
the
most
exciting
thing
for
you
guys,
right
now,.
C
C
C
Yeah,
so
I'm
gonna
put
this
on
the
top,
so
just
to
give
a
little
bit
of
context
at
the
beginning
of
the
year.
We
did
this
large
sort
of
research
effort
around
this.
This
concept
called
frictionless
runners
and
I'll.
Add
this
into
the
document
a
second
and
what
we're
looking
at
is
this
this
main
paper
from
customers
right?
Basically,
customers
are
saying
that
gitlab
runs
for
too
difficult
to
use
and
at
least
in
one
case
created
so
much
friction
in
the
infrastructure
they
choose
not
to
use
github.
C
C
C
C
Do
we
want
to
have
this
efficiency
effort,
so
it
kind
of
was
parallel
or
kind
of
dovetail
when
based
on
the
executive
team's
ads,
we
focus
just
in
the
short
term
on
this
specific
use
case
about
making
it
super
easy
for
self-managed
customers
to
get
going
with
using
that
lab
runners.
So
it's
related
to
friction
as
well
as
epic,
we're
gonna
get
that,
but
in
here
what
you're,
seeing
in
terms
of
our
solutions
roadmap.
C
As
we
talk
about
automation,
we
created
a
solutions
roadmap
for
automating,
a
setup
experience
for
the
runners,
things
like
docker
images
and
so
on
and
so
forth.
Where
we
are
right
now
is
the
first
ux
feature
that
we
tried
to
implement,
which
james
we
didn't
be
back
yesterday,
unfortunately,
is
the
guided
install
feature
all
right,
so
that's
the
first
thing
we
designed
in
the
ui.
The
angle
was
we'll
add
this
guided,
install
feature
in
the
ui,
come
back
later
on
and
add
automation
behind
it.
C
C
You
know,
gitlab.com,
it's
this
enterprise
management
view.
So
in
terms
of
our
next
research
efforts.
What
we
want
to
do
is
we
want
to
take
these.
The
initial
designs
revamp
these
and
go
back
out
to
customers
and
say:
hey.
Is
this
the
right
thing?
Is
this?
Let's
just
step
back,
here's
what
we
thought
we
heard
when
we
have
all
these
conversations
now
we're
coming
back
and
we're
thinking
about
black,
very
large
customers.
I
don't
want
to
mention
those
customers
names
on
this
call.
C
We
want
to
go
back
to
those
customers
and
have
focused
research
interviews,
hey.
We
thought
we
heard
this.
Here's
where
we're
heading
this
makes
sense
for
you.
What
are
we
missing,
but
all
these
different
pieces
are
kind
of
somewhat
tangential
and
that's
all
of
the
next
sort
of
what
we
want
to
do
and
running
in
terms
of
research
and
moving
the
ball
forward.
C
But
for
me
it's
how
do
we
improve
the
automated
install
experience
which
we're
iterating
on
that
right
now
and
then
the
next
big
thing
is:
what
do
we
really
want
to
do
as
a
team
around
runner
enterprise
management?
I
know
we're
having
discussions
about
the
various
dashboards,
so
how
does
all
of
that
fit
together?
At
the
end
of
the
day,
we
have
large
customers
with.
I
don't
want
to
make
up
a
number
of
hundreds
of
runners
all
over
the
place
right
and,
and
they
want
to
be
able
to
very
quickly
understand.
C
Are
these
things
secure?
Are
they
executing
jobs
right
and
then
can
I
if
there
is
a
security
issue
with
the
runner
like
say
the
token
is
compromised?
Can
I
quickly
deactivate
that
in
the
future
folks
want
to
know
how
is
my
notification
like,
for
example,
I'm
running
it
on
aws,
and
it's
costing
me
whatever
it
is?
Will
it
be
cheaper
running
on
gcp
so
anyway,
so
there's
a
lot
of
work
in
that
space
and
that's
the
next
evolution
of
our
research
that
we
want
to
do
in
terms
of
the
enterprise
management.
Dashboard:
hey!
C
B
This
is
awesome.
I
have
seen
that
some
of
these
efforts,
through
the
design,
presentations
and
the
showcase
from
juan
and
but
also
viticult,
it's
nice
to
get
a
little
bit
of
understanding.
What
you
folks
are
planning-
and
I
saw
one
of
the
the
issues-
I'm
not
exactly
exactly
sure
which
one
you
shared.
I
think
the
one
that
of
the
dashboard
do
you
have
like
a
view
with
some
some
cards.
Is
that
one
part
of
the
the
three
year
vision
for
for
runner?
B
C
Didn't
actually
create
a
three-year
vision
for
runner.
In
my
mind,
if
you
want
to
create
a
three-year
vision,
it's
fine,
it's
not
a
bad
idea,
but
I
actually
think
we
should
go
faster
than
three
years.
I
think
the
idea
was
the
current
admin
view
and
we
should
definitely
have
a
three-year
version
like
in
three
years.
What
does
management
of
enterprise
runners
look
like
at
scale?
That's
not
a
bad
idea.
We
never
did
actually
do
that
for
your
vision.
We
just
basically
knew
that
hey.
C
C
This
so
may
not
be
completely
accurate,
but
I
think
I
recall
they
said
they
had
three
or
four
guild
club
instances
right
three
or
four
separate
flag
instances
and
like
one
get
that
make
sense,
for
example,
hundreds
of
projects
I
forget
how
many
runners,
and
so
their
their
their
need
and
their
user
experience
reset
managed.
Customers
is,
as
you
start,
having
this
growth
of
git
lab
in
your
environment.
C
These
large
number
of
projects.
Now
these
last
number
of
build
agents
or
runners.
How
do
you
effectively
manage
that
thing
and
what
admin
view
today
doesn't
give
them
that
and
three-year
version
is
great,
but
I
I
my
firm-
and
my
firm
belief-
is
that
if
we
gitlab
can
get
ahead
of
him
of
this
space,
improving
that
experience
we
probably
get
ahead
of
microsoft,
which
I
have
a
sneaky
suspicion-
is
coming
soon
with
a
better
enterprise
management
solution
for
yourself
hosted
customers
well
yeah.
C
We
can
still
be
covering
the
three-year
version,
but
I
think
I
was
kind
of
looking
to
try
to
try
to
iterate
on
improving
that
admin
experience
as
fast
as
possible.
Starting
to
add
things
like
hey.
Can
I
find
my
runner
do
I
know
which
project
this
runner
is
attached
to
do?
I
know
where
this
runner
is
so,
for
example,
darren
could
attach
a
runner
to
your
project
and
that
runner
could
be
on
diamond's
computer
at
home.
Is
that
secure
all
those
types
of
things
we're
going
to
solve
for.
B
Yeah,
I'm
happy
that
this
sounds
all
similar
to
what
I've
been
doing
already
as
management
in
managing
deployments
at
skill
and
making
sure
that
yeah,
our
customers
have
this
application
view
of
the
the
release
orchestration
release
process
so
not
so
different.
I
imagine
from
the
the
use
case
different
parts
of
the
product,
but
it's
also
good
that
yeah
have
that
background,
so
you
can
align
with
well
not
progressive
delivery
anymore
with
the
release
through
this
side,
the
cd,
oh
super
cool,
I'm
just
adding
here
the
opportunity.
C
Is
one
sorry,
the
one
other
thing
for
renaissance
we're
all
sharing,
so
this
way
everyone's
on
the
same
page.
I
I
just
think
jackie
on
this
yesterday.
Where
is
it?
It's
called.
Let
me
find
it
so
it's
not
so
this
one
is
a
little
bit
different
tangent,
so
bear
with
me,
as
I
completely
disrupt
the
agenda,
but
I
want
to
kind
of
share
with
everyone
so
that
everyone's
aware,
what
crazy
thoughts
are
running
through
the
the
pms
of
one's
brain
here
it
here
it
is.
C
I
think
I
found
it
now.
Let
me
just
find
a
link
to
it.
Yeah,
I'm
applying
to
this
on
your
gender.
I
don't
know
how
this
one
fits
into
our
needs
to
do
an
opportunity,
canvas
and
research
and
all
that
stuff.
But
let
me
just
add
it
in
here,
so
what
that
one
is
I
just
added
below
it's
probably
in
the
wrong
spot.
That's
a
really
wrong
spot!
Sorry,
let
me
just
find
it.
We
can
fix
it
later
right
here.
C
So
what
I
want
is
is
right
now
this
is
I'm
calling
this
the
mac
os
build
cloud
on
github.com
pulse,
ga3
evision,
so
it's
ignoring
the
automated
setup
stuff
we
just
talked
about
and
my
stuff
for
the
second.
We
just
talked
about
this
other
thing:
we're
working
on
with
right
now
on
gitlab
that
comments
we
potentially
all
know
we
offer
the
linux
runners
on
github.com
and
we
offer
the
windows
runners
on
gitlab.com
and
we're
trying
to
add.
C
Are
we
working
towards
adding
the
mac
os
runners
in
github.com,
which
I've
been
calling
the
mac
os
bill
cloud?
What
we
I
created,
which
recently,
is
this
forced
ga3
edition,
which
is
basically
piggybacking,
all
of
that
three
division
theme
theme
and
thinking
about
once
we
get
to
ga
on
the
build
cloud
for
mac,
or
I
say
in
the
middle
of
next
year.
C
What
does
the
three
average
gun
look
like,
and
maybe
this
is
an
area
of
opportunity
for
us
to
do
another
opportunity,
canvas
more
research
and
that
sort
of
thing,
so
I
just
want
to
share
that
so
on
this
one
james,
there
were
things
like:
do
we
want
better
integrated
security
scanning
with
someone
that's
using
the
mac
os
bulkhead
off,
you
know,
do
you
know
what
I
mean
like
hey
you're
on
github.com
and
we
automatically
recognize.
This
is
a
mac
os
application
and
do
we
do
some
nice
fancy
thing
with
ci?
C
B
B
This
was
awesome,
deep,
diving
guys,
that's
that's
how
that's
how
we
roll
super
cool,
I'm
gonna
look
into
this
next
couple
of
days
and
then
yeah
I'll
come
up
with
with
some
questions.
As
I
start
understanding
everything
on
the
scope,
I
know
that
we
are
almost
at
a
time
and
I
just
want
to
touch
base
on
what
can
you
wax
do
better?
A
A
So
I
think
if
we
focus
a
little
bit
more
on
the
research
side
of
things
and
some
loose
design
and
then
do
some
more
just
in
time,
design
a
milestone
or
two
ahead,
we'll
be
in
a
better
spot,
and
part
of
that
is
my
fault
of
we
prioritized
some
work
and
then
we
realized
that
it
was
going
to
be
just
a
ton
of
back
end
work.
Now
that
we
have
a
great
engineering
leadership
in
place.
That
is
more
focused
on
testing,
that's
less
of
a
problem,
because
we
understand
all
of
the
back
end
work.
C
Yeah,
while
you're
capturing
that
I
would
say
for
me,
let's
just
say
I'll,
give
a
very
tactical
example:
let's
just
say
we
would
you
were
to
work
on
a
design
for
some
new,
let's
just
say
the
enterprise
manager
and
dashboard,
the
first
mvc
iteration
right.
Well,
I
think
the
next
thing
we
should
do
very
quickly
is
the
first
iteration
of
the
design
comes
out
and
we
very
quickly
engage
with
front-end
and
back-end.
We
don't
wait
for
months
and
months
for
the
beyond
the
milestone
to
engage
like
hey.
C
This
is
what
we're
thinking,
how
big
of
a
bread
basket
is
this
thing?
Can
we
realistically
schedule
it
and
whatever
milestone,
do
we
need
to
break
it
down
further?
Let's
get
some
eyes
on
this
versus
waiting
like
to
james
point,
two
or
three
months
to
get
steal
and
then,
by
the
time
you
bring
in
front
10
you're
like
oh,
this
is
going
to
take
six
months
and
then
you're
like
a
year
later,
you
haven't,
died.
B
So
work
on
the
iteration
like
on
the
fly
with
the
team,
as
we
as
I
think
for
both
as
we
validate
things
and
we
learn,
keep
the
train
moving
so
that
yeah,
that's
how
I
work
with
the
with
jackie.
So
I
have
a
I'm
just
gonna
show
for
reference,
so
you
can
understand.
Well,
maybe
we're
not
gonna
do
the
exact
same
thing,
but
that's
how
we
work
so
in
the
release
management
handbook.
I
have
like
a
ux
vision
map.
B
That's
the
second
link
you
can
send
where
I
know
that
okay,
these
are
like
well
10,
probably
big
items
for
release
management,
so
advanced
deployments,
group
releases,
splitting
secrets
from
ci
variables,
etc.
So
those
are
the
things
in
the
high
level
that
I
should
be
aware
of
and
then
yeah
the
validation,
the
interviews,
the
prototyping
everything
works
around
these
teams,
but
with
jackie
we
were
ahead.
We
were
like
milestone
agnostic,
so
the
second,
the
first
link.
B
Actually
I
sent
you
is
the
epic
that
I
use
with
her
to
kind
of
just
put
like
okay.
This
is
your
your
ux
backlog,
so
I
don't
need
to
be
working
on
13.,
whatever
I'm
working
on
whatever
we
are
validating
right
now,
so
this
used
to
be
my
list
of
things
that
are
my
top
priorities
and
then
once
I
finish
something
and
it
moves
to
planning
breakdown
because
the
developer
is
already
groomed,
then
we
have
an
idea.
It
moves
out
of
my
my
epic
and
I
go
to
the
next
step.
B
That's
how
I'm
used
to
work.
I
know
that
we're
gonna
have
a
different
dynamic,
but
just
so
you
have
an
idea.
That's
why
I
was
asking
in
the
beginning.
Please
include
me
on
everything
I'll
try
to
understand
as
much
of
the
technicality
that
I
can
because
I
feel
like
as
the
way
I
learned
at
gitlab
is
that
you
need
to
know
how
things
work
and
even
if
I
don't
speak
the
language
of
the
developers,
they're
the
ones
that
are
going
they're
going
to
guide
the
design
decisions.