►
From YouTube: CI/CD UX Meeting 2019-12-13
Description
By-weekly CI/CD UX Team Meeting to go over important updates, discussion items, feedback, etc.
A
Cool
nice,
so
I
know
that
you
have
had
some
discussions
on
the
last
session,
which
I
didn't
attend
due
to
my
day
off
about
the
capacity
for
the
UX
research
and
communicating
that
to
the
PM's,
so
you're
curious
like
so,
will
you
guys
move
this
topic
to
this
session?
What
were
some
of
the
outcomes
that?
Where
did
you
finish?
You
know
what
was
discussed.
Basically,
there.
B
Was
a
pretty
long
discussion
I
mean
I
like
multiple
views
and
there's
like
different,
like
perspectives
on
how
we
should
manage
this,
so
I,
don't
think
we
reach
to
like
a
concrete
conclusion.
Besides
like
yes,
we
need
to
communicate
our
capacity
to
our
PM's
and
we
need
to
find
a
good
way
to
do
that.
I,
don't
think
we
reach
like,
like
a
very
like
concrete
conclusion
and
I.
Think,
though
there
were
still
thoughts
like
regarding
these.
So
that's
why
we
moved
it
here.
Can
I
conclude
that
conversation.
B
A
B
I
thought
more
about
it.
I
I
definitely
can
like
was
more
mindful
about
it.
This
way,
with
my
PM's
to
see
how
I
was
communicating,
my
capacity
and
I
realized
that
it
may
be
I,
don't
know,
have
like
mechanisms
like
rapport
that
capacity
to
them
like
at
least
not
like
until
we
meet
and
like
we
say
like
we
go
throughout
the
backlog
on
the
roadmap
and
there's
like
okay
I
can
do
this.
I
can
do
that,
but
yeah
so
I
realized
that
maybe
there's
something
missing
which
is
CARICOM
more
like
they're.
B
Better
visibility
of
my
situation
is
a
little
bit
different
music
up
to
2
p.m.
to
group,
so,
like
I,
think
it's
very
important
for
them
like
how,
like
things
are
like
how
one
team
works
on
one
one
of
my
groups,
so
they
can
like
plan
against
my
work
there,
but
still
I.
Think
there's
like
an
opportunity
there
to
like
be
more
like
communicate
more.
You
know,
like
I,
don't
know
if
it's
like,
maybe
you
know
like
sharing
with
them,
like
a
aboard
in
slack
with
all
my
issues.
You
know.
B
Maybe
that
could
be
something,
so
they
can
just
go.
Look
into
that
like
a
synchronously,
but
that's
my
dear
that
I
had
or
maybe
just
like
kinda
like
telling
them
like
like
at
the
beginning
of
the
week
this
this
is
what
I'm
doing
is
week.
I
am
at
full
capacity.
Expect
me
not
to
be
available
to
work
on
these
I'd
be
more
practice.
That's
what
I
thought
I
like
those.
Those
were
the
thoughts
that
I
have
that
I
was
having
this
big
I,
don't
know
who
else.
A
C
C
C
So
the
idea
is
that
you
have
your
columns
of
problem
validation.
You
got
your
design,
workflow
design
and
workflow
solution,
validation
and
instead
of
filtering
down
for
a
milestone
we
filter
down
on.
You
know
your
as
a
nice
assignee,
so
you
I
filter
down
on
continuous
integration
and
the
author
me
Demetri
and
then
I
see.
You
know
my
issues
within
those
issues
within
those
columns
and
if
one
moves
to
the
next
or
one
moves
to
planning
breakdown
or
scheduling
whatever
it
means
that
a
spot
has
opened
up
to
some
extent.
C
That
is
a
simplified
way
of
looking
at
it,
because
we
don't
individually
wait
issues
and
I'd,
say
our
process,
and
then
this
will
be
different
than
engineering,
but
it's
it's
like
it
kind
of
visualizes.
In
a
way
you
know
hey
what
is
the
weight
or
what
is
the
current
effort
of
design
at
this
very
moment
and
if
something
changes,
then,
let's
hey.
Let's,
let's
review
this,
for
example
weekly
and
say
like
hey:
there
things
changed
versus
last
week:
hey
something
did
change
the
spot
opened
up.
C
D
D
So
it
tends
to
be
here's
a
bunch
of
stuff
and
then
this
is
the
time
slot,
we'll
add
it
and
then
I
just
kind
of
have
a
commitment
of
making
sure
each
thing
can
kind
of
be
done
in
a
time
range
and
it
flexes
in
weighing
so
I
try
to
keep
it
in
two
milestones,
but
I
try
to
reflect
like
the
solution,
validation
as
a
research
effort,
so
it
takes
a
little
longer
than
maybe
the
actual
design
phase
might
so.
I'll
try
to
pair
it
and
prep
for
the
solution.
D
E
D
D
I
tried
to
make
sure
there's
just
one
research
effort
hopping
in
a
milestone.
The
backlog
is
usually
emptier
on
my
side
than
it
is
on
Tim's,
just
because
it
goes
through
the
cycle
so
quickly,
once
it
hits
design
and
the
solution.
Validation
we're
working
on
figuring
that
out,
one
of
the
things
we're
going
to
do
to
try
to
do
that
is
12.7.
I'm
gonna
do
product
validation
and
let
him
have
an
extra
milestone
to
get
things
through
problem
validation,
mm-hmm.
D
Let's
the
we
defined
it
as
album
validation
is
Tim's
responsibility
he's
the
DRI
in
for
solution,
validation,
I'm
the
DRA,
but
we
try
to
partner
and
make
sure
that
our
research
efforts
are
aligned
and
and
I
get
involved
in
the
problem.
Validation,
so
I
can
understand
it
and
gather
the
information
I
need
and
he
sees
solution,
validation.
It
goes
through.
So
it's
a
partnership,
but
we
have
a
DRA
for
each
side.
So
in.
C
F
Better
be,
but
symmetry
that's
a
great
point.
I
actually
just
discussed
this
with
somebody
else.
The
research
team
I
need
to
go
back
to
all
of
our
product
managers
and
make
sure
they
understand
what
the
process
is.
I,
don't
think
they
do,
but
they
will
be
required
to
write
those
insights
just
like
we
all
are
writing
those
insights
to
put
them
in
the
repo,
otherwise,
the
research
that
they
do,
it's
not
usable
by
anybody
else
for
themselves
and
that
kind
of
sucks-
and
that
includes
not
just
the
problem-
validation,
any
customer
interaction
that
they
have.
D
The
answer
from
what
we've
been
doing
the
me
tree
is:
he
actually
ran
the
problem,
validation
sessions
and
recorded
them
all
and
then
I
went
through
and
synthesized
them
and
that's
how
he
partnered
on
it.
So
then
we
were
both
able
to
speak
to
it.
So
we
were
both
involved
in
creating
the
insights,
I
think
moving
forward
where
we
might
have
a
discussion,
because
the
insights
can
kind
of
take
awhile
of
splitting
that
effort
a
little
bit
more.
F
And
all
that
and
it's
a
new
insight
process
too,
like
I've,
never
done
it
this
way
either
I've
just
been
writing
like
45
page
PowerPoint
reports,
other
places
I've
been,
and
you
know
if
we,
but
if
you
don't
put
him
in
if
we
don't
break
him
down
and
put
him
into
the
repo,
what
will
happen
is
what
happened
to
me
the
other
day.
Hey?
Does
anybody
know
if
we
ever
did
any
research
on
XYZ
I
don't
know?
G
I
think
for
us
it's
it's
not
much
different
than
anything
else
in
the
sense
that
we
kind
of
talk
about
everything
that
needs
to
be
accomplished,
and
we
are
also
moving
to
the
Kanban
style
of
world,
which
will
give
us
a
new
board
planning
board
where
most
of
this
activity
can
happen
and
we
can
track
it
there.
Currently,
it
is
happening
on
the
mouse
owns
boards,
which
is
a
little
confusing
because
it
really
has
nothing
to
do
with
the
milestone.
G
That's
really
more
focused
on
upcoming
milestones,
but
really
no
I
mean
we
just
kind
of
talk
about
what
we
need
to
accomplish
from
design
for
a
research
side
and
development
side.
It's
all
kind
of
just
a
continuous
conversation,
because,
obviously
the
more
research
we
do
I
mean
unless
Lori
is
available
to
help
us
out
like
the
more
research
we
do,
the
less
design
we
do.
So
it's
all
kind
of
moving
target
of
what
we
need
to
accomplish
and
when
we
want
to
accomplish
it,
I.
A
See
nice,
it
sounds
like
everyone
is
figuring
out
the
way
to
do
it.
Yeah,
I
kind
of
like,
like
the
way
of
like
just
like
kind
of
like
setting
an
average.
We
pick
one
research
topic
per
milestone,
I
think
that's
kind
of
this
is
the
maximum
I
feel
like
we
can
do
with
there
all
of
the
work
design
more
than
we
need
to
be
done,
and
that's
kind
of
like
sets
these
expectations,
and
we
also
have
to
be
planning
for
that.
A
I
had
so
much
courses
all
today
discussing
that
it's
nice
to
plan
all
those
things
a
bit
earlier,
like
you
know,
kind
of
like
okay.
What
are
those
things?
Are
we
going
to
be
looking
in
one
or
two
milestones
just
to
give
everyone
a
heads
up,
because
I
like
I,
think
the
APM
should
be
able
to
do
that
planned
for
that?
It's.
D
If
you
will
is
when
we
kind
of
little
rope
rope
there,
we
go
Laurie
into
the
conversation
and
make
sure
that
she's
on
the
same
page
with
us,
it's
kind
of
helps
all
of
us,
because
then
it
is,
or
you
can
say,
this
is
a
really
easy
initiative.
Maybe
it
needs
less
time
and
we
can
work
it
here,
or
this
is
a
big
one,
like
you're
gonna
need
to
stretch
here
before
we're
in
the
milestone
where
it
starts.
A
I
suggested
that
can
happen.
Three
two
milestones
I
had
or
two
one
I,
don't
remember,
and
that
sounded
like
too
much
for
people,
and
there
were
a
few
comments
that
if
we
do
or
like,
if
you
plan
a
research
to
three
milestones,
I
had,
doesn't
it
become
obsolete
until
the
actual
development
time
will
come
like?
What's
your
experience,
there.
D
Sure
that
was
me
or
not,
I
didn't
want
to
step
on
any
toes
I
think
as
long
as
you,
Tim
and
I
have
like
very
clear
communication
and
conversation
about
like
if
things
are
flexing
and
changing,
and
it's
also,
we
have
the
belief
that
the
more
research
we
do
upfront,
the
faster
everything
else
is
going
to
go
for
us
and
the
more
likely
it
is
to
be
successful.
I
can
speak
to
that
now.
The
solution
validation,
we're
doing
because
we
did
such
thorough
problem
validation.
I've
been
getting
consistent
like
this
is
exactly
what
we
wanted.
D
This
is
what
we
needed
and-
and
every
designer
loves
that
moment
when
it
happens,
and
so
because
we
have
that
and
then
we
try
to
make
sure
the
research
is
big
enough,
that
it
could
be
a
couple
milestones
of
work,
so
we
were
doing
additional
gitlab
metadata
and
it
took
me
a
milestone
to
put
the
design
together
and
test
it
and
sorry
and
I
also
test
it.
But
there's
three
or
four
milestones
of
engineering
work
that
will
go
behind
those
changes.
D
A
Awesome
I
mean
what
I'm
able
not
look
for
love
with
you
a
little
bit
later
on
offline,
so
don't
take
people's
time,
but
yeah
I
think
this
is
this
is
a
this
is
kind
of
like
useful
I
think
for
us
to
see
what
others
doing
in
the
unloosed
age
group,
so
I
suggest
when
you
like
check
in
a
few
weeks
on
this
again
and
see
how's
everyone
going,
but
yeah
I
guess
like
what
I
can
suggest
is:
let's
exchange
some
experiences
to
make
sure
that
you
know
that
we
learn
from
each
other
and
if,
if
anything,
useful
will
come
out
of
this
craft,
I
will
keep
everyone
posted.
A
We
can
move
on
okay,
cool
Mike,
I've,
seen
that
you
pointed
this
one
out
from
the
about
the
ICSD
testing
project.
That
I
created
great
questions
thanks
for
asking
that.
So
let
me
give
you
a
little
bit
of
a
history
heads
up
for
30
seconds
and
then
yeah
feel
free
to
ask
me
this
question.
I
created
this
project,
basically
created
that
created,
SGI
CDU
acts.
A
Team
group
did
group
yeah
group
for
us
to
like
to
discuss
some
like
in
turn,
like
internal
team
process,
that,
for
example,
our
design
reviews
or
like
this
engagement
survey,
results
whatever
will
come
up
in
the
future.
So
it's
like
only
dedicated
to
our
team
and
also
created
one
of
this
SSD
testing
project
and
exactly
Mike
like
mine.
Go
for
that
was
to
put
some
data
in
there
that
we
as
a
team
as
a
product
designers.
A
G
A
G
No
I
think
we
chatted
about
this
a
little
bit
in
slack
of
the
day
and
I
think
that's
a
fantastic
thing,
because
I
mean
there's:
there's
really
no
way
to
do
that
unless
you've
set
up
your
own
personal
thing
or
GDK
and
a
situation
and
then
there's
always
that,
like
you,
gotta
somehow
connect
it
to,
especially
for
us
a
lot
of
things
you
got
to
hook
up
kubernetes
or
something
right,
usually
gka
before
you
can
like
really
test
out
some
of
the
edge
cases.
So
I
think
having
this
project
is
a
fantastic
thing.
G
I'm
give
I
know
when
I
started
here.
This
didn't
exist,
so
I
just
went
and
created
my
own
and
fooled
around
with
it,
but
then
eventually,
I
ran
out
of,
like
my
$300
credit
or
whatever
I
used
that
up
so
and
then
I
didn't
have
this
anymore
I've
since
gotten
access
to
the
there's,
a
demo
uke
thing
that
we
have
a
few
of
us
have
admin
access
to.
So
it
might
be
great
thing
to
hook
up
to
this
and
be
able
to
use
for
testing
and
stuff
like
that.
B
Also
might
be
I
definitely
soul
needed,
like
I,
also
have
the
same
problem
with
kubernetes
that
I
have
to
connect
something
and
like
what
I
was
gonna.
Do
was
expense
like
I,
create
like
a
micro
instance
in
Google
Cloud
and
then
like
probably
expense
that,
but
if
there's
a
way
to
like
avoid
all
that
and
just
have
a
project
that
not
only
has
to
burn
Eddie's
already
like
installed
on
everything
I
like,
but
also
like.
B
If
we
can
create
a
project
that
actually
has
like
a
lot
of
like
demo
jobs
running
like
it
has
like
a
complex
pipeline
running,
you
know,
so
we
can
go
on
like
see
all
these
functionality
and
test
against
that,
like
something
that
it's
simple
for
us
to.
Go
and
I
make
a
push
and
like
see
where
things
running,
but
that
it's
complex
enough
that
we
can
see
all
the
pieces
moving
right.
I
think
that
would
be
ideal.
Yeah.
A
This
is
my
call
exactly
I,
remember
my
days
of
CBO
labs,
where
not
sure
if
I'm
allowed
to
say
this
is
a
question.
I
really
needed
something
like
that.
But
I
was
close
to
the
engineers,
so
I
could
come
and
say:
hey.
You
may
be
an
instance,
and
then
that
would
be
going
not
some
testing
the
hell
out
of
it
yeah,
so
I
will
be
checking
on
that
I.
Restarting
the
PM
to
the
PMS
to
see
what
they
are
using.
I'm
kind
of,
like
collecting
information,
see
how
people
are
doing
that.
A
B
Can
also
look
into
exploring
like
a
demo
configuration
like
I
can't
like
spend
some
time
like
trying
to
see.
What's
something
but
like
creates
like
several
stages
and
they're
like
it's
simple
for
us,
just
maybe
I
don't
know
I
like
race
for
me
right
now
in
my
head,
but
I
think
like
I,
can
read
a
little
bit
about
that
and
see
see
what
I
come
up
with
yeah.
A
C
So
I've
been
reaching
out
in
the
previously
to
see
ICD
channel
in
slack,
but
we
also
might
want
to
think
about.
You
know
perhaps
like
a
process
that
we
can
ask
developers
for
such
things
and
we
can
assign
it
get
the
thing
set
up
and
now
we
are
able
to
just
doubt
the
kind
of
like
it's
it's
either
like
we
have
the
catch-all
strategy
and
you're
always
gonna.
Have
that
moment
that
you
know
that
one
example,
you
specifically
need
is
not
available.
So
you
end
up
in
the
same
position
anyway.
B
A
B
A
So,
let's,
let's
team
up,
if
someone
knows
anything
on
this
because
I
think
that
would
be
useful
for
me
as
well.
I
want
to
learn
and
I
found
it
really
challenging
like
setting
up
things
like
having
my
like
I
know,
setting
up
the
all
the
Google
accounts,
the
kubernetes
its
yeah.
You
need
the
instances
for
those,
and
that
was
a
bit
challenging
yeah.
C
If
you
set
up
like
a
kubernetes
cluster
through
your
Google,
like
get
like
Google
account
right,
you're
able
to
spin
up
like
a
cluster,
no
problem.
The
thing
is
with
that
that
you
also
need
to
think
of
the
active
in
the
end,
because,
like
a
cluster
costs,
you
like
40
bucks
a
month
or
something
or
45
and
every
once
in
a
while
there
might
be
a
maintainer
offer
or
Google
platform
might
do
a
cleaning
sweep
and
they
might
or
might
not
ask
you
to
yeah
they
closed
it
down,
and
you
know
forget
about
it
exactly.
A
Yeah
all
right
keep
going
to
the
next
topic.
I've
seen
that
you've
been
having
some
useful
discussions
about
EBT,
fine
UI,
app
ik,
so
I
already
talked
to
Marcel.
That
was
a
good
idea,
thanks.
So
much
for
whoever
proposed
that
and
basically
I've
seen
also
Dimitri
was
pointing
that
out
during
the
previous
meeting
that
so
all
the
like.
The
goal
of
the
beautifying
UI
epic
was
to
burn
out
to
burn
down
all
of
them
epics
to
zero
and
I.
A
A
That
would
that
would
like
the
goal
of
that
team
is
exactly
also
focusing
on
this
kind
of
thing,
so
like
working
with
the
components
and
like
focusing
on
the
consistency
and
all
of
the
small
kind
of
edifying
issues,
so
that
would
move
in
a
future
to
that
team.
I'd
know
if
that
answers
all
of
the
questions
that
that
you
had
in
the
previous
meetings.
B
That
sounds
me:
I'm
gonna
reach
out
to
my
cell
to
see
if
I
can
buy
if
he
has
more
issues
while
they're,
not
in
the
epic
but
thinks
there's
things
that
can
be
done,
then
I'm
happy
to
do
that.
I.
Really
it's
five
right,
I,
like
five
or
six
yeah
yeah.
A
B
Well,
I
for
all
the
things
that
I
have
been
doing
with
the
beautifying
UI
I
haven't
you
should
really
care
like
a
lot
so
and
then,
like
I,
have
a
couple
of
projects
that,
like
I
a
couple
of
em,
are
a
review
on
the
GDK,
but
then
I
also
have
another
handful
that
are
like
on
different
repos,
like
runner,
leaves
in
a
different
repo.
Before
with
you
leaves
in
a
different
window.
So
for
those
you
don't
need
typically,
but
I,
guess
that
I
use
GDK
a
lot
awesome.
G
I
set
it
out,
but
I
used
it
a
little
bit.
It
was
more
like
when
I
was
getting
on
board
I
set
it
up
to
see
if
I
could
and
got
in
there,
and
that
was
fun,
but
I've
been
getting
lucky
lately
on
the
issues
where
the
front-end
engineers
been
making
great
screenshots
and
even
going
so
far
as
making
videos.
Things
like
that
that
have
made
it
less
necessary
so
may
need
it,
but
just
seem
to
be
getting
by
the
last
couple
of
milestones
without
really
needing
it
too
much.
C
I
accused
it
from
time
to
time
I
would
say.
In
the
last
last
half
years,
I've
been
shipping
heavily
towards
renew
and
requesting
them
from
developers,
because
I
I
found
that
you
know,
spinning
of
the
UDK
is
often
exceeds
I'm,
saying
just
losing
so
much
time
doing
nothing
basically
fixing
errors
that
come
up
with
spinning
up
the
GDK
every
once
in
a
while.
If
you
don't
do
it
for
a
couple
of
you
know
like
a
week
or
is
when
athletes
that
means
you
know
your
libraries
are
out
of
date.
C
B
A
I
see
cool
well,
the
reason
why
I'm
asking
is
because,
like
after
our
discussion
with
with
Marcel
he's
like
think
that's
it,
that's
really
that's
really
cool
everyone
on
the
team
tried
that
except
me,
I
didn't
yet
set
it
up,
but
that's
on
my
to-do
list.
I
wouldn't
try
that
feature
as
well.
Well,
I
want
to
understand
the
development
experience.
I
think
that's
pretty
important
for
us
to
go
through.
It
would
yeah
yeah.
It
would
be
nice
if
it
would
be
coming
back
to
that.
I.
A
Think
if
you
see
some
with
some
improvements
to
do,
we
should
reach
out
to
the
engineering
teams
with
the
feedback,
but
I
feel
like
it's
very
important
to
have
that
experience.
You
know
what
are
we
talking
here
about
because
the
point
that
we've
been
discussing
with
Marcela
she
said
that
not
every
designer
you
have
done
that
and
I
was
just
curious.
You
know
how
are
we
I.
B
Have
contributed
to
the
dedicating
stuff
like
documentation.
I,
like
I,
wrote
some
documentation
from
them
in
like
how
to
set
up
your
GDK,
like
I,
think
we
had
like
a
big
portion
on
how
to
like
set
up
Ruby
that
wasn't
there.
So
I
wrote
that
for
them
and
I
definitely
have
seen
more
areas
of
help
like
that
and
more
things
that
I
could
hop
there.
B
C
Has
been
helping
out
in
this
regard
to
make
it
a
little
bit
easier
Tbk
we
created
this
merge
request
that
allows
you
to
basically
spin
up
the
GDK
from
the
reference
point
of
a
merge
request
ID,
so
you
can
just
input
the
ID
and
it
does
everything
for
you.
Thank
You
Gabe
gets
the
libraries.
You
know
it
does
everything
basically,
but
it's
very
much
in
beta,
and
it
means
additional
users
to
push
this
forward
and
also
we
you
know
we
should
in
that
sense,
if
we
finally
get
people
to
do
this,
push
see.
C
Jade
like
hey,
we've
noticed
these
new.
These
new
failures
can
you
fix
them
and
eventually
were
right.
We
really
want
to
push
this.
We
could
get
this
done
within
three
weeks,
but
it
beats
dedicated
effort
and
also
some
other
ability
from
zj,
of
course,
but
I
have
seen
it
working
and
it
works.
It
is
pretty
amazing.