►
From YouTube: CI/CD UX Meeting - 2020-10-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).
B
We
have
a
couple
of
fyi's
added
to
the
agenda.
I'm
gonna
just
quickly
read
them
because
I
think
they're
relevant
for
the
ones
that
are
not
seeing
the
call
today,
I'm
dropping
at
5
30..
That's
not
super
relevant
to
people
that
are
not
here
right
now,
but
I'm
still
double
today.
B
So
I
see
that
we
don't
really
have
a
lot
of
items
in
the
agenda,
so
we
might
be
able
to
finish
a
bit
earlier
and
nadia
udallah
is
on
pto
from
the
23rd
of
this
month
until
her
last
day,
her
last
day
is
actually
october
30th
and
if
you
need
something
from
her
next
week,
make
sure
that
you
bring
her
so
that
she
can
come
back
on
it
on
friday
and
vitica
is
going
to
be
the
entering
product
designer
for
testing
runner.
Thank
you.
Vitica.
B
C
Is
it
no
not
yet?
No
I'm
just
our
election
is
november
3rd,
so
I
might
be
taking
the
fourth
off
too
we'll
see
how
it
goes,
and
then
it's
just
the
next
week
is
just
I
got
to
get
away,
so
the
thanksgiving
is
the
fourth
thursday
of
every
november,
so
that's
probably
later
in
the
month
so
end
of
the
month.
Awesome.
B
That's
it
for
fyis,
I'm
going
to
jump
to
the
next
topic.
That's
actually
mine,
so
I
just
want
to
share
the
on
release
management,
the
learnings
and
the
recap
of
our
three-year
vision.
Dimity
is
not
here
today,
but
it
will
be
awesome
to
get
his
insights
later
on
on
the
process,
and
I
just
want
to
share
a
little
bit
how
it
went
for
us.
B
I
think
it
took
around
maybe
two
milestones
for
us
to
get
to
like
you
know
the
first
step
first
phase
done
and
what
I
wanted
to
highlight
here
is
a
little
bit
of
the
steps
that
we
took
and
what
worked
for
us
and
what
didn't-
and
I
already
discussed
this
a
little
bit
with,
especially
with
you,
girls,
with
kinda,
getting
the
issue
for
verify
for
ci.
But
for
us
what
was
really
important
was
that
pms
were
guiding
the
vision,
so
we
had.
B
We
define
the
scope,
and
then
we
set
the
due
date,
which
was
september,
and
actually
we
missed
that
deadline
at
first,
but
from
there.
Another
thing
that
really
helped
was
that
the
pms
documented
the
vision
in
the
handbook,
even
though
we
didn't
really
have
the
design
or
like
deliverables
anything
ready.
It
was
added
to
the
to
the
handbook.
B
B
Here
let
me
actually
share
my
screen
quickly,
so
that
the
others
can
see
what
I'm
enjoying
there's
an
epic
here
for
the
main
effort,
and
I
think
we
had
like
maybe
six
eight
different
flows
and
ideas,
but
they
chose
the
top
two
flows
so
for
us,
notifications
and
deployments
with
runbooks
and
deployment
approvals
and
feature
flags.
So
they
do
have
a
lot
of
common
features.
So
dimitri
and
I
divided
that
and
met
in
person
first
well.
B
We
could
do
that
because
we're
both
in
the
netherlands,
so
we
met
in
person
to
kind
of
like
define
the
plan,
and
then
we
shared
the
responsibilities.
So
we
worked
together
on
figma
and
we
decided
to
go
high-fidelity
from
the
beginning
because
we
didn't
want
to
go
back
to
this
later
on.
B
The
idea
and
the
main
goal
is
that
pms
wanted
to
product
wanted
to
have
this
figma
file
as
assets
that
they
could
show
to
marketing.
They
show
to
sales
and
not
only
to
potential
customers,
but
also,
while
doing
you
know,
user
inter
customer
interviews
to
kind
of
just
give
them
a
taste
of
what
city
is
going
to
look
like
right
now
or
up
to
that
point.
B
Jackie
had
like
document
like
word
documents
with
tables
and
kind
of
like
you
know
the
the
super
low
fidelity
of
iframes
that
she
was
using,
and
then
we
just
wanted
to
convey
the
story
in
a
different
way.
B
So
we
prototype
those
two
flows
that
you
see
here
in
sigma
and
from
there
dimitri
and
I
met
with
them.
We
scheduled,
like
some
milestones,
that
we
could
review
it
with
them
and
they
also
left
their
feedback
here
in
figma
on
the
fly
and
yeah.
That's
pretty
much
it
after
everything
was
done.
We
made
this
a
clickable
prototype
and
they
added
the
final
version
to
the
the
handbook
page
so
kind
of
supporting
the
release
vision.
We
have
also
the
figma
prototypes
that
customers
and
well
pretty
much
anyone.
B
As
I
said,
it's
the
only
part
of
the
story,
but
I
think
that
what
worked
for
us
was
really
you
know
not
trying
to
kind
of
reinvent
the
wheel
in
the
sense
of
using
different
ui
components
or,
like
you
know,
fixing
anything
in
the
product.
B
Was
it's
really
about
showing
how
it
would
look
like
on
gitlab
today
so,
for
example,
rum
books
and
from
here
it's
where
we're
going
to
you
know
we
start
a
conversation
with
our
developers
to
see
how
can
we
break
this
into
an
actual
deliverable
and
what
do
we
need
to
change
to
make
this
com
come
true?
B
That's
it
and
then
next
step
pms
are
going
to
record
a
walkthrough
based
on
our
prototypes
and
then
they're
gonna
share
the
customers.
The
way
I
mentioned-
and
I
see
davita
made
some
comments
here.
I'm
gonna
stop
sharing.
If
you
want
to
vocalize
that.
D
B
Mockup,
I
think
the
mock-ups
are
ambitious
in
a
sense,
but
they
are.
How
can
I
say
put
that
like?
As
I
say,
they
don't
reinvent
the
will,
so
our
ambitions
here
is
really
to
look
at
the
items
that,
if
you
look
at
the
direction
pages,
for
example,
for
release
management
and
progress
delivery,
you
can
actually
pinpoint
some
of
this
ui
some
of
the
ui
that
we
built
two
things
that
we're
gonna
build
this
year
or
next
year.
B
So
it's
really
like
related
to
things
that
we
are
either
currently
validating
or
that
we're
gonna
validate
soon
or
we're
gonna
build
soon.
So
when
it
comes,
for
example,
to
all
the
overlapping
with
ci,
that's
too
far
ahead,
we
haven't
validated
any
problems
around.
You
know
yet
things
that
are
in
probably
laura's
backlog.
B
D
Right-
and
I
think
another
thing
that
I
was
curious
to
know
was
I
mean
in
terms
of
the
features
that
you
have
proposed
like?
Is
there
a
plan
on
how
they
are
going
to
progress
like
do
you
have
a
plan
chopped
out
already?
I
know
that
things
eventually
they
change
they
develop
once
they're
out
once
they're
released
and
customers
start
start
to
give
their
feedback.
Many
things
would
be
altered
from
there
on.
But
to
begin
with,
do
you
have
a
roadmap
for
each
of
these
features.
B
We
do,
and
if
you
look
at
the
I'm
going
to
link
here
to
the
agenda,
if
you
look
at
the
release
management
ux
page,
I
linked
the
the
category
so
release
arbitration
release,
evidence
pages
whatever
and
on
each
category
we
talk
about
the
maturity
plan.
So,
for
example,
if
I
go
to
release
orchestration,
let
me
share
my
screen
again
to
kind
of
show
you
how
I
referenced
this
back
to
the
overall
plan.
This
is
the
release
orchestration
page.
So
here,
for
example,
we
have
run
books
are
complete.
B
The
next
steps
for
us
is
group
environments
associated
with
milestones
releases,
auto
change
log
for
releases.
So
when
we
look
at
the,
for
example,
the
prototypes,
this
is
really
like
something
minimal
that
you
know
is
shown,
for
example,
maybe
one
of
these
areas
in
the
prototype.
So
it's
not
really
about
linking
or
building
the,
at
least
for
us,
wasn't
about
building
the
prototype
for
to
feedback
in
the
features,
but
how
this
small
change,
for
example,
or
the
small
feature
binary
assets
to
release,
would
look
like
in
the
release
page
and
release
evidence.
B
B
A
Yeah,
it's
very
cool
that
you
already
have
this
roadmap
for
these
features,
and
it's
something
that
I
think
we
don't
have,
and
one
of
the
reasons
is
that
the
way
you
started
working
on
this
hyanna,
like
we
touched
this
in
our
upon
this
in
our
one-on-one,
was
it
was
really
driven
by
product.
So
those
were
already
validated
problems
that
product
managers
knew
that
we
want
to
be
solving
and
you
were
given
a
task.
Okay,
now
imagine
what
it
might
look
like.
A
I
don't
know
if
it
was
the
same
for
yukitika,
but
for
me,
like
I
already
tried
to
get
some
direction
and
I
I
was
told
to
just
like
look
at
the
competitors
and
just
gather
some
inspiration
and
just
come
up
with
something
completely
crazy,
so
we
really
came
up
with
something
super,
visionary
that
really
and
that's
why
we
stopped
vitica.
You
started
with
low
fidelity
because
it's
important
that
we
show
that
it's
so
visionary,
so
it's
like
our
path
towards
getting
it
so
refined.
D
It's
gonna
be
really
long,
that's
right,
so
one
thing
that
I
did
was:
I
had
my
one-on-one
with
tao
today
and
I,
like
I
requested
her.
I
like
mentioned
about
the
conversations
we've
been
having
on
the
issue
and
I
think
it's
time
that,
like
product
steps
into
it
and
kind
of
provides
us
with
the
direction,
because
if
it
still
remains
in
our
control,
we
might
I
mean
we
have
been
going
crazy.
With
that
we've
been
going
in
all
directions,
I
would
say
we
need
to
be
streamlined.
Now.
B
Yeah
and
even
if
it's
like,
they
want
you
to
be
visionary,
they
have
that
vision
in
their
heads
as
well
right.
They
know
the
market,
they
know
the
product,
so
I
think
it's
a
maybe
it's
an
exercise
also
for
them
is
to
just
spill
out
these
ideas
and
say
this
is
how
it
was
going
to
look
like
in
a
specific
task.
For
example,
I
don't
know
creating
a
pipeline
and
setting
up,
merge
trains
and
getting
notifications
and
whatever
just
that
one
flow.
B
D
And
in
the
process,
I
noticed
one
more
thing
I
don't
know
nadia.
You
might
agree
with
this
that
there
are
actually
some
problems
that
we
are
trying
to
solve
both
nadia
and
I
that
would
really
need
a
very
drastic
change
in
the
user
flow.
I
mean
things
really
have
to
move
from
here
to
there
and
those
solutions
they.
It
would
be
very
difficult
to
take
them
into
a
very
small
like
like
cut
them
into
very
small
mbcs,
and
it
would
be
a
very
tricky
exercise.
B
A
Yeah,
I
agree
I
mean
we
would
have
to
just
do
it
super
iteratively
and
try
to
still
kind
of
build
up
somehow
the
path
from
the
solution
that
we
have
today
and
we're
kind
of
trying
to
do
that.
A
But
yeah
honestly,
I
wouldn't
say
it's
going
super
well
like
just
because
there's
been
also
lots
of,
so
it
was
a
very
ambitious
undertaking
as
it
is,
but
also
there's
the
added
complexity
that
now
we
have
two
teams
and
python
authoring
team
is
new
and
there's
just
like
lots
of
kind
of
misalignment
still
in
the
way
different
people
work
on
the
team,
and
that
is
making
things
difficult
like
today
we
had
a
one-hour
meeting
around
the
mvc.
A
That
kind
of
is
leading
up
to
the
things
that
vitika
and
I
are
working
on,
and
even
just
that
first
step.
No
one
can
agree
on
what
to
do
so.
I
wonder
like
what
would
be
the
best
way
to
frame
this
and
get
this
direction
from
the
product,
because
just
asking
honestly
didn't
work
for
me.
So
I'm
not
sure
how
how
to
approach
this.
C
I'd
say:
let's
schedule
a
half
day
and
let's
go
in
a
conference
room
with
a
lot
of
sticky
notes
and
some
sharpies,
and
let's
just
talk
about
how
we
want
this
thing
to
be.
I
think
it's
a
little
harder
to
do
that
remotely,
but
still
can
be
done.
C
So
maybe
maybe
it's
getting
together
with
your
product
manager
synchronously
over
zoom
with
a
mural,
and
you
start
brainstorming
and
not
try
to
keep
them
to
a
linear
path
of
you
start
here
and
you're
going
to
end
up
there.
Instead,
it's
let's
start
taking
concepts
or
ideas
or
topics,
and
let's
talk
about
those
where
we
want
it
to
go.
C
Where
is
it
today
and
then,
as
you
build
the
mural,
maybe
group
those
things
together
in
those
those
ideas
of
those
topics
and
then
step
back
in
another
meeting,
come
back
later,
a
couple
days
later
to
that
billboard
again
and
say:
okay:
this
is
what
we
brainstormed
now,
how
does
it
all
fit
together?
How
does
that
look
for
the
consumer,
the
user?
How?
How
does
that
fit
for
that
software
developer?
C
What
what
what
is
their
journey-
and
it
may
be
different
journeys
for
different
people,
but
like
how
does
that
all
fit
together,
and
maybe
that
might
help
them
to
to
come
out
of
all
that
with
like
this,
this
amazing
vision,
because
it
is
hard
it's
like.
Oh
my
god,
I
don't
know
where,
like
I
don't
even
know
how
to
write
a
story,
let
alone
finish
a
story.
How
do
I
begin
this
story
and
it's
a
lot
of
pressure
just
to
spew
it
all
out
at
once.
So
maybe
something
like
that!
C
Yeah,
no,
you
cannot.
You
should
not
be
doing
this
by
yourself.
You
have
to
be
there
with
product
product
has
to
be
there
with
you,
because
they
have
more
domain
knowledge.
They
have
more
competitor
knowledge,
they
have
whatever
they
have
in
their
head,
bringing
to
the
conversation
yeah.
This
should
not
be
something
that
you
do
by
yourself
at
all.
It
must
be
a
team
sport
get
somebody
from
engineering
in
there
too,
because
they
need
to
weigh
in
on,
like
just
from
their
perspective.
What
they
see
are
the
problems.
Yes,.
A
That's
a
great
idea,
lori.
Actually
it's
it's
something
that
I
was
kind
of
proposing
as
the
next
steps
for
this
three
year
vision.
So
my
idea
is
to
first
collaborate
with
vitica
on
kind
of
just
just
asking
some
questions
around
the
prototypes
that
we
have
currently
so
just
put
our
flows
together
and
just
just
write
out
the
questions
that
we
have
the
gaps
that
we
see,
the
limitations
that
we
see
and
just
generally
kind
of
try
to
set
the
stage
and
then
get.
A
Maybe
we
can
address
some
of
those
things
as
we
do
that
or
propose
some
proposed
some
ideas
and
solutions,
and
then
we
get
on
a
call
together
with
the
pms
and
the
engineers
and
I
think
yeah.
Maybe
it
could
be
helpful
to
do
something
more
open-ended
like
this,
where
we
get
together
and
we
just
allow
everyone
to
share
whatever
mess
of
the
ideas
that
they
have
like.
A
The
pms
actually
there's
been
much
more
feedback
from
the
engineers
than
from
the
pms,
and
I'm
just
like
really
so
we
just
got
it
it.
So
we
just
took
our
first
pass
on
division
and
boom.
That's
what
we're
gonna
be
building,
I'm
not
sure,
I'm
okay
with
that
kind
of
responsibility
and
pressure
like
I
would
like
someone
to
you
know
validate
it
somehow.
C
Yeah
and
that's
why
I
said
I
think
you're
going
to
have
to
be
the
organizer
of
of
the
effort,
and
you
would
tell
them
like
you
have
to
be
there
like.
You
are
part
of
this.
You
need
to
be
there
and
and
see
where
it
goes
and
have
that
conversation
with
them,
because
there's
value
in
doing
it
asynchronously,
but
there's
also
value
in
doing
it.
Synchronously
and
anytime
you're
doing
like
a
brainstorming
thing.
C
I
found
that
it's
just
simpler
and
easier
to
be
able
to
verbally
talk
and
throw
stuff
up
on
the
wall
or
like
metaphorical
wall,
and
instead
of
trying
to
do
it,
asynchronously
so
yeah,
yeah
and.
B
C
C
There's
a
point
around
the
asynchronous
communication
around
like
here's,
something
where
you
guys
think
in
engineering's
weighing
in
and
then
there's
that
point
of
okay:
let's
bring
it
all
together
and
let's
talk
about
it
at
a
higher
level
and
then
we
can
get
down
and
dirty
deeper
into
it
later.
As
we
talk
about
it.
B
Yeah
yeah-
and
I
just
wanted
to
stress
here
that
it's,
I
think,
especially
in
something
like
this
type
of
calls-
that
they're
gonna
last
for
probably
more
than
one
hour,
it's
important
to
have
a
facilitator,
a
dri,
and
I
would
you
know,
recommend
it
to
be
one
of
the
pm's.
I
had
to
hear
the
link
to
the
first
recording
or
a
first
session
for
the
release,
video,
and
it
was
clear
that
jackie
was
a
facilitator.
She
was
really
like
trying
to
get
that
information
from
audits
trying
to
get.
You
know
the
ideas
from
jason.
B
I
could
not
do
that,
like
I,
don't
know
how
things
connect
in
such
a
deep
level,
because
I
don't
have
the
domain
knowledge
like
they
do
like
they
were
release
managers
they
work
with
ci
cd
every
day
so
really
make
you
know
the
dri
clear
from
the
beginning
and
yeah
be
there
to
take
notes
and
to
absorb
information,
but
if
they
are
not
pushing
this
like,
if
they're
not
owning
this
process,
I
would
say
give
them
the
monkey,
because
it's
their
problem
too
or
it's
the
problem.
You
know.
C
Yeah-
and
you
might
run
into
the
problem
because,
like
dove,
is
new
to
this
space
like
moving
from
apm,
you
know
it's
not
like
a
completely
different
place,
but
it's
new,
so
he
may
not
have
enough
domain
knowledge.
Tau
may
not
have
enough
domain
knowledge
either.
So
you
may
have
to
look
at
someone
else
to
come
in
to
help
facilitate
it.
C
Jason
would
be
a
good
person,
but
there's
soon
to
be
no
jason.
So
that's
useless.
I
don't
know
how
kenny
feels
about
it,
but
he
might
be
a
good
resource
to
point
you
to
somebody
who
might
be
able
to
serve
as
that
domain.
Knowledge
facilitator
as
well.
B
This
was
awesome.
Thank
you
so
much
for
yeah
sharing
all
this.
These
thoughts,
I'm
also
gonna
ping,
jackie,
to
see
how
else
she
can
contribute
there.
Maybe
she
can
also
help
share
some
of
the
learnings
with
the
pms
and
kind
of
try
to
push
this
a
bit
forward.
Awesome.
B
I'm
gonna
quickly
jump
to
the
next
topic.
It's
about
process.
We
have
the
ux
okrs,
the
f21q4.
Please
feel
free
to
review
them
and
yeah
leave
a
comment.
If
you
see
something
that
it's
not
clear
or
that
you
think
could
be
improved,
we
still
have
migration
or
we
have
migration
again
of
pajamas
components.
So
I'm
going
to
create
the
cicdux
okrs
once
everything
is,
it
is
done
and
once
nadia
closes
the
q3,
oprs
and
yeah
as
always
you're
free
to
assign
things
to
yourself.
B
C
I
was
just
looking
at
the
research
team
to
see
if
we
had
any
specific
okrs
yet
not
yet
okay,
so
I,
as
you
probably
have
known
already,
ladies
I'm
gonna,
step
away
from
being
so
involved
on
the
day-to-day
research
activities
for
everybody
and
moving
more
to
a
strategy,
strategic
viewpoint,
and
so
yesterday
I
created
this
epic,
where
all
of
the
currently
known
to
anybody,
strategic
ideas
have
been
captured.
C
I
created
them
all
as
issues
and
this
lives
in
the
research
project
and
kenny,
I
think,
has
gone
in
there
and
prioritized
those
issues
as
well
yesterday
or
this
morning.
So
that
helps
so.
If
you
have
anything,
you
want
to
contribute
to
any
of
those
issues
feel
free
to
get
in
them
and
right
there
in
those
issues,
that's
one
of
the
reasons
I
created
the
epic
is
so
we
can
kind
of
capture
all
those
discussions
there
and
then
capture
any
overarching
discussion
around
prioritization
and
effort
in
the
epic
itself.
C
So
I
expect
maybe
to
have
another
epic
later,
like
as
things
change,
we'll
see,
we'll
see
how
it
goes.
But
this
is
where
we're
going
to
start
all
the
discussions
and
stuff.
So,
as
far
as
I
know,
I'm
going
to
continue
doing
the
pipeline,
the
ci
adoption
work.
We've
had
really
a
tough
time
with
the
recruiting.
C
As
you
all
know,
so
we
will
be
wrapping
it
up
at
the
end
of
this
month,
which
is
what
we'd
hoped,
but
most
likely
before
thanksgiving
and
then
after
that
kenny
and
I
discussed
about
like
looking
at
the
findings,
understanding
what
we
now
know,
hopefully
from
the
research
and
then
figuring
out,
if
there's
other
opportunities
for
that
particular
topic
or
moving
on
to
the
next
one
in
the
list.
B
C
B
All
right
anything
else,
ladies:
we
have
a
retro
here,
I'm
not
sure
if
everyone
already
replied
to
the
13.5
milestone.
If
not,
please
go
ahead
and
do
it
it's
important
for
us
to
keep
track
of
everything
and
also
help
improve
or
process
it
as
a
higher
level.
B
I
got
a
drop.
I
I'm
double
booked,
but
yeah
by
all
means.
Let
us
know
if
you
have
anything
else,
we
can
keep
discussing.
A
Super
helpful
yeah
thanks
so
much
hayan
and
lori
for
sharing
your
ideas.
Now
I
feel
much
better
about
the
platinum
going
forward.
I
really
like
this
idea
of
having
this
cross
not
cross
team,
but
cross-functional
brainstorm.