►
From YouTube: CI PM:UX Weekly on 2020-08-26
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
Hi,
everyone
welcome
to
our
week
our
bi-weekly
cipm
ux
check-in
and
welcome
nadia
to
our
your
first
meeting
with
the
ci
team
me.
A
Let
me
I
I'm
having
a
problem
opening
the
the
agenda,
doc.
A
Okay-
I'm
probably
I
don't
know,
maybe
know
she
better
than
I
do.
I
haven't
had
a
chance
to.
We
had
to
reschedule
our
coffee
chat
yesterday,
and
so
I
would
have
known
this
already,
but
can
you
tell
me
a
little
bit
about
yourself
and
then
and
then
the
rest
of
us
can
tell
you
a
little
bit
about
ourselves.
B
Yeah
sure
well,
I'm
based
in
warsaw,
poland
and
I've
been
at
git
lab
for
almost
a
year
now,
it'll
be
a
year
at
the
end
of
september,
and
I've
been
working
on
the
monitor
apm
team,
mostly
focusing
on
metrics
dashboards
yeah,
I'm
very
excited
to
be
joining
your
team.
I
know
pretty
much
well,
I
know
almost
everyone
actually
had
a
chance
to
meet
quite
a
few
of
designers
from
the
ci
team
in
person.
B
A
Yeah,
I'm
excited
you're
on
the
team.
I'll
tell
you
real
quick
about
myself,
so
I
joined
get
lab
last
year
in
october
end
of
october,
so
not
quite
a
year
yet,
and
I
had
a
a
a
little
bit
of
context,
switching
on
which
team
I
was
working
on.
I
was
going
to
work
on
another
team
that
actually
I
came.
A
It
ended
up
not
getting
funny
and
came
back
to
ci,
so
I've
been
with
ci
since
march,
and-
and
I'm
super
excited
that
you
mentioned
having
worked
on
dashboards,
because
I
just
recently
looked
at
some
issues
that
have
the
ci
label
for
graphs
and
analytics
and
trying
to
think
about
how
we
can
dashboard
some
details
about
pipelines
that
could
be,
for
we
don't
have
a
lot
of
features
in
ultimate
premium
tier.
So
we
can
talk
more
about
that.
You
already
know
vitica.
Are
you.
A
All
right
so
going
to
our
agenda.
Let's
take
a
look
at
the
agenda
item
two
there,
the
ux
needs
epic.
A
A
I
think
that
oops,
we
should
probably
start
I'm
not.
I
have
not
been
referring
to
this
as
much
as
I
should
as
the
source
of
truth
of
what
really
is
in
flight,
because
I'm
going
issue
by
issue,
but
it's
probably
better
for
us
to
do
that
exercise
in
this
meeting.
Can
you
see
my
screen
yeah.
C
I
can,
and
I
totally
agree
with
you
because
yeah
I
have
been
pushing
this
a
little,
because
I
myself
I'm
very
lost
between
like
what
I'm
working
on
and
the
issues
on
which
I
had
to
assign
myself
and,
at
the
same
time,
after
a
couple
of
comments,
I
had
one
assigned
myself,
so
I
didn't
know
what
to
do
with
those.
A
Yeah
agreed-
and
sometimes
it's
hard
for
me,
especially
with
tables
I
get
lost
in
the
tables
themselves
when
I'm
editing
them.
So
I'm
going
to
open
this
side
by
side,
so
we
can
see
the
table
and
then
also
in
the
editing
view,
okay,
so
on
the
design
work
on
the
design
work,
I'm
gonna
skip
through
all
that
we
probably
need
to
clean
some
of
this
up
so
on
the
visualization
it
is
first
strap.
C
A
A
A
Make
what
web
ide
the
preferred
experience
for.
I
let
me
check,
but
I
think
jason
made
this
a
13.5
candidate.
C
A
C
C
I
think
when
he
comes
back
and
the
reason
he
pushed
this
to
13.6,
because
sarah
said
that
she
could
only
work
on
the
first
one
by
13.5.
A
Okay,
all
right,
then,
for
our
purpose,
I'll
just
put
13.5
for
now,
all
right
explore
pipeline
grab.
First
draft:
this
is
still
back
long.
Okay,
so
that's
accurate
and
then
improve
navigation.
This
one
should
be
13.4.
A
All
right,
let
me
copy
this
to
make
it
quick,
let's
just
copy
and
edit
it.
A
C
And
then
there
are
a
couple
of
issues
on
which
I
only
had
to
put
like
one
comment,
because
those
were
mostly
around
ci
rules,
so
I
just
suggested
if
we
could
use
these
two
words.
It's
instead
of
this
one
word,
so
I
am
not
really
putting
those
here.
A
A
Let
me-
but
this
is
after
the
issue
is
closed
and
not
when
the
design
is
done.
So
all
of
these
are
correct.
None
of
these
issues
are
closed,
but
they're
not
closed.
Yeah,
I'm
sorry
are
not
closed,
and
so
it's
you
don't
need
to
remove
it
when
the
design
is
done,
but
it
does
make
it
confusing.
A
Okay,
first
draft
design
added
ready
for
dev.
Do
you
want
me
to
put
a
status
on
this
one.
A
Okay,
and
is
there,
is
there
so
this
is
everything
right
for
design
work
for
that's
for
that
you're
doing
right
now,.
A
C
C
So
for
the
dark
visualization,
all
the
interviews
are
through
and
I
thought
I
would
be
analyzing
the
interviews
on
tuesday,
which
was
yes
yesterday,
but
there's
a
lot
of
work
and
jason
mentioned
that
to
get
everything
weighted
for
13.5
smoothly.
I
should
be
putting
all
the
designs
for
13.5
by
the
end
of
this
week,
so
I'm
kind
of
focusing
on
that
and
there
was
a
lot
to
look
at.
A
A
The
other
thing
that
I
think
we
should
call
out,
even
though
it's
not
a
formal
research
is,
is
the
the
the
regarding
the
the
graphic
visualization,
because
you're
collecting
the
feedback
on
it
and
also,
I
think,
you're
summarizing.
That
takes
a
lot
of
time.
It's
not
an
official
research,
but
it
still
is,
in
my
mind,
a
a
a
research
effort
in
and
of
itself
review.
A
I
was
thinking
that
we
probably
need
to
have
a
session
and
take
all
that
feedback
and
do
some
analysis
of
what
will
be
the
next
issues
that
we
create
off
of
that.
But
I'm
wondering,
if
really
that's
for
me
to
do
anyways
when
it's
going
to
be
probably
under
jason's
category
or
ci
authoring.
C
I
did
have
like
I
did
ask
jason
the
question
about
how
I
should
work
on
the
for
the
development
on
that
idea
and
what
how
should
I
at
least
make
the
stakeholders
aware
of
what
roadmap
I'm
trying
to
follow,
or
should
I
be
creating
new
stories,
but
I'm
thinking-
and
you
can
tell
me
what
do
you
think
about
it-
I'm
thinking
to
discuss
this
once
in
the
ci
weekly,
with
like
in
presence
of
the
whole
team-
maybe
not
today,
maybe
next
week,
because
I'll
be
off
after
this
meeting,
and
so
then
what
would
happen
is
all
the
engineers
might
also
get
to
weigh
in
on
this
like.
C
How
would
they
want
this
to
be
broken
down,
because
there's
so
much
to
be
done
on
this
concept
like
there
are
many
small
little
parts
of
it
that
have
to
be
taken
care
of
so
right
now,
I'm
not
sure
that
I
am
done
covering
all
the
capabilities
of
the
yaml
file
itself.
I
have
to
also
take
care
of
the
toolbar
that
would
go
on
the
graph
and
some
more
elaborate
graph
interactions.
A
Yeah,
so
we
we
probably
wouldn't
cover
that.
That's
why
I
was
mentioning
that.
Maybe
we
needed
a
session,
we
probably
wouldn't
cover
that
in
the
ci
weekly,
because
it
sounds
like
more.
We
need
a
deep
dive
session
with
engineers
to
to
to
to
talk
about
what
the
just
the
feature
as
a
whole,
and
we
wouldn't
have
time
in
that
30-minute
meeting
with
all
the
stuff
on
the
agenda.
It
would
be
a
dedicated
session.
A
deep
dive
session
into
these
are
all
the
feedback.
A
Let's
talk
about
the
capabilities
and
how
we
want
this
feature
to
evolve
and
then
from
there
order
the
sequence
of
iterations
on
it,
and-
and
I
was
you
know
if
this
was
going
to
only
remain
a
a
visualization-
I
would
probably
want
to
be
more
involved,
but
since
this
is
going
to
be
what
we're
delivering
was
just
the
initial
visualization
from
here,
it
gets
very
interactive
as
far
as
editing-
and
I
think
the
the
pm
for
ci
author,
which
should
probably
be
involved
in
that
and
not
me
now.
A
There
is
a
lot
of
transition.
That's
happening
around
that
anyways
and
you
and
I
have
the
most
knowledge
about
it.
So
we
will
kind
of
do
an
exception
on
it
and
and
I'll
probably
leave
the
chart
on
charge
on
it
with
we'll
probably
have
both
pm's
and
both
designer
in
that
deep
dive
session,
and
then
probably
a
representative
engineer
from
front
end
and
back
in
yeah.
C
A
Not
the
entire
team
yeah
I'll
I'll
just
go
ahead
and
schedule
that
what
do
we
know
is
is
well
I'll
find
out.
If
I
I
include
jason
or
or
probably
yeah,
I
know
there's
some
transitioning
that's
going
to
be
happening
there,
but
for
now
I'll
just
include
all
pms
yep.
C
Anything
else
yeah,
so
I
had
this
other
question
that
in
the
ux
theory
that
we
are
using
right
now,
this
like
we
are
assuming
that
that
workflow
design
is
followed
by
ready
for
development,
and
I
know
I
had
this
conversation
with
you
once
but
then
again
I
saw
multiple
threads
on
slack,
like
some
people
again
weighing
in
on
this
and
some
sort
of
conversation.
So
is
there
any
update
on
that
front
like
are
we
doing
it?.
A
Yeah,
you
know
yeah,
so
the
the
confusion
is
this:
normally
the
the
the
way
we
would
do
it
is
the
design
is
done,
and
then
the
issues
gets
weighted
and
when
the
issue
gets
weighted,
it
goes
from
workflow
design
to
planning
breakdown
when
the
issue
gets
weighted
to
ready
for
dev
right.
A
A
When
we
talked
about
it,
I
said
it
might
be
hard
for
you
to
know
where
it
should
go,
whether
it
goes
to
planning
breakdown
or
ready
for
dev
to
just
ping
me
and
cheryl,
and
we'll
figure
it
out
in
the
current
milestone.
The
most
recent
discussion
and
confusion
was
in
the
interest
of
time.
A
D
But
you
isn't
there
another
round
of
of
just
confirming
and
checking
the
weights
after
the
design
is
ready
needed,
because
it
feels
a
bit
like
counter
logical
to
have
the
weight
before
the
design
is
ready.
I
mean
how,
yes,
what
is
engineering
than
putting
the
weights
on.
A
No,
I
totally
agree
nadia.
I
think
they
were
doing
their
best
guess,
based
on
the
what's
in
the
proposal,
I
don't
think
we
were
good
at.
We
were
not
getting
ahead
of
having
all
the
designs
before
a
milestone
started,
and
so
we
were
trying
to
do
our
best
guess.
D
And
I
guess
it
should
not
influence
anyway,
like
the
change
in
the
in
the
workflow
order,
I
mean
if
we
are
doing
with.
If
we
are
done
with
the
designs,
maybe
it
still
makes
sense
to
assign
that
to
the
ready
for
the
development
or
like,
what's
the
workflow,
that
that
we
are
signing
the
weights
and
then
just
go
through
the
normal
flow.
So
we
don't
have
any
exceptions
and
it's
less
confusing
and
we
also
try
to
learn
and
follow
the
proper
order.
D
Oh
so
yeah
great,
oh
yeah.
I
was
actually
working
on
the
visualization
for
this
and
it's
so
much
needed
here.
So
after
well,
yeah
after
the
workflow
design,
there
is
workflow
solution,
validation,
usually,
and
then
there
is
a
planning
breakdown.
The
next
workflow
I'm
looking
here
so
yeah.
D
Here,
yeah,
I
think
it
makes
sense
if
we
are
trying
to
stick
to
that.
I
also
know
in
the
process,
but
also
like
yeah,
I
think,
especially
if
we
have
the
weights
already
just
kind
of
like
giving
it
another.
Quick
look.
Maybe
nothing
changed,
but
then
we
still
follow
the
order
and
just
re-ensuring
that
our
previous
weight
was
correct
was
having
the
design.
Actually,
I
don't
know
just.
A
Yeah,
I
I
think
we're
just
always
gonna
so
we'll
just
always
put
it
back
to
planning
breakdown
and
let
let's
show
decide
if
the
weight
can
stay
as
it
is,
and
she
can
move
it
to
ready
for
dev.
I
I
think
the
the
team
we
were
trying
to
move
quickly
before
is
right
after
it
was
designed
going
to
ready
for
dough,
because
at
that
point
the
waiting
was
less
important.
A
If
it's
already
in
the
milestone
and
part
of
the
purpose,
was
the
way
it
was
deciding
whether
or
not
it
would
be
in
the
milestone
right.
So
it
was
kind
of
after
the
fact,
but
I'll
reiterate
at
the
team
meeting
that
when
the
design's
done,
we
always
just
put
it
into
planning
breakdown,
even
if
there's
already
a
weight
on
it,
so
that
there's
a
re-validation
of
the
weight.
A
And
another
scenario:
an
idea
of
why
something
already
had
a
weight
in
the
past.
We
realized
it
had
to
wait,
it
did
not
appear,
there
was
any
ux
design,
ux
flow
or
design
needed
and
it
went
into
development
at
the
initial
stage
we
decided.
Actually
we
do
want
to
have
a
design,
but
we
didn't
go
back
and
remove
the
weight
from
the
issue.
We
just
pushed
it
back
to
to
get
a
design,
but
then
it
was
confusing.
D
Yeah,
I
think
that
just
like
makes
a
lot
of
sense.
This
is
natural
way
to
do
it
because
yeah
with
the
design,
probably
a
lot
of
well,
I
would
expect
some
corner
cases
are
visited,
that's
in
the
definition
of
dawn
of
ux
as
well
right,
so
I
yeah,
I
would
expect
changes
to
the
weights.
A
Yeah
and
then
the
other
thing
that
I
realize
later
is
the
advantage
of
even
if
there's
already
a
weight
and
they
wanted
some
refinement
on
the
design.
So
we
put
it
back
to
workflow
design
that
it's
good
to
always
take
it
from
there
to
planning
breakdown
so
that
the
set
in
this
case
tiffany,
has
a
chance
to
reassess
her
notes
on
what
the
end-to-end
testing
needs
to
be
in
case
some
small,
something
that
we
think
is
a
small
addition
to.
A
A
Okay,
so
I
I'll
upload
this
to
our
playlist.
I
realized
last
week
that
I
didn't
upload
the
one
we
meet
every
other
week
now
for
this
session
and
then
in
between
those
every
other
week
is
discussion
solely
on
ux
research
with
lori
involved,
in
that
one
I'll
upload
that
one,
along
with
this
video
from
today
to
our
our
playlist
and
the
playlist
link,
is
at
the
top
of
this
agenda.