►
From YouTube: CI PM:UX Check In on 2020-08-11
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
rcipm
ux
weekly
check-in.
The
first
agenda
item
is
our
usual
one
to
talk
about
the
planning
issue,
so
there's
a
link
to
it
there
before
we
go
there.
Let's
go
through
the
ish.
The
comments
that
victoka
has.
B
Yeah,
so
I
mean,
since
I
think
from
this
milestone,
we
wouldn't
be
using
this
epic
at
all.
So
I
wanted
to
know
like
what
was
the
expectation
that
tao
you
had
from
this
epic
and
if
that
would
be
fulfilled
by
taking
this
discussion,
that
happens
here
or
whatever
we
put
here
on
the
planning
issues.
A
So
I
really
had
no
expectation,
I
think
dimitri
originally
created
it
to
have
one
place
for
discussion
between
ux
researcher
product
designer
pm,
but
it
was
also
before
our
team
got
in
the
habit
of
using
a
planning
issue,
which
seems
now
that
there's
duplication
there,
but
he
did
make
a
good
point,
which
is
even
if
we
had
the
planning
issue,
that
each
planning
issue
is
specific
to
one
milestone,
whereas
the
purpose
that
dmitry
proposed
for
this
epic,
which
it's
across
milestones
to
capture
conversation
that
goes
beyond
specific,
milestone,
planning
and
milestone,
issue
implementation-
I
can
see,
there's
duplication
there,
so
I
don't
have
if
it's
helpful
to
ux
researcher
and
designer
to
have
it,
then
it's
great
to
keep
it.
B
Because
I
was
planning
that,
if
I
mean
the
discussion
in
the
planning
issues,
they
definitely
helped
because
the
larger
context
is
maintained
and
even
the
developers
are
part
of
the
conversation.
So
that
way,
I
think
we
are
sorted.
B
We
don't
explicitly
need
this
issue
to
have
those
conversations,
but
I
personally
wanted
to
have
like
one
place
where
I
could
go
and
keep
a
log
of
everything
that
I'm
involved
in
which
is
kind
of
getting
difficult
at
this
point,
especially
because
there
are
issues
on
which
I
don't
even
get
the
time
to
put
the
workflow
design,
because
it's
like
it
happens
as
a
part
of
a
conversation
on
an
issue
and
the
next
moment
the
workflow
ready
for
development
is
added,
so
there
will
always
be
certain
cases,
but
I
still
for
myself
need
to
have
a
place
to
go
and
look
at
if
I
want
to
refer
everything
that
I
have
worked
on
recently.
B
So
I
was
thinking
if
it
would
be
fair.
If
I
take
this
to
my
notion
doc,
if
the
team
doesn't
need
it
for
the
larger
discussion.
That's
that's
fine.
A
With
me-
and
I
agree
with
you
that
doing
the
you
kind
of
redirecting
our
discussion
to
the
planning
issue-
that
includes
engineering
as
well-
is
a
little
more
interactive
with
the
entire
team,
and
if
you
want
to
move
this
somewhere
else,
just
so
that
you
can
always
tr
have
a
overview
of
your
work.
That's
fine
with
me.
C
I'm
a
little
bit
cautious
about
moving
this
information
to
like
outside
of
gitlab
to
notion
because
it
will
be
only
accessible
to
you
vitica
and,
for
example,
I'm
also
I
could
be
the
user
of
that
for
sure,
and
also
if
you
will
move
this
to
notion,
we
will,
we
will
remove
other
people
from
contribution
and
participation.
C
This
kind
of
like
goes
against
the
gitlab
values,
so
I
don't
think
like
at
least
yeah,
I'm
usually
advising
against
using
any
other
tool,
because
we
have
gitlab
specifically
for
that
and
honestly,
as
we
early
earlier
discussed
with
qvt,
I
prefer
to
keep
this
epic
open.
I
think
it
adds.
It
obviously
adds
value
to
you.
It
adds
value
to
me
as
well,
because
I
can
see
the
cross
stage-
collaboration,
sorry,
not
cross
stage
but
like
cross
teams,
because
you
have
basically
two
pms
to
work
with.
C
I
think
in
your
case
specifically,
it
just
makes
sense
to
keep
it
to
keep
it
alive
and
to
like
use
that
as
a
planning
across
milestone,
but
also
across
pms.
I
don't
see
a
big
reason
why
we
should
why
we
should
close
this
issue.
To
be
honest,
I
think
it's
helpful
for
keeping
a
general
overview,
so
I
would
advise
to
reopen
it
to
be
honest,
okay!
Well,
what
are
the?
What
are
the
points
against
of
keeping
it
open,
because
it's
obviously
helpful
to
keep
an
overview
of
all
of
the
work?
A
Right,
I
probably
won't
use
it
as
much
for
discussions
about
things
in
a
milestone
because
I'll
do
it
in
the
planning
issue,
since
I
don't
because
I
don't
want
to
do
it
in
two
places
when
I'm
talking
about
a
specific
milestone.
A
So
this
and
one
thing
that
I
think
dimitri
was
doing-
that,
I
think
vitica
will
have
to
maintain
it's,
maybe
there's
a
more
efficient
way
of
doing.
It
is
updating
this
table
because
I
saw
vitoka
you.
You
noted
the
agenda
that
it
doesn't
exactly
reflect
what
you're
working
on
now.
It's
missing
a
few
things,
and
so
we,
I
don't
think
it
was
clear.
A
My
understanding
was
product
designers
is
maintaining
the
the
details
in
the
description
and
it
is
a
lot
of
copy
and
paste,
but,
like
maybe
you
can
just
use
a
link
to
a
filtered
list
and
you
make
a
list
where
it
dynamically
lists
this
all
out
for
you,
when
you
click
on
the
link,
so
you
don't
have
to
do
so
much
manual.
Make
not
maintenance
on
it.
C
B
Kind
of
stopped
updating
it,
because
I
mean
there
was
this
conversation
going
on,
so
I
did
not
know
if
we
are
still
doing
that
or
we
are
not
so.
I
mostly
just
participated
in
the
planning
issues
and
I
relied
on
the
labels
like
candidate
for
this.
This
milestone
those
things.
A
That's
interesting,
I'm
looking
at
jason's
comment
he
suggested
or
you
can
move
it
to
your
personal
project
or
something
similar.
I'm.
C
Afraid,
if
we
will
move
this
to
the
other
project,
the
links
will
not
work
and
honestly,
like
I,
don't
see
a
really
big
need
of
why
we
should
move
it
out
because
it
related
work
right.
It's
our
planning
issue
for
ux,
it's
very
similar
like
for
like
milestone
planning,
but
it's
on
the
ux
level
and
again,
especially
because
vehicle
works
for
the
2pm.
They
feel
it's
it's
it's
needed,
so
I
would
probably
propose
vitica
to
come
back
to
jason.
D
C
Ask
for
reasoning
why
we
should
move
that
and
if,
if
maybe,
if
he
would
agree
that
we
will
leave
it
as
it
is
right
now
and
give
it
a
try
for
another
few
months
when
we,
if,
if
we
will
say
that
okay,
that's
that's
not
necessary
or
we
can
find
another
way
to
to
do
the
planning
instead,
I
would
be
happy
to,
but
I
think
for
now
we
are
taking
usage
of
that.
C
We
just
need
to
keep
it
updated
and
that's
it,
and
if
you
need
any
help
with
updating
that
manually
or
or
more
dynamically,
you
can
talk
to
dimitri
because
he
is,
he
was
the
one
who
created
that
I
know
he's
keeping
the
he
is
actively
using
that
in
progressive
delivery
and
also
similarly
to
that
hayana
is
using
that
in
release
management.
So
all
of
the
most
of
the
other
stages
on
cicd
have
similar
practice.
So
why
would
we
get
rid
of
that?
If
we
also
feel
like,
we
need
that
right.
B
Sure
so,
let's
keep
that
open.
I'll,
have
a
conversation
with
jason
around
it.
A
I
went
ahead
and
just
reopened
it.
Okay.
I
I
and
I
know
working
with
two
pianos
be
the
couple
jason
and
I
interact
with
you
on
the
planning
issue
and
he
and
I-
and
he
probably
won't
be
interacting
with
you
on
this
issue
at
all,
since,
since
we
both
interact
on
the
planning
issue,
but
I
would
use
you'll
see
the
comment
I
just
said
per
discussion
at
this
weekly
meeting.
We
will
reopen
this
issue,
so
that
should
be
so
that's
there
for
you
to
use
yeah.
A
I
I
it
didn't
matter
to
me.
If
it's
useful
to
our
ux
folks,
then
then
it's
good
though
I
reopened
it,
okay
and
then
so
I
was
thinking
since
our
our
agenda
was
really
abbreviated
today
and
last
week.
If
we
wanted
to
move
to
alternating
weeks
with
ux
research.
That's
the
agenda
item
2
for
our
meeting
today,
because
I
was
thinking,
one
thing
is
is
vitica
and
I
because
we
we
want
to
have
time
really
for
maybe
more
actual
deep
dives
and
work
session
together.
A
We're
gonna
do
one
on
once
twice
a
week
and
I'm
gonna
guess
some
of
the
stuff
that
we're
gonna
discuss
will
probably
fall
off
of
this
agenda,
and
I
was
just
wondering
if
we
change
this
to
every
other
week.
Then
one
week
we'll
have
our
discussion
about
ux
research
and
then
one
week
we'll
have
this
check-in
meeting
any
thoughts.
A
Well,
we'll
still
have
the
the
weekly,
the
the
the
ux
dedicated
meeting,
but
I'm
wondering
this
slot
what
works
better
for
everyone?
If
we,
if
we
don't,
have
this
every
week,
it's
every
other
week,
then
we
still
have
this
time
reserved
on
our
calendar
to
move
the
ux
meeting
to
this
time.
A
Okay,
that
work
okay,
so
I'll
I'll
adjust
the
meetings
after
this
session,
where
this
one
will
will
so
next
week,
it'll
be
a
ux
research
topic
and
then
the
following
week,
two
weeks
from
today
will
be
pm.
Ux
weekly
check-in
or
it
won't
be
weekly
check
in
anymore
it'll
just
be
check-in
because
it's
not
weekly,
okay,
hey
on
a
separate
topic.
I
forgot
to
add
it
to
the
agenda
here.
I'll
add
it.
I
was
asking
jason
of
a
question
that
came
up
at
our
last
week's
ux
research.
A
A
So,
and
maybe
I
need
a
specific
section
in
the
direction
page.
Let
me
go
find
the
direction
page
I'll
link
to
it.
I'll,
add
it
to
the
agenda
because
in
his
mind-
and
I
haven't
been
doing-
maybe
referring
back
to
every
referring
everyone
back
to
the
page
as
often
as
I
should.
Let
me
add
it
here
to
the
direction.
A
Page,
so
that's
and
this
is
specific
to
ci
direction
page.
A
So
what
we
want
to
do-
and
I
wanted
to
ask
laurie
really
if
it's
even
helpful,
is
there
are
specific
sections
here
what's
next
and
why,
which
is
very
specific
to
the
upcoming
milestone
but
down
to
top
vision
item.
D
Well,
here's
the
thing
that
I've
experienced
with
other
groups
is
that
today
august
11th,
they
may
think
like
three
things
need
research
tomorrow,
august
12th,
those
three
things
might
change.
So
I
what
I
just
typically
tell
my
pms
is
just
open
a
research
issue,
ping
me
on
it.
That's
that's
the
system
I
work
in.
I
don't.
D
I
will
bookmark
this
page.
I
will
put
it
in
my
bookmarks
in
my
my
browser,
but
I'm
not
sure
if
I
would
come
back
and
check
this
to
see
what
right
should
be
focusing
on.
So
I
don't
mind
that
you
put
it
here,
but
that's
not
where
I
would
go
to
look
at
things
or
go
to
have
a
conversation
with
you
and
bethica
about
okay
thanks,
but
maybe
that's
just
me
like.
I
can
change.
A
Sorry-
and
I
I
I
probably
communicated
that
poorly,
I
meant
it
would
be
one
place
that
we
go
to
at
our
every
other
weekly
every
other
week,
meeting
to
say:
okay,
this
is
what
I
just
added
to
my
direction
page
and
here's
a
link
to
a
a
research
issue
that
has
something
to
do
with
this
thing.
That
is
in
the
direction
page.
So.
D
A
But
I
I
totally
agree
with
you
for
anything
I
want
to
talk
about
for
research
upcoming.
There
should
be
a
ux
research
issue
and
then
we
can.
That
will
be
the
starting
point
of
having
that
conversation
in
that
issue.
Yeah
and.
D
I
will
tell
you
that
the
research
issues
until
the
research
is
done.
We
are
keeping
them
confidential
because
we
don't
want
any
of
our
potential
users
or
customers
to
go
and
find
them
and
read
about
them
and
bias
themselves,
especially
sometimes
in
our
screeners,
we'll
ask
some.
I
mean
if
you're,
just
happily
intelligent,
you'll
know
what
we're
going
to
be
talking
about.
D
A
Okay,
gotcha,
that
is
everything
under
the
actual
ux
research.
D
A
Okay,
you
know,
let
me
go
to
the
top
of
this
direction
page
because
it
links
to
a
research.
That's
been
closed,
but
okay,
interesting
it
links
to
an
epic
I'll,
probably
need
to
update
that.
This
is
kind
of
old,
just
verify
this
privilege
to
keep
track
of
ux.
We
should
conduct
and
verify
error
so
that
we
can
iterate
continue
explore.
A
Okay,
well,
that
one's
closed
okay.
That
sounds
good.
I
wonder
if
it
makes
sense,
it
looks
like
originally
katherine
had
a
research,
an
epic
under
the
ux
research
project,
under
which
we
would
link
to
any
individual
research
issue.
Do
would
that
be
helpful
for
us
or
do
any
other
groups
do
that
laurie?
D
No,
I
think
tal
I
feel
like
kali
tried
that
too,
I'm
not
sure
does
that
one
look
like
it's
still
active,
I'm
not
sure
if
cather's
still
doing
that
or
not
it's
closed.
Okay
yeah.
I
think
we
all
tried
some
stuff
right
now
and
then
to
see.
What's
going
on,
we
have
our
own
research
board
that
you
can
find
wherever
the
boards
live
for
the
research
team.
So
that's
how
I
keep
track
of
what
I'm
I'm
assigned
to.
D
A
Well-
and
that's
and
that's
perfectly
fine
with
me,
but
I'm
curious:
how
would
you
even
make
it
unconfidential
if
it's
if
the
entire
ux
research
project
is
internal
access,
only
it's
not.
D
A
Oh
okay,
I
thought
I
misunderstood
you
earlier
when
I
was
saying
okay,
so
the
issues
that
are
individually
made
at
confidential
until
we're
done
with
that
research.
Yes,
okay,
okay,
yeah,
that's
fine
with
me!
If
I
I'm
is,
can
I
I
guess
I
could
just
use
the
labels
to
create
a
board
of
my
own
unless
there's
a
board
that
is
commonly
used?
A
Are
you
talking
about
a
board
you
crave?
Just
for
yourself
of
you.
D
A
A
Okay,
all
right!
That's
all
I
have
for
today
I'll
go
back
viteka,
maybe
at
our
101
on
thursday
we
can
make
sure
that
that
ux
review
epic
is
has
all
of
is
updated.
If
you.
B
A
I'll
check
out
there's
no
hurry
I'll
check
before
we
get
together
on
thursday,
okay
and
and
then
I
think,
on
thursday,
oh
so
just
to
update
nadia
and
lori
on
thursday
we're
gonna
do
every
time
I
do
a
kickoff
video
is
something
slightly
different.
The
first
one
I
did
was
me
and
v
with
dimitri
speaking
viticus
sitting
in
on
it
the
second
time
it
was
just
me
and
vitika
this
third
time
we'll
be
recording
this
thursday
will
be
me.
A
Vitica
and
jason,
so
it'll
be
a
three-person
discussion
of
the
the
the
scope
of
13.4
and
we're
doing
it
early
since
friends
and
family.
It's
the
normal
date
is
due
on
the
16th,
which
is
sunday
we're
all
out
on
friday.
So
so
look
forward
to
that,
and
so
I
was
thinking
vitica
right
after
that
meeting.
I
can't
remember
if
you-
and
I
are
our
sync
is
before
or
after
that,
but
maybe
we
can.
I
was
thinking
this
thursday.
We
can
talk
about
13.5,
sure,
yeah,.
B
A
Our
her
session,
that's
on
our
session,
you
and
I
are
getting
together
after
that.
I
think
there
are
some
things
that
are
not
going
to
make
it
into
13.4
that'll
be
for
13.5
and
then
there's
a
couple
other
things
I
wanted
to
run
by
you.
If
you
had
we'll
talk
about
it,
then,
okay,
okay,
anything
else,
folks,
all
right
I'll,
stop
the
recording.