►
From YouTube: CI/CD UX meeting - 2020-12-09
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,
hi
everyone.
This
is
the
cicd
ux
meeting
and
yeah.
We
have
a
couple
of
items
in
the
agenda.
I
know
that
nadia
is
not
joining.
I
think
she
added
some
async
topics
to
it.
A
Let's
see
anyone
wants
to
jump
into
what
she's
talking
about
pmux
engineering
collaboration
in
cicd
and
she
talks
a
little
bit
about
the
product
development
workflow.
So
I'm
just
gonna
go
ahead
and
read
so
please
interrupt
me
at
any
moment.
B
I
want
to
make
a
point
on
this
one
that
when
I
think,
when
nadia
penned
this
down,
the
workflow
hadn't
changed,
and
it
has
undergone
a
lot
of
changes
very
recently.
B
So,
and
that
also
means
that
I
mean
we
were
technically
basing
our
ux
definition
of
done
on
the
existing
product
development
workflow,
and
that
also
needs
to
evolve.
So
all
the
discussions
that
we
have
had,
we
might
have
to
have
them
again.
B
I
don't
remember
very
clearly,
but
I
I
have
a
faint.
I
could
recall
that
we
now
have
an
extended
validation
phase
in
the
product.
Development,
workflow
and
design
is
kind
of
a
part
of
the
solution,
validation
phase,
and
that
itself
is,
I
think,
a
pretty
big
change.
B
So
maybe
we
were
kind
of
following
the
same
approach,
but
how
we
were
addressing
those
phases.
I
mean
the
terminologies.
We
were
using,
at
least
that
definitely
has
to
change
in
the
ux
definition
of
tan,
and
I
think
nadia
could
use
this
as
an
opportunity
as
well,
because
pipeline
authoring's
ux
pages
yet
to
be
set
up,
and
she
could
consider
all
the
new
changes
and
create
something
from
scratch.
A
So
I'm
taking
some
notes
here
so
yeah.
She
can
follow
up
a
sync
to
set
up
these
definitions
and
then
we
can
talk
to
nadia
if
anything
needs
to
need
clarification,
I'm
still
not
up
to
date
with
all
the
changes
I
personally
in
the
brow
development
workflow,
because
I
haven't
started
working
hands-on
with
the
pms
yet,
but
I'm
curious
to
see
how
this
is
going
to
affect.
Maybe
audit,
you
have
some
insights
from
a
broader
point
of
view.
C
A
Yeah,
so
maybe
that's
an
action
item
for
all
of
us
follow
up
and
see
how
how
that
affects
our
ways
of
working
and
let's
see,
let's
see
how
that
goes,
any
comments
on
that
we'll
try
to
jump
into
the
next.
One
final
comments:
nope
e-
and
I
see
your
new
house-
and
you
have
stairs
now
so
nice.
E
C
D
D
A
That's
the
beauty
of
amsterdam,
there's
always
something
happening,
but
it's
also
the
curse.
If
you
live
in
the
city
center
awesome,
I
added
a
couple
of
fyi
items
here.
It's
the
first
one
is
that
I
added
I
think.
Over
the
last
week
I
added
a
couple
of
points
to
the
ux
to
the
verify
group
page
in
the
handbook
just
pointing
to
where
our
ux
pages
live.
A
So
this
is
just
for
awareness,
so
yeah,
because,
especially
if
you
think
that
there's
something
else
that
could
be
added
here
by
all
means
just
add
a
merge
request
and
kind
of
just
want
to
clarify
some.
A
I
want
to
clean
up
all
these
handbook
pages,
because
I
see
that
there's
a
lot
of
information
being
repeated
on
how
we
work-
or
I
don't
know
our
team
strategies,
and
I
think
we
should
refer
to
one
source
of
truth
so,
for
example,
the
cicd
ux
page
and
I'm
adding
this
I'm
testing
myself
with
some
of
this
cleanup
later
on.
So
all
my
being
you
okay
or
for
feedback
later
on.
B
That
that's
a
good
point,
because
I
also
observed
that,
on
the
ux
page,
there's
kind
of
a
duplication
of
some
information
that
should
live
on
the
verify:
ci
product
development,
workflow,
page
yeah,.
A
So
it's
a
a
bit
of
a
it's
a
thing
for
us
to
keep
updating
all
these
pages.
So
I'm
just
going
to
make
sure
that
yeah
we
have
the
least
not
the
least
information,
but
we
are
pointing
to
one
source
of
truth.
I
think
that
will
help
moving
forward,
especially
also
when
we
talk
about
the
product,
workflow,
definition
of
dawn,
etc.
It
would
be
nice
to
have
one
place
of
reference,
and
my
next
point
is
that
in
case
you
haven't
seen
it
yet.
A
There
was
a
merge
request,
adding
some
information
on
future
investments
and
priorities
for
op
sections
and
here's
a
link
to
the
page,
and
it
talks
a
little
bit
about
our
10
investment
priorities
and
yeah
strategy
or
acquisition
plans,
etc.
So
the
three
main
topics
are
verify
runner
platform,
enablement
package,
enterprise
hardening
and
accelerating
sequence
management.
A
C
I
can
say
that
we're
looking
into
maybe
testing
in
future
flags
to
accelerate,
but
so
far
we've
kind
of
said,
like
we
haven't,
found
something
good.
Everything
is
lacking
and
we
already
do
it.
So
I
don't
know
yeah.
A
There's
an
issue
also
linked
here
that
talks
about
the
research,
not
sorry,
not
the
research,
but
a
list
of
all
issues.
B
A
I
kind
of
wanted
to
take
this
opportunity
to
ask
you
all
like
how
are
you
feeling
about
these
meetings
and
what
can
we
use
these
moments
to
you
know
for
the
for
the
sake
of
the
cross
collaboration.
A
I
know
that
we
have
this
one
and
then
we
also
have
the
reviews
in
think
big,
but
yeah.
We
have
less
attendance,
I
think
in
the
last
month,
or
so
like
less
than
two
months.
So
I
just
kind
of
wanted
to
hear
from
you
if
you
have
any
thoughts
on
changing
the
cadence
of
these
calls,
the
cicd
us
calls
or
changing
the
format
or
whatever
so
open
question.
If
you
have
any
feedback.
B
I,
for
once,
you
feel
that
we
should
have
add
some
rituals
to
this
meeting.
For
example,
what
are
the
current
important
things
that
we
are
working
across
like
all
the
stages
that
we
are
concerned
with,
so
that,
if
there's
an
opportunity
to
maybe
collaborate
or
even
to
comment
that?
Okay,
something
similar
on
similar
lines,
is
happening
on
my
stage
group
or
we
are
working
on
a
component
that
touches
upon
the
feature
you're
talking
about
yeah?
A
It's
like
having
standing
items
that
we
know
that
in
a
way,
yeah
are
owned
by
multiple
people,
yeah
any
other
thoughts.
C
I
usually
don't
join
this
call
because
it's
very
ux
focused.
I
had
some
time
today,
so
I
thought
I
would
join.
I
think
that,
given
the
current
circumstance,
I
don't
know
how
much
cross
work
we're
going
to
do
in
the
near
future,
because
there's
just
so
few
designers
for
the
stage
at
the
moment.
A
Yeah,
for
me,
I
agree
with
the
with
vidiq.
I
think
it
would
be
nice
to
kind
of
use
these
moments
to
talk
about
a
little
bit
of
something
about
something
that
it's
interesting
or
that's
been
going
on
in
your
stage
group,
but
make
it
more
topical.
I
think
that's
also
what
nadia
was
trying
to
do
with
the
review
sessions
right.
A
We
had
the
the
synchronous
ux
review
session,
so
it
doesn't
necessarily
have
to
be
about
yeah
work,
but
it
would
be
nice
if
it
will
be
a
bit
more
topical,
so
people
can
add
asynchronously,
maybe
and
then
yeah
whoever
joins
or
if
we
can
just
decide
to
not
have
the
face-to-face
call
the
content
is
there,
let's
see
how
that
goes,
ideas
for
like
a
topic
of
ikea,
even
though
like
what
considering
what
artists
said
right
now.
What
what
would
you
like
to
see
being
discussed.
B
Another
thing
is,
I
mean
because
of
so
many
new
work
that's
happening
around
and
I
mean
I
know
that
we
nadia
we
are
trying
to
innovate
every
day
with
the
process
that
we
are
following
and
it
starts
from
how
we
plan
to
how
we
conduct
the
review
sessions
with
the
developers.
All
of
that,
we
are
trying
out
new
processes,
so
maybe
we
could
share
about
that
and
I
completely,
for
example,
changed
the
way
I
used
to
plan
with
my
team
and
the
new
planning
process.
B
It's
working
out
so
well,
not
just
for
me,
I
think,
for
the
whole
team.
I
had
only
proposed
one
change
that
instead
of
tracking
my
items
somewhere
else
on
a
spreadsheet,
I
want
to
do
it
on
the
planning
issue
and
that
we
keep
the
planning
issue
open
throughout
the
milestone
and
not
close
it
and
keep
visiting
it.
And
I
mean
in
the
beginning
everybody
was
kind
of
skeptic
about
how
that
might
work
out,
but
it's
working
out
for
everyone.
D
I
really
like
the
idea
of
adding
conversations
or
topics
that
bring
us
together
talking
about
how
we
handle
problems
on
individual
teams,
because
just
like
vithika
is
saying
where
there's
this
planning
issue
in
that,
then
our
work
is
now
in
there.
We
did
that
on
package
and
it
really
changed
the
game.
So
not
only
did
I
have
a
single
source
of
truth
of
what
design
is
being
worked
on,
it
didn't
interfere
with
engineering
or
the
boards.
They
were
also
aware
of
it.
D
A
I
know
that
we-
I
don't,
we
have
one
of
these-
calls
this
year
christmas
new
year's.
I
think
next
one
is
it's
january
2021.
A
A
You
know
be
super
cool
and
vietnam,
your
planning
issue
here.
Do
you
want
us
to
share
more.
B
Yeah,
so
in
this
planning
issue,
if
you
see
there's
a
I
mean
we
used
to
have
this
long
back
a
section
for
the
ux
work.
It
started
off
with
four
issues
and
it
has
grown
to
11.
I
think-
and
it's
not
that
this
was
a
very
unique
milestone.
This
used
to
happen
every
milestone,
just
that
it
was
not
documented
all
at
one
place.
So
I
was
kind
of
handling
all
of
these
things.
B
On
my
own
and
my
pm
and
the
development
team,
they
were
not
always
aware
of
what
are
the
changes
which
are
happening
on
my
workload,
but
now
it's
very
transparent,
and
so
others
have
also
started
to
list
other
things
that
they
work
on,
that
which
are
kind
of
unplanned
and
or
maybe
they
are
added
after
milestone,
had
started.
B
Those
documentations
have
started
to
happen.
Then
we
also
started
to
discuss
about
promoting
things
within
the
team.
So
how
would
we
promote
a
certain
feature
that
we
have
worked
on
on
in
a
milestone
to
everyone
outside
and
should
we
is
it
something
that
we
should
promote
before
it
gets
released,
or
should
we
promote
a
teaser
first
and
maybe
the
feature
the
next
milestone?
B
A
A
Just
I
think,
one
of
the
most
powerful
things
my
opinion
is
giving
people
visibility
on
what
you're
working
on
and
helping
like
us
ourselves.
Better
pm
have
a
more
informed
conversation
about.
What's
coming
next,
where
you
act.
So
I
love
that
you,
you
move
things
from
that
sheet
to
this
issue.
So
that's
awesome.
C
Also
ian
asked
me
to
add
his
items
to
the
planning
issue
and
something
that
I
thought
about,
even
though
ian
didn't
answer.
I
know
that
nadia
at
the
time
had
a
issue
where
ux
doesn't
get
to
weight
things
in
terms
of
ux,
and
there
was
this
separate
spreadsheet
where
you
were
adding
ux
weight.
So
I
think
this
could
be
a
really
nice
place
to
consolidate
that
and
like
put
the
ux
weight
on
the
issue
in
the
planning
so
that
it's
visible
to
everyone,
you
don't
have
to
look
for
another
separate
location.
B
Right
and
one
more
thing
I
would
want
to
point
out
or
is
that
the
design
issues,
if
you
go
to
them,
they
are
not
assigned
any
milestone,
because
I
mean
it's
a
good
practice
to
work
on
them
in
advance
earlier
what
was
happening
it
was
since
I
was
tracking
them
separately.
I
had
to
assign
a
milestone
to
them.
I
used
to
cause
a
lot
of
confusion.
Like
is
this
a
candidate?
Is
this
not
a
candidate?
Is
it
in
a
milestone
backlog
and
all
of
that
now
it's
very
clear.
A
Yeah
this
is
awesome.
All
these
timelines
are.
We
are
very
engineering
focused
and
then
once
we
start
like
adding
new
wax
things.
There's
always
these
questions
are
rebuilding
this
thing
right
now
yeah.
So
it's
awesome
to
see
that
you
can
clarify
that
with
the
this,
not
just
the
status
but
yeah.
This
is
design
work
right.
You
still
need
engineering
involvement,
but
your
your
responsibility
in
the
planning,
it's
clear
yeah.
A
C
This
is
like
the
first
milestone
that
we're
actually
doing
this,
so
I
don't
have
like
a
good
retrospective
in
terms
of
what
works.
What
I
like
about,
it
is
a
it
gives
the
team
visibility
into
what
the
ux
designer
is
doing
and
b.
It
also
kind
of
sets
an
expectation
that
they're
going
to
be
pinged
on
this
issue,
so
right,
yeah.
D
A
D
Really
well
with
having
engineers
be
aware
of
what
we're
going
to
be
working
on,
which
is
a
huge
step
forward,
and
I
think
kind
of
to
what
viethco
was
saying
earlier.
Nobody
gets
confused
about
this
milestone
is
in
13.7.
Does
that
mean
design
is
doing
it
in
137,
or
does
that
mean
it's
engineering
in
1307
and
the
design
is
late?
There's
that
conversation
has
gone
away
entirely.
It's
all
on
this
nice
issue
we're
using
gitlab,
there's
no
spreadsheets
anywhere
else.
I
really
like
it.
A
Vitica
since
yeah
you're
planning
on
applying
this
also
for
the
next
milestone,
can
you
bring
back
to
us,
maybe
some
of
more
insights
and
learnings
and
in
case
something
happens
or
something
changes.
It
would
be
nice
to
hear
yeah
how
the
team
is
adapting
to
that
and
yeah
the
results
you
see
there,
so
we
can
begin
discussing
yeah.
A
I
just
want
to
say
that
funny
is
always
painful,
so
finding
one
little
way
to
a
small
way
to
improve
it,
for
yourself
is
just
yeah,
and
now
I
kind
of
have
a
question
vitica
on
you
have
priority,
and
you
also
have
the
way
right
on
the
issues
yeah
you
got
like
asked
developers
about.
I
know
the
ux
weight.
Is
there
a
clear
understanding
that
the
ux
weight
is
different
from
the
engineering
way
or
this
is
like
topic.
B
Right
since
I'm
not
working
in
the
same
milestone-
and
probably
I
am
two
to
three
milestone
ahead
of
the
development
work,
so
I
mean
developers
don't
even
have
to
care
about
how
I
am
weighting
my
issues
when
it
is
in
design
phase,
they
are
completely.
I
mean
it's
totally
up
to
me
how
I
manage
that
and
the
priority.
I
discussed
that
with
my
pm
and
then
we
set
priority
so
that
in
case
we
have
some
meeting
coming
up
in
the
middle
of
the
milestone
or
we
need
to
make
some
presentation.
B
So
we
try
to
attend
to
those
items
first
and
then
move
to
the
others
and
in
the
process
it
often
happens
that
I
don't
even
get
time
to
think
about
the
priority
of
some
items
and
have
to
work
on
them
on
the
go.
So
those
are
listed
at
the
bottom
that
they
were
unplanned,
but
they're.
A
A
No
confused
faces
not
now
awesome,
then
yeah,
let's
get
back
some
20
minutes
and
see
each
other
later.