►
From YouTube: CI/CD UX Meeting - 2021-04-21
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
B
B
So,
first
off
we
had
lots
of
discussions
in
the
retro
that
I
started
to
gather
feedback
from
the
engineers
on
how
they
would
like.
Isn't
this
retro?
Yes,
how
they
would
like
to
work
with
ux
so
like
how
do
they
want
to
collaborate
in
issues?
When
do
they
want
to
be
included?
What
is
the
preferred
way
to
receive
updates
from
ux,
like
all
of
these
things
and
our
front-end
engineers
provided
lots
of
very
detailed
feedback?
That
really
helped
me
better
understand
like
what.
What
is
the
problem
like?
B
What
is
that
gap
that
exists
between
us,
and
I
like
it,
answered
a
lot
of
questions
for
me
and
kind
of
opened
my
eyes
to
some
of
the
problems
that
I
didn't
think
were
problems,
so
that
was
great.
So
there
was
a
discussion
here
with
some
follow-up
questions
and
stuff,
based
on
that
and
based
on
the
survey
that
I
ran
to
kind
of
set,
a
benchmark
score,
which
actually,
I
have
to
finish
analyzing
this,
I
kind
of
analyzed
the
results,
but
haven't
really
documented
them
yet.
B
So
I
have
to
do
that,
but
I
ran
a
survey
it's
anonymous,
so
I
can
share
the
results
with
you.
I
think
which
was
interesting,
because
it
really
highlighted
that
there's
really
a
gap
between
what
the
engineers
want
and
what
I'm
providing.
B
Even
though
I
felt
like
I'm
really
doing
such
a
great
job,
communicating
all
of
the
ux
findings,
but
I
just
wasn't
doing
it
in
a
way
that
made
a
lot
of
sense
to
them
and
that
was
easy
for
them
to
consume,
so
turned
out
that
a
lot
of
the
team
members,
so
these
are
the
responses
were
from
front
end
engineers,
mostly,
but
also
backhand,
and
also
one
engineering
manager
as
well.
Half
of
the
team
doesn't
really
feel
included
or
excluded
into
x
process.
B
I
guess
they
just
don't
really
feel
that
much
involved
and
I'll
kind
of
go
over.
Some
of
the
most
interesting
results,
but
most
participants.
B
They
didn't
understand
how
ux
research
ties
into
our
product
direction
and
the
user
experience.
So
that
was
interesting
also
because
for
me
and
dove
it's
obvious.
We
know
why
we're
doing
it
and
we
know
why
it's
important
and
we
share
it,
but
it's
just
like
we
weren't
able
to
really
show
how
it
ties
to
our
product
direction,
not
yet
at
least
because
again
we're
very
new.
So
I
guess
it's
normal
that
we're
going
through
this
process
and
yeah.
So
it
turns
out
also
we
weren't,
including
the
engineers
early
enough.
B
We
would
include
them
after
we
do
like
a
first
pass
on
a
design
solution
or
like
a
design
proposal,
and
from
that
and
from
there
on,
we
would
really
include
them
and
we
would
collaborate
with
them
at
that
point,
but
they
felt
like
at
that
point
we're
already
leading
with
some
type
of
solution
that
we
created
based
on
the
insights
and
the
data
and
the
business
case
that
they
don't
fully
understand.
B
So
we
we
found
that
there's
an
opportunity
for
us
to
establish
more
trust,
for
example,
for
sure,
and
to
show
like
a
more
solid
foundation
that
we
already
have
in
our
heads,
but
show
it
to
the
rest
of
the
team
of
all
of
the
ux
research
insights
and
all
of
the
like
opportunity,
canvases
that
dove
has
been
working
on,
and
you
know
things
like
that.
B
So
there's
also
nmr,
where
I
propose
some
changes,
but
there
will
be
many
more
changes,
mainly
just
like
simplifying
things.
You
can
go
over
this,
mr,
if
you're
curious
about
like
what
are
the
things
that
I'm
hoping
to
accomplish
in
terms
of
ux
collaboration
on
the
team
and
there's
an
ongoing
discussion
here
between
the
engineers
and
the
engineering
managers
and
job,
and
I,
if
you
have
any
comments,
also
feel
free
chairman.
B
B
So
our
goal
is
to
our
goal
is
to
align
on
like
a
small
process,
change
that
we
know
will
be
impactful
and
that
will
be
piloting
and
for
now
we're
thinking
that
we
will
focus
on
fostering
async
communication
and
async
updates
between
engineers
and
ux
to
help
us
document
everything
better
and
that
will
like
solve
many
problems
in
terms
of
the
shard
understanding
that
we
create
and
how
accessible
the
information
is.
B
So
yeah
very
excited
about
this,
and
it's
been
taking
up
a
lot
of
my
time
and
just
like
kind
of
mental
energy.
Just
because
it's
this,
this
kind
of
messy
human
relationship
thing
that
needs
to
be
figured
out.
But
let's
see
how
that
works
out.
I
think
we
can
figure
it
out.
A
Thank
you
for
sharing
this
nadia.
I
know
that
it's
we've
been
talking
about
this.
It's
a
recurring
theme
across
git
lab
and
I'm
curious
to
hear
also
from
others.
I
know
that
vitica
with
your
team,
you
managed
to
align
things.
I
think
in
I
would
say
much
easier
way
and
then
your
your
own
boarding
and
you
getting
to
know
people
but
yeah.
I'm
curious
to
hear,
with
your
experience
and
your
thoughts
on
on
the
on
the
survey
on
the
results
that
nadia
shared.
C
C
Are
there
very
responsive
and
they're
always
keeping
an
eye
out
for
any
new
updates
on
the
issue
by
me
or
by
someone
else,
so
the
discussion
pardon
the
ci
team,
it's
it's
very
healthy
and
it's
very
productive
that
I'm
just
having
a
hard
time
of
like
taking
out
an
actionable
improvement
that
the
pipeline
authoring
team
could
make
by
getting
inspired
by
how
we
work,
because
it's
also
organic.
D
So,
for
my
part,
this
this
last
milestone
1311,
was
my
first
milestone
fully
as
as
designer
in
release.
So
for
me,
it
was
rather
than
having
an
optimal
process.
Just
having
any
process
was
the
first
time
I
was
was
implementing
a
design
process.
D
Here,
I
already
got
really
good
feedbacks
on
how
I
can
improve,
and
some
things
I
realize
were
not
ideal,
so
I'm
gonna
start
using
loom
videos,
for
example,
to
communicate
the
broader
design
division
for
an
issue,
because
just
typing
walls
of
text
sometimes
doesn't
really
work
as
well
to
communicate
the
meaning
behind
the
design
changes
nadia.
I
think
it's
really
great
how
how
not
only
you
had
this
initiative
to
improve
the
process,
but
also
you,
you
used
the
design
process
to
improve
the
design
process.
That
was
really
amazing.
D
The
survey
and
everything
I'm
still
figuring
out
where
to
go
in
terms
of
design
process
for
release,
but
I'll
definitely
steal
some
of
your
ideas
to
to
have
better
feedback
in
a
similar
way,
more
structured
right,
rather
than
just
asking
hey.
What
can
I
improve?
So
thanks
for
the
really
good
example.
B
Yeah,
I
think
my
my
learn
main
learning
from
this
whole
process
so
far
was
that
I
should
have
run
the
survey
like
one
week
into
the
pipeline
authoring
team
being
born.
Just
maybe
not
this
exact
survey
but
to
better
understand
the
background
of
all
of
the
engineers
and
how
they're
used
to
working
to
understand
what
gaps
to
expect
and
what
gaps
to
kind
of
predict
that
they
will
form
because,
like
this
is
their
background-
and
this
is
my
background,
so
I
could
adjust
earlier
on,
but
yeah
better,
better
late
than
never.
A
Yeah
that
was
actually
gonna,
be
my
point.
I
was
cycling
this.
I
think,
a
key
like
element
to
success,
especially
for
us
that
you
know
we
are
all
remote
company
we
are
acing.
First,
is
that
whenever
you
join
a
team
or
someone,
you
join
get
that
person
into
a
zoom
chat
and
ask
how
do
you
want
to
work?
What's
your
experience
working
with
designers,
this
is
what
I
do.
This
is
what
I'm
expecting
from
you.
A
How
can
I
help
you
know-
and
I
think
a
lot
of
times,
especially
that
in
teams
where
either
they
don't
have
a
strong
experience
working
with
designers,
but
also
where
they
are
development
first
right
in
terms
of
they're
led
by
engineering,
so
teams
that
are
less
mature
in
terms
of
design
processes,
etc.
A
I
think
it's
important
that
we
take
the
the
lead
and
have
this
tough
conversations
with
folks
who
to
build
that
build
up
bridge,
and
it's
awesome
that
nadia
and
also
dove
right
during
this
this
conversation
with
the
team.
They
really
are
asking.
What
do
you
want
to
see
from
us?
A
I
think
that's
also
very
important
to
connect
with
people
on
a
personal
level,
and
maybe
it's
something
that
here
I
go.
We
can
bring
to
the
ux
department,
but
not
in
terms
of
here's,
what
I'm
we're
doing.
But
how
can
we?
You
know
if
this
keeps
happening
if
this
is
a
a
recurring
thing
in
other
teams?
Here
are
a
couple
of
tips
that
for
designers
here
a
couple
of
questions
that
you
should
that
we
should
be
asking
our
peers-
and
I
don't
know-
because
he'll
have
a
framework
to
help
others
yeah.
But
it's.
C
C
Yeah
and
on
similar
lines,
I
I'm
also
thinking
on
about
something
similar,
that
I
feel
that
everything
is
going
fine,
but
I
think
this
is
a
good
reminder
that
we
should
be
checking
with
our
team.
I
mean
before
something
gets
out
of
control.
I
just
keep
checking
if
everybody
is
fine
with
the
team
process
or
do
some
people
expect
some
changes
due
to
current
circumstances
or
something
so
we
should
be
doing
that
more
regularly.
A
A
My
experience,
for
example,
with
the
religion
release
management
team,
was
that
the
em
and
also
the
pm
would
be
the
ones
taking
on
the
the
topics
right:
the
feedback
from
the
engineering,
the
ux
team,
whatever
and
creating
action
items
for
us
for
the
upcoming
milestone.
How
is
that
done
today
in
your
teams.
C
B
Yeah,
it's
kind
of
the
same
thing
on
the
pipeline
authoring
team.
I
don't
know
if
we
create
issues
for
all
of
the
items.
To
be
honest,
I'm
not
really
well
aware,
like.
I
was
never
tagged
on
any
of
those
issues
if
sam
and
cheryl
used
something
to
track
those
efforts,
maybe,
but
I
know
that
we
do
have
a
section
for
actionable
items.
I
linked
one
of
our
retros
there
somewhere
at
the
top
of
the
agenda
and
we
just
link
them
there,
like
just
as
bullet
points.
B
This
is
action
item
we
want
to
do
this.
We
want
to
do
that
and
then,
when
we
created
the
next
retro
at
that
point,
we
have
a
look
at
the
previous
retro
and
we
see
what
happened
to
the
action
items
and
then
cheryl
and
sam
and
dove
probably
fill
it
out.
I'm
not
sure
who
exactly
is
involved,
but
I
know
that
sam
for
sure,
shared
updates
on
action
items
and
we
had
discussions
about
that
in
the
weekly
team
meetings
as
well.
A
I'll
paint
them
in
your
retro
just
to
ask
and
also
to
ask
it
if
this
time,
based
on
the
you
have
today
right
the
the
sync
retrospective,
you
can
create
those
issues
that
refer
to
things
that
belong
to
ux,
sortings,
that
you
need
to
work
on
with
dolph
et
cetera.
I
think
that's
important.
A
That
was
my
experience
in
release
management.
We
were
very,
I
think,
we're
very
well
structured
in
terms
of
process,
and
I
actually
have
one
example
here
to
share
yeah.
So
let
me
add
to
the
agenda
because
it's
a
good
reference.
A
This
was
the
an
action
item.
Singular
situation
that
I
had
is
not
different
and
the
merge
request
review
process.
So
I
was
not
being
tagged
on
any
merge
requests
or
being
asked
for
a
review
lots
of
ux
that
being
generated
and
the
pm
not
npm
the
engineering
manager.
John
back,
then
he
created
a
specific
issue
where
the
front-end
engineers
and
I
could
just
go
in
and
review.
So
all
our
conversation
happening
separate
and
we
were
responsible
for
taking
that
action
item
working
on
it
and
then
bring
on
a
separate
discussion.
A
I
think
it's
something
interesting
to
bring
to
your
teams
if
you
are
working
on
feedback
during
the
retrospectives
and
just
checking
if
they
are
doing
this
way,
if
not
and
if
you
don't
feel
comfortable
having
this
conversation,
just
let
me
know
and
I'll
reach
out
and
I'll
check
in
with
the
teams.
C
Oh
yeah,
so
it's
more
of
a
read-only
but
I'll
still
vocalize
this.
So
it
starts
last
day
today
and
yeah.
That's
pretty
sad
and
following
that
there
might
be
some
changes
that
will
take
place
in
the
ci
design
priorities,
so
I'll
be
having
meetings
with
jackie
one
on
ones
to
discuss
the
ux
projects
for
ci
and
a
few
things
might
change.
But
I
will
try
my
best
to
keep
everyone
informed
around
those.
A
Yeah
thanks
for
the
heads
up
vitica
have
you
seen.
I
know
that
is
a
bit
off
topic.
Have
you
seen
the
the
planning
for
the
next
three
milestones
that
jackie
already
created.
C
At
that,
because
I
think
tao
also
created,
I
did
not
know
that
jackie
again
created
something
I'll
check
that
out.
I
think
I
think
it's
the
same.
C
A
A
A
And,
of
course,
I
think
with
that
transition
think
it's
important
to
remember
remind
all
of
us
that
transitions
happen,
and
I
think
this
team
is
a
it's
a
living
proof
of
you
know:
gitlab
changing
and
people
leaving
and
joining
in
a
very
short
period
of
time
if
anyone
needs
help,
especially
with
these
transitions
with
the
research.
Please,
let
me
know
I'm
here
to
support
you,
I'm
here,
to
find
the
connections
and
trying
to
understand
who
can
help
you
we're
not.
A
A
Yeah
yeah.
I
just
want
to
ask
if
anyone
has
any
fun
plans
for
focus
fridays,
if
you
have
been
using
your
plan
to
use
this
friday
to
work
on
leader,
growth
and
development,
stuff
or
just
personal
stuff,
for
me,
I'm
taking
the
friday
this
friday
to
work
on
my
upcoming
week,
because
I'm
doing
a
lot
of
interviews
for
the
testing
runner
design
role
so
talking
to
speaking
with
a
lot
of
people
very
time
consuming,
but
also
very
tiring.
D
Yeah
I
have
a
hover
conference
this
friday,
which
I'm
very
excited
about
to
learn
some
advanced
css
stuff.
They
have
this
weird
dates.
I
think
it's
split
within
two
dates,
so
it's
going
to
be
this
friday
and
then
another
piece
later
on
so
yeah
really
excited
about
it.
We'll
we'll
take
lots
of
notes
and
share
with
you
all.
I
think
they
will
likely
have
videos
up
soon,
so
everyone
will
be
able
to
watch
it
as
well.
C
Oh
yeah,
I
I
wanted
to
mention
that
nadia
and
I
participated
in
the
bad
conference,
but
the
participation
couldn't
be.
It
did
not
go
as
planned,
because
the
technology
was
very
shaky
and
very
disturbed.
So
even
I
am
who
I
really
struggle.
I
thought
if
I
have
taken
the
leave,
I
would
go
through
the
videos
as
they
go
live,
but
it
was
just
not
possible.
So
when
I'm
working
on
getting
the
recordings
and
then
going
through
them
as
an
idea.
A
Was
being
recorded
wow,
but
it
if
you
couldn't
follow
it
and
I
think
it's
something
that
yeah
we
should.
We
should
look
into
or
we
could.
A
B
Yeah,
hopefully
the
recordings
will
be
fine,
because
it
also
wasn't
that
cheap
honestly.
So
it's
a
bit
of
a
disappointment
and
the
recordings
are
still
not
live,
none
of
them.
So
I
I
even
took
some
time
off
last
week
to
listen
to
all
the
talks,
but
I
I'll
just
have
to
do
it
whenever
the
recordings
come.
A
B
A
B
A
A
For
myself,
if
you
can
then
later
on
just
briefly
just
slap
me
with
what
happened
in
what
issues
you
had
and
then
I'll
I'll
think
with
that
valeria
just
throw
them
a
message
to
see.
If
there's
anything,
we
can
do
bad
conference.
A
No
comments,
but
we
can
do
that
well,
but
anyways.
If,
of
course,
if
you
get
access
to
when
you
get
access
right
to
the
the
content,
please
take
the
time
to
go
over
things
and
even
though
yeah
it's
not
the
official
conference,
but
I
think
it's
it's
important
to
have
that
the
mind
space
to
do
that
so
feel
free
to
drop
a
you
know,
weird
thing
focus
time
take
a
day
or
two
not
sure
if
the
conference
was
a
day
or
two,
but
do
your
thing
you're
free
to
do
that.
B
D
A
B
Be
doing
I'll
be
working
on
interview,
training
which
I
wouldn't
say
it's
fun,
so
I
should
probably
add
something
else.
That's
fun.
I
have
like
replying
to
retro
issues
and
doing
interview
training
on
my
list
for
now,
but
I'll
add
some
something
more
interesting
to
that.
A
A
Yeah
please
align
on
that.
That'll
be
awesome
and
I
think
then
you
also
add
a
plus
one
here:
go
over
the.
A
Yeah
that
I
think
that's
the
most
important
and
when
you're
done
with
the
trainings,
bring
me
the
issue
and
say
hey,
I'm
ready
to
to
start
shadowing
now,
because
I
think,
especially
with
the
time
zones,
would
be
interesting
to
get
the
two
of
you
vitica
nadia,
to
shadow
some
interviews,
but
also
at
some
points
lead
or
have
that
experience.
Since
we're
getting.
A
Candidates
in
india,
I
think
australia,
so
that
would
be
they'll,
be
fun
too,
and
also
daniel.
To
help
me.