►
From YouTube: CI PM/UX Research Planning on 2020-09-02
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
Okay,
welcome
everyone
to
our
bi-weekly
ci
pmux
research
planning,
meeting,
welcome,
jason
and
dove
and
nadia.
We
got
to
meet
last
week
and
so
dove.
Maybe
at
the
end,
when
the
rest
of
us
joined,
you
can
tell
us
a
little
bit
about
yourself.
Now
turn
the
recording
off
for
that
so
first
agenda
item:
it's
kind
of
gonna
be
like
this
week.
First
agenda
item:
do
you
wanna
walk
through
those
yeah
sure.
B
So
I
mean
lately:
I've
realized
that
if
we
compare
our
research
efforts
to
the
issues
that
we
are
working
on
and
how
much
we
are
delivering
it's,
it's
kind
of
the
ratio
has
shifted
and
we
are
doing
very
less.
We
are
spending
very
less
time
on
researches,
so
I
mean
once
we
have
the
responsibilities
divided
between
the
teams.
B
We
should
really
look
at
what
are
the
topics
that
we
could
kick
off?
Research
on
for
the
upcoming
milestone,
because
right
now,
there's
I
mean
from
the
top
of
my
mind.
I
don't
have
any
concrete
idea
about
what
we
should
be
looking
deeper
into
so
just
wanted
to
bring
it
to
everybody's
notice
that
we
should
start
thinking
on
these
lines
and
maybe
line
up
a
couple
of
validation
exercises
or
some
other
research
that
we
need.
A
Hey
so
on
that
vein,
by
the
way
I
do
have
talked
about
something
similar
in
general
item
two,
but
one
thing
I
thought
about
is
we've
never
done
this,
but
a
while
back
laura
and
I
talked
about.
Do
we
want
to
do
research
about
or
even
if,
it's
just
a
survey
of
the
features
that
we
recently
released,
that
we
haven't
followed
up
with
users
on.
A
Obviously,
we
followed
up
with
the
dag
visualization,
but
there's
other
features
that
we
release
that
I
don't
think
we've
ever
systematically
done,
surveys
to
users
after
a
month
or
two
when
something's
released,
and
we
can
maybe
look
at
that.
You
know.
A
Because
sometimes
we
had
to
in
the
entrance
of
narrowing
it
down
to
something
really
small
for
the
first
iteration.
We
release
the
something
that
we
know
is
not
complete
and
then
there's
a
bunch
of
different
directions.
We
could
take
it
and
laurie
and
I
had
talked
about
well.
We
won't
really
know
what's
the
best
next
thing
or
what
the
most
wanted
next
thing
would
be
unless
we
kind
of
hear
get
some
feedback
on
that.
A
So
I
could
look
with
you
on
the
ci,
inter
interaction
ones,
and
we
can
maybe
find
one
or
two
that
we
want
to
follow
up.
I
don't
know
the
best
way.
I
think
lori
and
I
have
talked
about
maybe
doing
a
survey
instead
of
doing
live
interviews,
but
maybe
some
of
them,
you
may
think,
deserves
a
live
interview,
because
the
next
iteration
has
things
we
want
them
to
look
at
and
get
their
reaction
live.
B
In
fact,
this
reminded
me
of
something
else
I
was
thinking
since
we
are
working
on
this
very
new
effort
of
providing
a
visualization
for
the
yaml
file,
and
we
had
a
very
good
experience
with
the
link
that
we
provided
with
the
mvc
release
of
dag.
So
should
we
do
something
similar
for
that
as
well?.
A
B
I
I
mean
at
whichever
stage
you
would
want
to
put
put
it
there,
maybe
with
the
visual
builder,
if
you
want
people
to
have
a
look
at
the
broader
concept
and
then
give
their
inputs.
That's
also
fine
with
me.
A
Gotcha
yeah,
I
hadn't
thought
I
didn't
realize
you
meant
that
at
the
beginning,
but
that
would
make
a
lot
of
sense
because
we
can
get
feedback
on
the
what
we're
releasing
in
13.4
and
then
get
some
additional
feedback
on
on
the
behavior
with
the
when
it
becomes
a
builder
yeah,
an
editor
yeah.
That
would
be
really
good
because
that's
a
that's
a
there's,
a
lot
more
work,
that's
gonna!
A
Even
to
see
if
it's
intuitive
to
them
that
we're
probably
going
to
not
build
it
out
in
the
simple
file
editor,
but
go
with
the
the
web
id
yeah
yeah.
I
think
that's
a
great
idea
as
as
a
neck
one
of
the
next
research
projects.
C
I
added
one
there
for
vita.
You
showed
us
that
link
yesterday,
I
think
it
was
on
the
snippets,
catalog
and
template
viewer.
We
might
be
able
to
start
research
on
that
now,
for
when
we
finish
the
visual
builder,
we
can
kind
of
have
that
ready
to
go
and
roll
right
into
it.
I
was
also
just
going
to
do
a
search
for
there's
issues
out
there
that
have
like
the
problem-
validation,
labeled.
D
D
C
Yeah,
there's
13
open
ones
that
are
just
all
on
schedule.
That
might
be
worth
looking
at
one
here.
C
A
I
don't
think
we
ever
could
what
I
think
the
research
was
done
on
the
public
pipeline
page,
but
I
might
have
to
close
it
out.
C
Not
very
much
interesting
here
I
mean.
Maybe
there
is
but
nothing
that
jumps
out
as
being
like
really
interesting
solution,
validation.
We
have
the
feedback
for
the
dag
in
solution
validation,
so
that
needs
to
get
wrapped
up.
Maybe
you
already
had
that
therapy
jenkins
wrapper
solution,
validation.
I
don't
know
that's
probably
on
hold.
D
C
Is
it
on
the
agenda
already
if
it's
already
on
the
agenda
somewhere
else
again.
A
It's
not,
and
I
think
it
was
I
think
we
had.
The
thing
was
the
last,
maybe
a
couple
of
months
ago
we
had.
You
can
remind
me
if
I'm
saying
that
correct
we
thought
about
maybe
going
back
and
doing.
A
We
made
some
assumptions
because
we
had
to
to
deliver
the
mvc,
and
so
we
thought
maybe
we
need
to
go
back
and
do
the
problem
validation
on
that,
because
we
yeah,
because
we
kind
of
feel
like
we
don't.
We
do
know
the
problem,
but
that
was
based
on
feedback
from
our
internal
team
members
based
on
their
discussion
with
prospects
and
customers
and
thought.
Maybe
we
should
just.
C
We
didn't,
but
we
were
going
so
we
didn't,
because
we
just
had
direction
from
the
leadership
team
to
just
go,
build.
D
C
But
then
we
built
it
and
it
seemed
like
nobody
wanted
it.
So
the
research
that
I
thought
we
were
doing
was
to
go
back
and
see.
If
actually
anybody
wanted
anything
at
all.
D
C
Which
isn't
necessarily
to
do
like
go
back
and
redo
problem
validation?
It's
just
see
if
this
was
just
like
kind
of
like
a
misunderstanding
in
the
first
place,
because
it
was
if
we
never
did
problem
validation,
we
just
sort
of
like
no.
We,
you
know
we,
as
the
leadership
team,
know
that
this
is
important,
so
just
go.
Do
it.
E
With
this,
oh
go
ahead,
laurie,
sorry!
Well,
it's
okay
yeah!
So
it
is
kind
of
like
problem
validation
because
they
assumed
that
that
was
going
to
solve
the
problem.
So
now
we
have
to
figure
out
what
is
actually
the
problem
that
needs
to
be
solved
and
find
out
a
little
bit
more.
We
were
hoping
to
talk
to
people
who
were
using
it
or
or
should
have
used
it,
but
I
I
know
vethika
and
tao
were
trying
to
find
them
and
I
was
too
and
we
couldn't
find
anybody
to
talk
to.
C
E
Right
exactly
so,
you
know
that's
a
good
hypothesis
to
go
with
documentation.
Just
should
be
enough.
We
need
to
figure
out
what's
missing
in
there,
that
we
could
fix
but
yeah,
so
that
definitely
does
need
to
be
touched.
C
Okay
did:
did
we
ever
go
back
to
the
leadership
team
and
say
that
we
can't
find
anybody
who
actually
wants
this
thing
we
built.
A
We've
said
that
before
where
I
wasn't
getting
any
feedback
on
participating
in
the
public
issue
for
feedback
on
the
wrapper.
But
I
haven't
gone
back
and
and
since
that
time
that
update
and
said
it
again.
C
Yeah,
we
probably
need
to
if,
if
we
so
it's
been
like
a
month,
I
think
or
two
even
since
we
started
the
second
round
of
research
for
okay.
If
there's
still
nothing,
then
yeah
just
get
get
an
update
to
kenny.
When
he's
back,
and
let
him
know
that
yeah
we
did,
we
did
two
more
months
of
research
and
didn't
figure
anything
out
and
we
can
share
the
research
that
we
got
did
over
the
last
two
months
again
and
which
is
that
we
couldn't
find
anybody
who
was
interested
and
yeah.
C
Then
he
can
go
update
and
just
say
like
hey.
This
doesn't
seem
like
what
we
wanted.
People
do
still
want
to
migrate
from
jenkins
to
gitlab,
so
we
have
to
figure
that
out,
but
like
it's
not
this
thing
that
we
built.
Nobody
wanted
that.
A
A
No
worries
I'll,
oh
okay,
never
mind!
Someone
threw
that
your
notes
at
the
bottom
there
on
number
six.
Okay,
do
you
nadia,
I
think
you've
already
gone
for,
do
we
feel
like
we
need
anything
for
13.6?
I
I
haven't
gotten
that
far,
not
yet
13.6,
but
I'll.
Look
at
it.
I'm
trying
to
finish
my
13.5
issues
for
13.5
this
week,
although
that
may
lead
into
what
I
want
to
ask
about
for
for
number
two.
But
do
we
want
to
go
to
viticus
point
one
b?
B
Sorry,
which
was
that
point
so
point
b,
was
just
about
tracking
the
progress,
but
I
think
we
just
talked
about
everything,
that's
in
progress,
so
for
that
I
have
interviewed
about
eight
people
just
that
these
two
weeks,
I'm
too
busy
taking
care
of
the
milestone
work.
I
couldn't
get
myself
to
do
the
analysis.
I
would
do
that
and
we
just
discussed
about
what
we
would
do
for
the
jenkins
problem:
validation,
yeah.
I
think
that
that
should
be
yeah.
A
Okay,
all
right
so
agenda
item
two
one
of
the
things
that
pm's
are
being
asked
to
focus
on
this
prioritize
issue
for
usability
improvements,
and
I
went
out
there
for
my
feature.
A
Labels
and
I
searched
on
the
ux
label
and
then
later
I
also
searched
on
the
ui
polish
and
the
the
the
ux
debt,
and
I
I
got
back
so
many
issues
that
I
I'm
not
quite
sure
where
I
want
to
focus
this
and
I'm
gonna
try
to
figure
out
a
few
topics,
and
I
just
wanted
to
throw
it
out
there
for
all
of
us
to
think
about.
I
know
that
here
we
don't
have
to
decide
today,
but
I
I
I
think
it
would
help
to
get
feedback
from
all
of
you.
A
Well
how
we
want
to
refine
the
scope
of
what
we
want
to
focus
on
for
usability
research,
because
because
ci
as
a
topic
is
so
broad,
I
thought
maybe
looking
at
purely
the
things
that
are
very
visual,
that
the
the
user
interacts
with.
So,
for
example,
looking
at
things
we
can
improve
in
the
pipeline
graph
topic,
what's
displayed
on
the
pipeline
page
as
opposed
to
ruling
out
my
other
topic
areas
like
api
interactions,
ci
processing,
which
is
behind
the
scenes
and
not
visible
to
the
user.
A
I
mean,
and
then
I
thought
well,
that's
kind
of
obvious,
but
but
there
are
things
in
ci
processing
that
affects
the
what
the
user
sees.
So
the
the
ci
processing
issues
include
things
that
determine
statuses
and
things
like
that
that
they
see
so
anyways.
What
I'll
do
is
async
I'll,
come
up
with
a
couple
topics
and
throw
it
out
there
and
we
can.
We
can
decide
what
might
be
one
or
two
we
want
to
pursue,
and
I
created
a
research
issue
for
it.
C
A
A
B
Think
so
I
asked
this
question
a
couple
of
days
back
when
nadia
pointed
out
that
about
the
misplaced
play
icon
in
our
pipeline
graph,
so
yeah
I
mean
it
would
help
us
a
lot
if
we
can
get
some
telemetry
data.
But
at
this
point
I
think
there's
something
underway.
I
mean
some
effort
who
won't
share
that
with
me.
I
can
post
it
here.
I
can
look
for
that,
but
there's
nothing
at
the
point
which
is
working.
A
Hey:
hey:
hey
dove!
What
what
the
word
telemetry
it
kind
of
means
a
couple
different
things
to
me:
what
do
you
mean
when
you
say?
Are
you
meaning
clicks
on
buttons,
for
example,
or.
A
C
Times
different
pages
are
loaded
and
things
like
that,
and
it's
fairly
obvious
even
within
ci,
you
know,
which
pages
are
the
ones
that
people
use
the
most.
So
if
it's
more
like
we
it's,
I
don't
think
it's
that
we
don't
know
what
people
are
using
in
ci.
C
We
know
the
pages
and
workflows
that
are
the
most
common
ones
and
but
yeah
figuring
out
what
the
best
ux
improvement
is
to
make.
I
don't
think
counts
of
button
clicks
and
things
like
that
will
help
us,
but
popular
issues
tend
to
especially
for
like
really
egregious
ux.
Problems
tend
to
get
a
lot
of
up
votes,
so
they
may
bubble
to
the
top
of
each
of
the
topic
areas.
That's.
D
It
sounds
like
a
good
place
to
start
and
also
jason.
You
mentioned
that
we
know
that
the
most
popular
user
flows
or
the
most
popular
features.
Maybe
we
could
run
an
evaluation
on
that,
like
defining
the
main
jobs
to
be
done.
That's
pretty
similar
to
the
main
user
flows.
As
you're
saying
we
could
run
the
evaluation
of
experience
like
using
the
ux
scorecards
there
or
if
you
have
already
some
inputs
in
the
issues.
Like
the
like
what
you
jason
said,
we
have
a
lot
of
customer
attention
to
a
certain
feature.
D
D
Yeah,
I
can
imagine
that
we
will
have
a
couple
of
those
items
because
yeah
is
pretty
wide
and
so
popular.
Maybe
we
would
want
to
each
bring
up
a
couple
of
things
or
a
thing
and
then
run
a
voting
exercise
or
something
like
that
to
define
the
one
to
have
a
look
at
to
build
there
to
build
a
backlog
of
those
priorities
that
we
would
wanna
improve
for
the
user
experience.
C
D
Yeah
one
thing
that
kind
of
worries
me
looking
at
the
amount
of
issues
we
often
talk
about,
like
also
looking
at
the
amount
of
issues
that
vidiq
is
currently
busy
on.
I
think
we
would
need
to
be
a
bit
better
in
the
prioritization
as
well
to
make
sure
that
we
do
a
good
job
at
defining
the
priorities
like
which
items
we
need
to
look
at
and
focusing
a
bit
better
to
make
sure
that
we
are
not.
A
C
Mean
those
are
ux
necessarily.
A
Yeah
yeah
yeah,
and
it's
not
any
one
issue
that
I
want
to
focus
on.
It's
just
trying
to
figure
out.
What
is
the
theme?
Let's
say:
10
of
them
is
about
the
interaction
with
the
pipeline
graph.
Then
then
yeah,
then
that
would
be
you
know,
pipeline
graph
pain.
Point
research
is
what
it
would
be
I'll.
Look
at
that
thanks
for
the
just
it
was
so
obvious,
but
thanks
just
to
help
me
focus
just
to
go
off
of
popularity.
B
B
A
F
I
also
wanted
to
just
ask
if
any
of
you
are
aware
of
any
research
issues
or
like
research
inside
epics
that
are
related
to
ci
authoring
that
dove,
and
I
could
have
a
look
at
to
just
learn
more
about
the
user
and
the
products
you
know
just
consume.
Whatever
insights
that
we
have
please
just
let
me
know
you
can
ping
me
on
slack
or
link
it
here.
If
you
have
any
pointers.
B
I'll
post
the
link
here,
we
usually
have
all
the
links
in
our
ci
ux
epic
itself.
The
research
exercises
which
are
ongoing,
yeah.
F
A
We
can
reach
out
to
dimitri
to
see
if
he
recalls
any
too
and
then
we
could
just
maybe
just
do
in
the
in
the
ux
research
project,
I'm
not
sure,
but
we
can
go
search.
I
will
look
right
now,
search
on
the
ci
group,
ci
label
in
case
dimitri
applied
that
label
and
find
them
that
way.
E
A
Listed
that
was
listed
just
for
everything
just
before
we
started
using
dovetail
lori
right,
yeah
yeah,
yeah
yeah.
I
don't
think
anything's
happened
related
to
ci
authoring
after
that,
since
we
started
using
dovetail
nadia,
so
whatever
you
might
find
there
does
anyone
can?
If,
if
I
I
forget
that
that
readme
file
is
out
there,
if
anyone
can
add
the
link
to
that
in
the
agenda
when
they
get
a
chance,
I'd
like
to
look
at
that.
D
C
Was
read
only
number
six
how's,
the
ci
use
case
research
going.
We
had
to
kick
off
recently
what
it,
what
what's
next.
C
E
It's
what
I'm
doing
is
the
adoption
journey.
Like
oh,
that's,
a
different
word.
It's
going,
it's
going.
I
had
some
time
off
and
andre
kept
pushing
forward
for
me.
While
I
was
gone,
I
just
started
the
screener
for
both
the
non-engineering
technical
user
and
the
non-web
app
developer,
so
I
obtained,
I
think,
I
think,
jason,
both
you
and
tao
in
that
issue.
So
if
you
guys
get
a
moment,
please
look
at
those
screeners
because
I
feel
like
you
guys,
would
be
able
to
pick
up
one
more
opportunity.
E
Like
maybe
some
questions
I
should
be
asking
or
some
answers.
I
don't
have
there
for
people
to
choose
from
so
as
soon
as
we
get
that
I'll
start
working
with
emily
to
get
people
recruited.
So
the
goal
for
that
is
that
persona
piece
of
the
project
to
understand
more
about
these
two
types
of
people
who,
from
everybody
we
talked
to
stakeholders
all
said,
we
don't
really
do
a
good
job
understanding
what
their
needs
are.
So
we
want
to
understand
what
their
needs
are.
E
He
teamed
you
on
a
couple
of
things
and
you
guys
have
talked
about
it
and
he's
also
taking
point
on
what
we're
terming
the
literature
review,
which
is
also
looking
at
past
research
as
well
as
forester
articles
and
other
things
out
there
to
understand
what
ci
dot
ci
adoption
looks
like
everywhere
else
and
and
how
we
might
be
able
to
apply
those
definitions
to
how
we
define
it,
because
everybody
had
a
different
definition
when
we
talked
to
them
different
start
point:
different
endpoint,
different
success,
metrics.
E
So
he's
going
to
take
point
on
that
and
I'm
going
to
assist
him
with
that
and
then
always
forgiveness
of
the
other
piece.
So
we're
we're
working
on
it.
It's
getting
it's
getting
worked
on.
C
When
will
the
next
milestone
be.
E
As
soon
as
we
have
something
to
share
so,
hopefully
I
can
get
my
people
scheduled
for
the
persona
research
and
then
I
can
do
that
and
have
something
to
share,
but
I'm
not
sure
how
long
how
hard
it
will
be
to
find
the
non-engineering
people,
because
we're
talking
scientists
and
researchers
and
product
managers
and
project
people
so
we'll
we'll
see
because
they'll
have
to
be
somebody
who's.
E
I
think
interest,
maybe
not
interested
in
ci
but
like
they
could
use
it
if
they
knew
what
it
was.
So
those
people
might
be
harder
to
find.
I
think
the
non-web
app
people
won't
be
that
much
that
hard
to
find.
We
just
need
to
give
them
so
we'll
see,
and
then
andre-
and
I
talked
yesterday
about
the
data
piece
of
it
so
he's
going
to
work
on
outlining
our
his
approach
like
these
are.
E
A
Hey
lori,
I'm
looking
at
the
the
research
plan,
that's
linked
to
the
research
issue
or
linked
from
the
research
issue.
It
was,
I
I'm
not
sure,
maybe
and
dre
was
one
who
put
this
in.
It
was
interesting
that
one
of
the
things
the
questions
for
the
data
analysis
section
is
analyzing
why
potential
users
are
not
adopting
ci
because
they
have
a
hard
time
migrating
from
other
tools,
and
so
it's
broader
than
just
jenkins
you're,
going
to
look
at
jenkins,
travis
ci
circle,
ci
and
stuff,
but
it
would
be.
A
It
would
be
interesting
to
find
that
and
one
of
the
notes
there
was
what
number
of
projects
I
guess
in
gitlab
dot
com
uses
other
tools
for
ci.
I
might
be
able
to
help
with
that.
I
was
trying
to
do
that
analysis.
C
A
The
data
that
we
have
in
order
to
get
those
numbers-
it's
not
perfect
data,
but
circle
back
with
me
on
that,
because
I'm
I'm
trying
to
figure
that
one
out
too
getting
data
for
a
number
of
projects
on
getlab
ci
gitlab.com
that
uses
other
ci
tools.
Yeah.
E
Oh
cool,
please
ping
him
in
the
issue
tile
because
I
know
he's
he's
really
keen
on
talking
about
that.
So
yeah.
A
A
Okay,
I
think
we're
at
the
end
of
our
agenda
was
there
anything
else.
Folks
wanted
to
talk
about?
Oh
vitica,
did
you
want
to
verbalize
your
note.
B
It's
just
a
link
that
I
added
for
my
it's
around
the
conversation
that
I
had
with
bill.com
about
the
same
jenkins
solution
that
we
provided.
So
there
could
be
some
insights
that
could
be
found
from
here
as
well
like
why
they
did
not
go
for
that
solution.
A
So
so
build.com
for
folks,
who
don't
know
build.com
and
it
might
have
been
verizon-
were
the
two
existing
customers
that
our
technical
account
manager
found
that
were
willing
to
participate
in
in
testing
out
the
jenkins
wrapper,
and
I
actually
don't
recall
that
the
verizon
contact
did
any
testing.
I
think
build.com
was
the
only
one
right
after
we
delivered
the
wrapper
that
had
someone
who
actively
used
it
and
tried
it.
B
Yeah
she
mentioned
okay,
I
need
to
check
my,
but
there
was
an
issue.
I
remember
where
people
had
shared
their
experience
with
the
two
so
I'll
find
finally
updated.
A
Yeah,
I
think,
we're
over
time
and
we're
at
the
end
of
our
agenda
thanks
everyone
I'll
upload
this
to.