►
From YouTube: CI PM/UX Research Planning on 2020-08-05
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
You
to
see
if
emily
can
help
us
run
a
survey
and
blast
it
everywhere,
use
the
social
media,
get
rupert
on
it
for
linkedin
and
put
it
everywhere
just
to
see
you
even
know
it's
a
thing
that
we
have
and
then
based
on
that
question.
Are
they
interested
like?
A
Did
they
try
it
and
will
they
talk
to
us
about
their
experiences
and
if
they
didn't
try
it
are
they
interested
in
talking
to
us
about
trying
it
and,
if
so,
get
the
tams
involved
and
have
like
a
one
to
two
conversation
with
them,
because
I
think
that
would
help
the
tams
to
understand
what,
if
there's
objections,
I
don't
know
like
right
now.
We
have
no
idea.
Why
nobody's
using
this
thing,
so
we
have
to
figure
out.
Is
it
what
is
it
so
yeah
so.
B
B
I
mean
I
have
updated
the
link
that
I
added
the
conversation
to
dovetail,
but
I
it
somehow
got
missed
in
this
particular
issue.
It
was
there
in
slack
as
well,
so
I've
just
updated
it
in
the
issue.
If
you
click
on
it,
you'll
go
to
the
conversation
and
you'll
see
that
what
they're
trying
to
say
is
they
never
wanted
what
we
have
created.
They
wanted
something.
A
Yeah,
that's
what
I
that's
what
I
suspect
it
will
be
nice
to
see
if
we
can
get
more
than
just
one
person
telling
us
that
and
that's
why.
I
that's
why
the
other
part
of
that
survey
would
be
to
see
if
people
were
halfway
interested
in
some
sort
of
solution
and
to
talk
with
us
about
that,
like
about
our
proposed
solution
and
then
also
talk
back
to
us
about
what
they
would
actually
want,
because
I,
my
gut,
is
telling
me
that
we
somebody
somewhere
assumed
that
the
wrapper
is
the
right
answer.
A
We
went
off
and
we
coded
it
without
actually
getting
that
problem
validated
that
that
is
the
right
solution
for
that
problem,
and
here
we
are
so
now
we
have
to
back
up,
and
you
are
right.
You
think
that
this
is
more
falls
more
in
the
problems:
validation,
space
because
we're
backing
back
up
and
trying
to
actually
validate
what
is
the
problem?
We
know
the
outcome
is
that
they're
not
using
ci
rci
they're
still
using
jenkins.
A
We
suspect
the
problem.
The
core
problem
is
that
jenkins
just
doesn't
play
nice
with
anybody
else,
and
you've
invested
people,
you've
invested
time
and
training
and
jenkins
and
pipelines.
We
thought
the
wrapper
would
be
the
best
solution.
Clearly,
it's
not
so
now
we
need
to
go
back
and
find
out
from
our
potential
customers
perspectives.
A
C
And
so
let
me
clarify
when
you
talk
to
the
customer
so
that
we
actually
didn't
think
it
was
the
best
solution.
It
was
this,
the
smallest
one
we
can
do
that
was
feasible
at
the
time,
because
our
engineers
did
some
studies
on
what.
If
we
built
something
that
did
a
translation
you
know
of,
but
it
wasn't
possible,
we
would
basically
what
they
came
up
with
is
trying
to
translate
like
the
declarative,
syntax
and
it
would
be
writing
a
whole
entire
new
language
which
we
didn't.
C
Well,
what
is
a
at
least
a
stop
gap
solution
for
them
to
at
least
start
running,
yeah
gitlab
inside
I'm
sorry
running
jenkins
inside
gitlab,
and
so
that
was
to
allow
them
to
at
least
put
it
in
a
box
using
the
wrapper.
A
Right
right-
and
I
get
that-
and
I
think
that
at
some
point
we
just
it
was
like
ships
in
the
night
we
just
we
just
went
past
and
we
I
don't
know
who
decided
like
decided
to
go
ahead
and
push
forward
with
that
wrapper
solution.
But
unfortunately
it
doesn't
seem
like
it's
something
that
our
customers
want.
What
we
have
to
do
is
figure
out
why
they
don't
want
it.
We
only
have
one
customer
so
far,
who's
told
us
anything,
and
so
now
we're
on
the
hunt
to
try
to
find
out.
A
A
Do
we
further
invest
in
the
rapper
or
do
we
pivot
and
say
well
boys
and
girls
we're
making
a
new
language
if
we
want
to
do
this
kind
of
thing,
which
is
crazy,
or
is
there
a
third
solution
or
a
fourth
solution
to
the
problem?
But
we
have
to
uncover,
I
think
we
have
to
uncover
a
little
bit
more
of
the
barriers
from
our
customers
perspectives
and
I'm
not
enough
of
a
expert
in
any
of
this.
A
A
All
of
this
is
this
even
the
thing
to
be
focusing
on
andre-
and
I
talked
about
this
yesterday
because
we're
doing
that
ci
adoption
journey
project
and
yeah
like
who
knows
I
I
don't
know,
I
don't
know
if
that's
the
area
to
focus
on
or
if
it's
to
focus
on
other
parts
of
the
product
to
make
it
look
so
cool
and
so
sweet
and
so
easy
to
use
that
they
will
abandon
jenkins
and
we
don't
have
to
wrap
anything.
We
don't
have
to
talk
to
anything.
A
Who
knows,
I
don't
know,
but
that's
like
the
further
out
thing
like.
If
nobody
takes
our
bait
on
the
survey,
we
can't
find
anybody
to
talk
to
I'd,
say
something's
there
that
we're
missing,
and
it
may
very
well
be
this
time
and
investment
in
training
and
writing
their
own
pipelines
and
jenkins
that
they
just
can't
move
away
from,
but
we'll
see.
B
E
A
B
I
figured
that
this
problem
is
not
something
very
unique
and
I
mean
other
products-
circle
ci,
github,
they're,
all
struggling
with
something
very
similar.
So
what
I
did
was,
I
also
went
ahead
and
read
a
few
comments
on
stack
overflows
and
I'm
like
finding
different
places
where
I
can
read
the
reaction
of
people
who
are
using
those
wrappers
so
that
I
get
what
they
did
right
or
what
they
did
wrong.
D
Yeah,
this
is
great.
I
think
this
is
amazing
to
look
at
the
competition
and
see
what
we
can
learn
from
them.
What
they've
done,
what
ideas
we
can
get
and
I
see
tao
you
also
posted
a
link
on
linkedin
where
some
people
have
commented.
I
think
this
is
a
great
idea
to
try
reaching
out
to
those
20.
wow.
C
Out
of
those
20,
there
was
one
that
actually
tried
it
and
opened
an
issue
for
an
improvement
to
the
wrapper,
and
it's
m
ram
he's
like
third
from
the
top.
That's
awesome,
so
you
won't
need
to
reach
out
to
him.
C
You
could
probably
see
he
made
a
comment
in
the
public
issue
and
he
linked
to
the
issue
he
created
and
we
quickly
implemented
that,
but
no
one
else
has
and
each
time
they
said,
they're
in
I
said
well
great
everything
you
needed
in
that
issue
go
to
the
issue
and
then
they,
some
of
them
just
haven't
now,
keep
in
mind
that
the
about
when
this
happened
was
when
the
pandemic
was
really
affecting
people
no
and
see
that
could
be
a
whole
other.
A
C
The
pandemic
so,
but
you
know
I
I
I
think
things
have
kind
of
settled
down
as
far
as
people
finding
their
rhythm
at
work
and
it's
just
a
maybe
a
matter
of
reminding
them
hey
you
expressed
interest
back,
you
know
way
back.
When
can
we
can
can
you
would
you
be
interested
in
filling
out
this
screener
to
see
if
you're
the
right
candidate
for
us
to
to
interview
yeah.
A
C
I
know-
and
so
it's
interesting
but
but
I
I
I
think,
lori's
idea
of
of
having
our
marketing
team
really
blast
the
news
out
there
to
to
get
awareness.
I'm
I'm
expecting.
You
know
hundreds
and
hundreds
of
people
responding
to
something
like
that.
That's
using
jenkins,
not
the
the
200
or
so
that
responded
to
my
post
in
linkedin.
A
Yeah
yeah,
I
hope
so,
and
you
know
we
can
ask
also
in
that
survey
we
can
target
people
who
are
using
other
products
like
and
you're
saying,
circleci
and
github
and
if
they
all
have
rappers
too
for
jenkins.
Let's
talk
to
those
people
too,
because
you
know
I
mean
I'm
assuming
nobody's
doing
it
perfectly.
A
B
Yeah
I
mean
one
thing
that
I
mean
I
previously
used
to
practice
was.
If
I
worked
on
a
certain
thing
on
a
in
a
particular
milestone
and
towards
the
end
of
that
milestone,
I
used
to
write
blogs
about
it
and
really
advertise
it
everywhere,
so
it
really
used
to
catch
eyeballs
and
people
started
to
react
on
it.
I
think
that's
something
we
should
be
doing.
C
Actually,
a
different
thought
on
that.
I
think
in
a
coffee
chat
with
him.
He
had
told
me
that
he
had
some
contacts
at
a
previous
company
that
you
that
heavily
uses
jenkins
to
leverage
him.
If,
if
I
wasn't
gonna
get
enough
response,
you
know
in
the
public
testing
issue.
Okay,.
B
I
do
have
one
meeting
with
a
tam
in
like
nick
after
30
minutes,
she's
the
only
one
who
accepted
the
invite
so
we'd
be
talking,
and
she,
let's
see
if
she
could
put
me
in
touch
with
another
customer.
C
C
C
C
Are
we
ready?
Are
we
done
on
the
discussion
about
jenkins,
wrapper
solution,
validation,
yeah,
you
know
so,
okay,
the
next
one
is
dad
feedback.
Is
yours.
B
Yeah
this
is
mine,
so
I
I
mean
I
spoke
with
rupert
today
and
clarified
a
few
things
like.
What's
the
compensation
we're
providing
and
how
should
I
go
about
it
so
taking
his
his
advice
and
what
you
laurie
and
I
had
discussed
in
the
previous
meeting,
I
put
this
message
in
the
dark
feedback
issue
tagging
everyone
who
has
commented
there
asking
them
to
fill
a
survey
and
six
of
them.
They
have
already
responded
to
the
surveys,
and
that
was
pretty
fast.
I
think
so.
Yeah
then
I'll
reach
out
to
them.
B
B
B
So
and
since
we
are
working
on
on
quite
a
lot
of
things
to
improve
the
pipeline
navigation,
so
I
think
a
really
good
opportunity
to
test
what
we
create
is
by
creating
is
by
conducting
a
scorecard
exercise
in
the
following
milestone,
which
is
13.5
so
that
we
can
also
in
a
way
gauge
our
user's
reaction
on
the
changes
that
we
would
make
in
13.4.
C
I'm
curious:
do
you?
Do
we
think
that
a
feature
delivered
in
13.4
will
users
will
have
an
opportunity
to
get
familiar
with
it
by
13.5?
I
remember
lori
a
while
back.
You
me
and
dimitri
were
talking
about
doing
surveys
with
users
after
about
features
that
had
been
released
two
milestones
ago,
so
that
we
were
confident
they
were
in
a
position
to
have
use
and
can
evaluate,
but
I
know
that
parent-child
pipeline,
oh
you're,
this
is
specific
to
navigation.
C
Like,
for
example,
with
with
what
you're
thinking
of
something
like
when
the
the
the
issue
we
delivered
in
the
last
milestone
of
hovering
over
a
downstream
would
show
which
was
a
triggering
job,
okay,
that
kind
of
right.
B
And
like
we
covered
a
good
portion
of
changes
in
that
issue,
but
there
are
a
few
things
missed
out
which
I'm
working
on
today,
in
fact,
so,
even
though
it's
scheduled
for
13.4,
because
I
have
time
I've
started
on
the
design
work
and
I
mean
yeah,
it
would
be
interesting
to
see
what
how
people
react
to
that.
Okay,
you
won't
find
people
who
would
be
who
would
get
familiar
with
it
so
soon,
but
if
not
exactly
those
small
parts,
the
13.4
parts,
but
what
we
have
delivered
in
the
previous
milestone
might
also.
C
Yeah
that
makes
sense
if
you're
limiting
it
just
in
the
navigation
experience
when
I
first
glanced
at
that,
I
thought
you
were
just
talking
about
around
parent
child
pipeline
as
a
whole,
and
I
wasn't
sure
if
some
of
the
pros
changed
in
13.4
is
to
help
with
authoring,
and
I
didn't
think
they
would
necessarily
be
re-authoring
some
of
their
pipelines
before
you
surveyed
them.
But
if
it's
around
the
navigation,
then
that's
that's
super
helpful
and
valid,
like
you'll,
be
able
to
there
it's
easier
for
them
to
be
in
position
to
comment
on
that.
D
D
It
is
important
to
align
on
the
goal
of
this
exercise
and
see
if
like,
if
the
scorecard
is
fitting
the
the
purpose,
but
it
sounds
like
it
is,
and
yeah
the
the
concern
that
tao
raised.
I
I
remember
we
have
been
talking
about
that.
We
are
trying
not
to
run
a
new
scorecard
on
on
features
that
we
that
have
been
created
in
one
or
two
maximum
milestones,
but
yeah.
If
this
is
about
the
validation
of
the
navigation,
I
think
that's
that
should
fit.
I
don't
know
what
lori
thinks.
C
Oh
yeah
yeah
yeah,
thanks
for
finding
that
link
nadia.
When
I
look
at
the
issue
now
the
jobs
to
be
done,
there
would
be
great
ones
to
validate
with
the
user.
B
B
D
This
is
exciting
cool
thanks
for
starting
this
video.
I
also
I
added
this.
I
assigned
this
issue
already
to
the
ux
scorecards
epic,
so
it's
already
there
so
just
for
visibility.
B
A
C
I
don't
have
anything
jason.
Might
I
actually
am
in
the
process
of
now
that
he
and
I
have
specific
buckets
by
topic
within
ci?
Well,
actually,
there
was
one
I
created
one
bucket.
There
was
one
bucket
that
was
really
big.
This
ci
interaction
bucket.
We
had
a
thousand
issues
in
it
still
and
I
was
trying
to
yeah.
I
know
have
you
all
seen
that
the
the
numbers
that
jason
shared
at
the
time
when
he
was
done
labeling
all
of
the
issues
in
order
to.
C
Let's
say
ci
issues
by
topic:
it's
actually
a
slack
message
that
he
gave,
but
if
you
go
to
that
slack
message,
you'll
see
that
oops
did
I
give
you
the
right
link.
Yeah
you'll,
see
that
I
think
the
the
one
that
I'm
trying
to
break
down
further
is
ci
interaction.
It
has
a
thousand
in
the
process
of
doing
that.
I'm
reading
through
each
of
the
issues
as
quickly
as
possible
and
I'm
finding.
There
are
certain
themes
in
there.
C
One
of
them
was
around
pipeline
graph,
so
I
created
a
new
label
for
pipeline
graph.
People
have
some
specific
input
on
how
they
want
the
graph
to
behave.
Yes,
usability
things,
and-
and
so
I
thought
that
might
be
a
research
we
want
to
do
in
the
future,
but
I
haven't
really
thought
out.
I
haven't
really
read
through
those
carefully
enough.
Let
me
see
if
you
I'll,
add
a
link
to
those,
but
the
problem
was
when
I
was.
C
I
guess
I
shouldn't
judge
the
importance
of
it
by
the
number
of
issues.
When
I
was
doing
that
exercise,
I
made
notes
to
myself.
I
carved
out
a
thing
for
python
ground.
There
were
only
36
issues
out
of
that
1009
that
had
specific
comments
about
pipeline
graph,
so
I
might
combine
it
with
another
topic
for
ci
analytics,
so
I
can't
decide
the
graph
you
would
think
graph
and
analytics
would
sound
like
they
go
together,
but
the
comments
about
the
analytics
was
really
metrics
that
they
wanted
to
see
as
opposed
to
visual
ux
ui
changes.
C
They
wanted
to
be
done
with
the
graph
so
sure,
and
one
of
those
yeah
and
one
of
those
areas.
I'd
like
to
do
some
research
jason
gave
me
a
good
idea.
Was
he
says
the
work
that
we'll
do
in
the
future,
with
with
reporting,
metrics
and
analytics
in
a
dashboard
are
things
that
a
higher
level
persona
like
a
higher
level?
I
mean
someone
who's
not
directly
working
with
the
pipelines,
things
they
would
be
interested
in.
That
would
be
valuable
features
we
can
put
in
ultimate
pricing
tier.
C
C
I
know
some
of
the
other
product
groups
are
building
out
dashboards,
but
none
of
those
are
going
to
be
specific
to
our
ci
metrics.
So
we
could
either
leverage
and
collaborate
with
them
and
not
reinvent
the
wheel,
but
I
haven't
evaluated
what
they're
building
and
it
may
not
be
exactly
what
we
want
to
present.
So
that's
going
to
be
I'm
going
to
guess.
We
want
to
evaluate
what
our
other
teams
are
doing,
probably
design
something
similar,
so
there's
a
consistent
user
experience,
but
something
entirely
different,
that's
specific
to
ci
analytics.
C
So
those
are
the
two
topics.
Unfortunately,
those
two
there's
right
now
from
as
I've
only
gotten
through
about
300
issues
of
that
one
thousand
and
I've
only
found
yeah
as
far
as
reading
through
them
as
quickly
as
possible-
mitigate
like
oh,
my
god,
but
of
those
300
that
I've
read
through
really
quickly.
33
were
about
analytics
and
36
about
pipeline
graph.
C
A
Sense
totally,
and
speaking
of
the
only
thing
I
am
not
clear
on
is
who's
starting
the
survey,
because
if
it's
problem
validation,
it
typically
sits
in
the
lab
at
the
pm,
but
not
that
we
can't
help
you
with
it.
A
For
the
jenkins
wrapper
the
one,
the
our
first
point
that
we
talked
about
earlier,
we,
I
suggested
a
survey,
but
I
don't
know
who's
putting
it
together.
If
it's.
C
F
A
A
And
I'm
happy
to
help
like
refine
and
and
stuff.
But
if
you
want
to
take
point
on
that
towel,
that
would
be
great,
then
I
can
help
refine
it
and
then
we'll.
Hopefully,
emily
will
see
her
pain
in
that
issue
and
she'll
be
able
to
tell
us,
because
social
media
people
have
things
that
they
are
doing
and
sometimes
they're.
Not
they
don't
time
or
something
comes
up
sometimes,
and
they
they
don't
push
things.
A
I
think
everything's
okay
right
now,
but
emily
would
know
so
much
more
she's,
so
much
closer
to
them
to
be
able
to
tell
us
about
like
their
bandwidth,
and
she
may
be
able
to
tell
us
about
rupert's
as
well,
but.
A
That
we've
built
this
thing
it
doesn't
have
to
be.
Those
were
just
that's
where
I
started
the
conversation
at
because
we
don't
know
if
anybody's
used
it,
and
I
don't
know
why.
So
one
of
the
questions
is,
do
you
even
know
it's
a
thing
and
how
would
they
have
known?
I
don't
know
so
for
people
who
don't
have
tams,
do
they
find
out
a
different
way
is:
was
there
a
blog
post?
Was
there
your
issue?
Did
they
just
not
see
the
issue?
A
I
don't
know
so
I
thought
that
would
be
a
good
place
to
start
and
then
we
could
ask
questions
based
off
of
their
answers
to
that
then
bethico
brought
up
competitors
because
I
didn't
know
circles.
Ci
github
were
doing
this
too,
so
I
feel
like
it's
an
opportunity
to
put
those
questions
in
the
survey
as
well
to
understand
like
well.
Okay,
maybe
you
haven't
heard
about
ours,
but
what
about
github
circleci?
A
A
F
A
A
C
A
A
I
don't
think
I
have
one
of
those
okay,
okay,
we
can't
ask
emily
emily
might
know
that
she's
usually
touching
all
of
the
surveys,
so
she
might
have
some
good
examples
that
she
could
share
with
you
in
quality.