►
From YouTube: ENG/UX Progressive Delivery Meeting 2020-09-01
Description
Meeting to improve alignment between Engineering and UX for progressive Delivery
A
All
right
cheers
thanks
for
joining
the
ux
engineering
meeting,
where
we
try
to
fetch
and
catch
all
the
gaps
in
process,
but
also
help
each
other
out
with
blockers
and
those
kind
of
things.
So
in
that
sense,
are
there
any
direct
blockers
where
I
am
blocking
engineering
with
a
certain
issue?
If
so,
this
is
the
right
moment
to
bring
it
up,
otherwise,
I'll
get
to
them
later.
A
Are
there
any?
If
not,
then
we're
gonna
go
through
the
next
point,
all
right,
three,
two
one
all
right
on
to
the
next
point,
so
I
was
looking
at
this
merch
quest
from
you,
andrew,
and
your
comment
was
super
valid.
So
I
thought
like
hey,
let's
bring
it
up
here
in
the
mr,
which
was
partly
reviewed
by
ayanna,
and
this
kind
of
thing
right
like
in
in
the
issue.
A
Those
skins,
I
think,
there's
always
a
point
of
improvement,
but
the
comments
you
create,
let
me
see,
did
I
that
was
the
other
link
here
and
I'll
share
my
screen.
So
there's
some
few,
some
visuals
here
here
you
can
see
like
hey
the
one
alert
seems
to
be
missing.
This
was
also
missing
from
initial
mockup
super.
True,
I
was
I
answered
to
this.
Like
hey,
the
mock-ups
did
not
represent
every
outcome
of
the
design's
concept.
That
is
not
like
you
know.
I
don't
want
to
do
the
work.
A
I
do
want
to
do
the
work,
but
sometimes
it
doesn't
make
sense
or
it
is
quicker
to
be
done.
In
writing.
I
was
having
a
discussion
with
hayanna
about
this,
because
I
met
up
with
her
friday
in
real
life
at
rotterdam,
and
I
was
discussing
how
she
does
certain
things
and
she
says,
like
I,
don't
create
any
visuals
if
I
don't
have
to
like
like
any
like
they
just
they
just
have
to
read,
and
I
was
like
all
right
that
works,
but,
on
the
other
hand
like
sometimes
visuals,
are
needed,
etc.
A
But
I
think
the
main
point
I
got
out
of
that
is
like
all
right.
She
does
that
to
decrease
wasteful
energy
spent
on
creating
mockups,
but.
B
A
Other
hand
it
highlights
the
importance
of
the
text
of
the
concept
right
like
if
I
wouldn't
have
put
the
image
there,
then
there
wasn't
an
image
to
look
at
and
then
the
only
thing
highlighted
there
was
the
text.
So
my
basic
question
would
be
like
hey.
How
would
you
like
to
see
developer
handoff
be
done
like
do
you
like
the
visuals,
or
is
it
only
exceptionally
necessary
when
something
is
unclear
and
otherwise
keep
your
text
or
like?
C
I
am
personally
a
big
fan
of
mockups,
I
think
they're,
a
good
way
of
catching
as
we've
seen
this
thread
kind
of
spiral
out
and
they're
a
good
way
of
catching
things
that
end
up
being
a
little
weird
earlier
in
the
process
than
then
later
on.
A
A
My
main
point,
though,
is-
and
that
is
mostly
for
the
design
person
I
don't
want
to
create,
like
you
know,
like
10
iteration
markups,
with
small
visual
changes,
so
what
I've
done
in
the
like
the
last,
I
know
so
many
issues.
I've
worked
on
if
there's
only
a
small
change
towards
the
design.
For
example,
I've
been
in
talks
with
marcel
on
technical
writing,
and
you
know
like
hey.
A
This
copy
needs
to
be
changed
in
this
slightly
different
sentence
structure
like
yes,
I'm
not
going
to
create
a
new
visual
for
that,
because
that
is
just
wasted
energy
right,
but
I
do
want
to
make
it
clear
like
for
those
cases
that,
like
the
mock-up
will
not
always
represent
the
latest
and
the
greatest
like
it,
it
will
be
indicative
if
so,
like
I
don't
know
if
you've
already
seen
like.
I
sometimes
like
put
a
note
like
no
this.
This
mock-up
is
indicative.
C
A
C
It
might
also
just
be
like
a
transition
thing
you
know
like
mike
was
very
mock-up
first
mock-up
forward,
I
I'd
say
so
it
could.
It
could
also
just
be
like
a.
D
And
if
they,
you
know,
you
talked
before
about
like
the
some
ways
they're
like
do.
They
need
to
be
high
fidelity
mock-ups.
I
wonder
if
you
can
get
away
with
something
else,
that's
less
time-consuming
right
and
maybe
it's.
A
Yeah,
I
I
I
see
exactly
what
you
mean
and
it
is,
it
is
I'll
I'll
tell
you
from
my
site,
yes
low,
fi
prototypes
or
mock-ups.
However,
you
want
to
call
them
should
be
easier
to
create.
A
On
the
other
hand,
we
have
this
amazing
design
system
that
has
full
fidelity,
easy
things
to
play
around
and
throw
in
your
screen,
and
unless
you
go
outside
of
that,
like
it's
quite
easy
to
to
create
them.
But
it's
more
like
it's
more
like
the.
A
This
thing
you
can
just
copy
and
paste,
because
otherwise
it
would
just
be
lines
and
wireframes,
which
is
fine,
but
I
don't
like
the
wireframe
balsamic
like
I'm,
not
that
fast
and,
like
I'm,
faster.
A
My
sketch
than
I'm
in
balsamic
yeah
and
I'm
not
a
big
sketcher
on
paper,
because
then
I
need
to
take
a
picture
of
it
and
I
cannot
write
my
read
my
handwriting
and
I
see
some
designers
do
that
and
I
just
like.
I
don't
know
how
you
do
that
like
I
can
try
it
out,
but
I
I
can
assure
you
it's
not
gonna
be
a
success,
or
at
least
I
think
so,
but
yeah.
A
I
think
the
collapsible
section
is
a
good
thing
and
just
like
the
general
call
out
of
that,
the
visuals
do
not
always
describe
the
full.
The
full
image
I'll
try
to
remind
if
need
be,.
C
C
C
In
this
particular
instance,
due
to
its
dynamic
nature,
just
like
having
having
the
full
thing,
there
could
have
maybe
saved
us
this
now
ongoing
ux
iteration
that
we're
we've
got
going
on
in
the
middle
of
this
m.r.
A
Yeah
all
right
learning
point
I
think
we're
pretty
clear
in
this
always
good
to
have
the
perspective
from
the
other
side
then
on
to
the
next.
Let
me
see
so
step
one
of
bros,
so
I
want
to
thank
chase
and
everyone
involved,
but
mostly
chase
on,
like
creating
this
ad
mention
handle.
A
We
now
have
at
our
disposal-
let's
not
use
the
spam,
but
I
think
it's
super
nice
that
if
you
are
gonna
close
an
issue
please
use
the
mention
handle,
so
you
don't
have
to
mention,
like
you
know
like
who
am
I
going
to
mention,
just
use
this
mansion
handle
and
it
is
now
defined
in
the
handbook
as
well.
So
that's
nice,
so
we
can
see
here
in
the
verification
process
like
hey.
A
If
all
cycles
are
to
be
informed,
just
use
this
pension
handle,
if
you
do
add,
progressive
delivery,
will
immediately
pop
up
click
in
hey.
This
thing
has
been
merged.
It's
looking
good
as
far
as
I'm
concerned,
and
then
I
would
say
like
if
we
go
off
this
this
this
copy
here,
the
owner
of
the
epic,
mostly
the
pm,
will
ensure
the
issue
fits
the
context
of
solution.
A
D
No,
I
mean
I
typically
issue
closing
happens.
Well,
it
seems
to
happen
right
by
the
engineer.
I
I
would
think
right
if
all
things
have
gone
up
to
verification
stuff's
on
in
the
right
place
right.
Is
that
not
the
case
or
are
we
suggesting
that
we
need
to
like
follow
back
through
with
with
some
with
with
the
pm.
A
Yeah,
so
the
thing
is
today
later
on
is
the
progressive
delivery
weekly,
because
I
was
originally
intending
to
bring
this
up
in
the
weekly
meeting,
but
I
think
orit
and
I
are
both
not
joining
because
it's
outside
of
our
time
zone
right
but
yeah.
I
would
love
to
have
a
less
check
on
that
by
ored
and
kind
of
lying
on,
like
hey
from
a
product
perspective,
I
would
like
product
to
close
the
issue,
because
if
that
is
the
case,
then
we
can
also
do
a
functional,
verify
and
mostly
concerned
with.
A
Like
hey:
did
we
have
any
follow-ups?
Do
we
need
to
create
any
new
follow-ups?
If
so,
let's
do
that?
Let's
mention
it
in
the
issue
and
then
actually
close
the
issue.
Then
it's
really
close
because
then
we
know
what
the
follow-up
actions
are.
Those
kind
of
things
I
think
currently,
that
process
is
a
little
bit
muddy,
like
the
engineer
closes
it,
but
you
know
the
exact
requirements
or
timing
when
it's
not
super
clear,
at
least
that's
how
I
view
it.
I
was
wondering
what
your
thoughts
are.
C
No,
I
don't
have,
I
don't,
have
a
stake
in
being
the
one
typing,
slash
clothes.
A
A
Yeah
yeah,
I
am
mostly
concerned
with
follow-ups.
C
C
A
So
yeah,
so
I
think,
like
my
intention
here,
is
fully
on
the
issue-
is
to
be
closed
after
follow-up
issues
are
created,
not
including
anything
into
the
current
scope.
That
is,
that
is
like
the
wrong
way
to
go
like.
I
would
not
not
advise.
That
would
be
horrible.
A
Yeah
totally
agree
I'll
put
this
up
in
the
the
agenda
cool
thanks
for
the
input
here
next
step.
A
So
this
is
the
important
part
where
I
wanted
to
get
to
so
I
was
discussing
with
nadia
on
the
merge
process,
so
this
is
like
the
the
thing
we
just
discussed
is
just
the
first
step
and
things
that
I
saw
like
hey,
we're
we're
missing
out
here
or
we're
not
following
the
process
as
we
have
defined,
or
you
know
those
kind
of
things
and
one
of
more
of
those
things
is
where
I've
brought
up
in
the
past.
A
It's
like
hey,
I'm
not
sure
about
this
merch
quest
like
I'm
not
included
or
I'm
not
aware
or
somebody
else
is
not
aware
or
there's
inconsistency
on,
like
the
process
that's
being
followed-
and
I
was
discussing
this
with
with
with
with
the
nadia-
and
she
says,
like
the
best
stage,
troops
that
she
sees
the
example
of
do
not
enforce
approvals,
which
I'm
a
big
proponent
of.
I
think
that's
amazing.
A
On
the
other
hand,
they
do
have
a
habit
of
over
communication
and
including
all
stakeholders
as
necessary,
and
this
is,
I
think,
where
we
can
do
better,
like,
for
example,
me
making
it
aware
that
hey,
I
saw
this
merch
quest
being
merged.
I
didn't
even
know
what
it
was,
or
I
saw
things
being
merged
with
your
exchanges
or
whatever,
and
I
was
not
aware
that
this
was
a
thing
like
it's
not
about
me
approving
the
merch
quest.
A
That
is
the
problem,
not
at
all
it's
more
about
like
me,
not
knowing
that
this
thing
even
existed
and
is
now
changing
the
process
for
our
end
users.
I
think
that
is
the
thing
that
we
need
to
to
solve,
and
I
think
that
is
not
only
for
me,
but
also
for
it.
That
is
for
technical
writing,
which
I,
by
the
way,
I
see
often
included,
which
is
amazing,
but
those
kind
of
things.
D
B
I
guess
if
you're
talking
about
ux,
I
actually
almost
never
seem
to
do
anything
that
affects
ux.
So
if
I
do,
then
I
would
usually
just
ping
ux
whenever
I
like,
as
soon
as
that.
Mr
goes
up.
A
Uh-Huh
and
then
in
terms
of
like,
let's
I
want
to,
I
want
to
open
up
this
discussion
to
beyond
ux
like,
of
course,
I'm
ux,
but
it
doesn't
mean
that
I
do
not
care
for
anything
else
or
only
ux
like
it's
like
in
general.
Like
let's
say
it's
a
back-end
only
merge
quest,
but
it
has
an
effect
on
performance
or
it.
It
enables
this
new
thing
through
the
api,
which
is
in
a
way
ux,
but
that
is
for
for
later.
A
You
know
like
hey,
who
do
you
include
who
like
when
it?
When
does
orig
know
this
thing
it
becomes
live
like
those
kind
of
things.
B
B
The
async
updates
that
we're
putting
on
issues
as
we're
working
on
them.
A
Updates
yeah,
that
makes
sense.
I
love
those
async
updates.
The
main.
The
main
thing
I
have.
What
I
would
like
to
see
for
those
async
updates
is
a
notification
like
I
don't
know
about
you,
but
I
work
with
to-do's
personally
and
I
seen
multiple
other
people
do
that.
A
I
don't
know
if
that's
within
professor
delivery,
but
I
do
not
see
when
an
issue
is
updated
unless
I'm
not
mentioned
so
when
I
see
an
async
update,
sometimes
like
oh,
this
was
from
four
days
ago,
or
this
was
last
week
and
I,
like
I,
don't
know
what
the
current
status
is
like.
I
think
the
key
and
the
feedback
I
got
from
nadia
was
like
there
should
be
some
kind
of
form
of
continuously
updating
each
other
or
keeping
each
other
informed
at
the
very
least
like
the
async
updates
kind
of
do
that.
A
D
So
when
we
talked
about
this,
you
know
months
a
few
months
ago,
when
we
adopted
this
sort
of
process
the
one
of
the
things
I
think
the
key
primary
concerns
of
other
people
were
how
not
to
spam
a
bunch
of
people
with
what
might
be
considered.
You
know
something
you
know
just
sort
of
like
here's,
an
incremental
update,
here's,
a
thing
that
is,
I'm
not
asking
for
any
action
on
for
you,
but
this
is
like
for
your
information.
This
is
helpful
for
a
wider
group
of
people
right.
D
So
so
we
haven't
done
that
in
those
async
issue
updates
to
ping
the
group
or
to
to
directly
alert
somebody
if,
unless
it's
like,
unless
it's
necessary,
so
I
mean
I
would
want
to
like
make
sure
we're
doing
that
correctly
or
well,
or
you
know
something
before
we
just
jump
in
and
start
pinging
the
entire
group
every
single
time.
C
I
don't
I
don't
personally
need
pings
from
the
new
tag,
every
time
that,
like
amy
or
etienne
or
jason,
do
something
is
working
on
something
you
know.
A
Yeah,
I
I
I
see,
I
see
what
you
mean
andrew,
like
it
was
not.
My
at
least
was
not
my
intention
to
intend
for
that
mansion
attack
to
be
used
all
over
the
place,
like
the
use
case
I
had
for
the
attention
tag
was
purely
for
the
verification
process.
Hey
we
are
like
this
is
in
the
product
right
now
like
this
is
this
is
done.
We
are
now
aligned
that
this
is
done
right
from
an
engineering
perspective.
A
I
assume
that
if
they
have
done
all
the
work,
it
is
super
duper
clear,
but
from
my
perspective
and
or
its
perspective
as
well,
it
is
often
where,
like
I
don't
know
like
if
something
works
yeah.
If
I
see
it
on
gitlab.com,
I
know,
but
if
it's
not
I'm
unaware,
unless
I
specifically
jump
into
the
issue
after
I
got
pinned
on
something
or
something
like
that,.
C
A
So
yeah,
I
think
this
is
a
very
different,
a
very
different
stage
of
the
process,
and
you
know
like
the
keeping
or
the
like
informing
stakeholders
at
the
end
is
like
all
right.
We
at
least
catch
everything
instead
of
dropping
some
of
it.
A
Now
it's
focus
on
the
rest
and
see
how
we
can
we
can
fix
that
in
in
a
way
that
makes
sense.
So
I
I
wouldn't
want
to
notify
all
engineers
in
like
when
you
post
a
merch
quest,
update
or
something
like
that.
That
is
not.
That
is
not
the
idea,
but
I
do
think
it
is
important
that
the
stakeholders
who
are
involved
with
that
specific
issue
are
updated
when
you
post
an
update,
because
let
me
let
me
phrase
it
the
other
way
around
you
were
creating
async
updates.
A
If
nobody
reads
them,
why
would
you
care
writing
them
right
and
to
kind
of
make
the
other
point
where
chase
where
you
were
describing
hey,
we
were
mostly
you
know,
aligned
with.
We
don't
want
to
create
spam
for
everyone.
B
A
So,
where,
where
do
we
like,
we
need
to
meet
somewhere
in
the
middle
which
works
in
in
in
a
good
way,
and
with
that
in
mind
I
would
say
I
mean
if
I
would
speak
from
my
personal
perspective.
I
would
love
to
be
like
if
there's
an
async
mr
update
ping
me
on
it,
like
just
ping
me
that
is,
that
is
awesome,
but
that
is
hard
to
describe
as
a
process.
A
I
think,
or
it
would
be,
welcoming
such
information.
I
don't
know
about
marcel,
but
you
know
which
other
stakeholders
are
there
to
be
included.
Perhaps
there
needs
to
be
created,
something
for
that
as
well.
A
I
don't
know
like
what
would
you
propose
for
you
know
for
such
things
to
happen,
because
my
next
step
in
this
case
would
be
like
all
right
I'll
invite,
for
example,
an
engineer
from
a
different
team
where
that
process
is
active
and
a
designer
from
that
team,
where
that
process
is
active
and
ask
them
like
all
right,
how
are
things
going,
your
team,
what
works?
Well?
D
Yeah,
I
mean,
I
think,
if
there's,
if
we're
I'm
wondering
the
first
thing
I
I
think
about
when
I
think
about
you
just
making
this
as
easy
as
possible
right,
I
want
to
be
lazy,
so.
A
D
Like
if
we're
using
a
tool
like
tall
tall
to
to
do
those
acing
updates,
I
think
there's
like
a
way
that
that
there's,
like
a
you,
know,
there's
some
kind
of
template
there.
That's
like
it,
builds
out
right
and
maybe
there's
a
way
that
we
can
use
that
use
that
template
that
it
provides
for
the
update
itself
to
also
include,
like
the
you
know,
to
cc.
D
You
know
a
subset
of
people
who
might
who
you
know
want
to
be
opted
in
all
the
time.
Somehow
you
know
re,
I'm
fine
to
have
it
too.
I
mean
I,
I
don't
know
how
it's
possible
if
I
can
get
more
email
than
I
already
do,
but
we
can.
We
can
try.
So
maybe.
A
A
Yeah
because
yeah,
I
agree
there
make
this
lightweight.
I
mean
like
just
to
start
off
with,
like
I'm
speaking
from
product
perspective
here.
Right,
like
I,
don't
speak
for
any
other
stakeholders.
For
me,
it
would
already
be
okay,
like
just
include
me,
in
order
just
say,
for
your
information
product
product
progress
delivery.
A
I
know
that's
too
much
mentioned
tags,
I'm
I'm
I'm
unfamiliar
with
tools
as
telltale
and
how
that
applies
to
gitlab,
but
just
not
mention
of
product.
When
you
give
an
update
would
be
more
than
welcome-
and
I
know
like
you
know-
maybe
I'm
selfish
here
a
little
bit
with
you
know
relying
on
to-do's
instead
of
emails,
but
I
yeah,
I
know
like
it's
a
gitlab,
supportive
feature
and,
like
I
know,
multiple
people
working
with
that.
A
A
A
A
The
feedback
that
nadia
gave
from
the
other
stage
groups
is
basically
this.
They
keep
each
other
informed
through
issues
slack
and
meetings
and
stand-ups.
That's
what
I
do.
So
it's
not
one
single
thing
that
fixes
the
problem
of
over
communicating
and
being
inclusive
in
the
in
the
build
process.
It's
like
all
right.
Where
are
we
today?
What
are
we
gonna
do
hey
by
the
way.
I
need
your
help
on
this
by
the
way,
hey,
I'm
creating
a
new
merch
quest,
because
I'm
scoping
out
this
small
feature
subset
hey
by
the
way
this
might
interest
you.
A
This
is
going
on.
I
decided
on
this
this
certain
way
of
going
forward,
p.s
think
about
including
this
other
person.
I
don't
know
it's
like
it's
it's
this
this
thing
of
when
you
do
something
who
can.
I
include
to
make
more
aware
of
this
thing,
I'm
doing
and
might
make
sense.
I
think
that
mindset
is
the
thing
that
like
gives
us
like
the
up
the
upside
the
like.
That
is
what
is
going
to
give
us
the
follow
through.
D
I
think
what
you're
getting
at
there
is
what
you've
alluded
to
before,
which
is
just
this.
This
idea,
and
this
this
comfort
with
over
communication
right
and
just
to
like,
hey,
hey
like
and
with
the
always
assuming
the
best
intent
possible
right,
like
dimitri,
probably
wants
to
know
about
this
right.
So
go
ahead
and-
and
let
him
know
like
and
just
you
know,
say
hi,
you
know
try
and
shift
behavior
that
direction.
A
D
I
mean
we
can
update
the
handbook
to
you
know,
make
that
clear,
and
you
know
a
clear.
You
know,
motivation
for
the
team
to
to
do
so
and
just
and
I
we
can
just
reinforce
it
right,
be
like
hey
and
do
and
do
the
opposite.
D
D
I
don't
know
it's
difficult
to
to
to
turn
into
a
a
process.
Type
thing.
I
think
this
is
more
yeah.
This
is
more
just
cultural
than
anything.
A
B
A
And
ninja,
I
have
a
management
issue,
I'll
link
that
here
I'll
also
describe
it
extensively
in
slack
channels
and
ayanna
will
be
covering
an
ian
from
package,
so
there
will
be
coverage
for
sure
and
I'm
trying
to
kind
of
neatly
wrap
up
things
this
week
as
much
as
I
can.
A
So
that
is
the
the
plan
for
me
going
out
of
office,
but
yeah
the
handbook
update
I'll
see
if
I
can
squeeze
that
somewhere
in
between
and
have
everybody
kind
of,
like
iterate
on
it
and
kind
of
acknowledge.
If
it's,
okay
or
not,
you
know
like
this
to
some
something
actionable
or
not
sounds
like
a
good
idea.
A
Thanks
for
all
the
input
today,
that
was
super
valuable
and
there
was
one
point
left
to
discuss,
but
we'll
do
it
another
time.
So,
thank
you.
So
much
bye,
bye.