►
From YouTube: Verify & Release By-weekly UX Meeting | 6th May 2020
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
All
right
so
welcome
everyone
to
the
verify
and
their
release.
You
acts
by
a
weekly
meeting.
We
are
with
a
smaller
group
of
people
today,
Demetri
is
not
joining
due
to
the
time
zone,
so
I
got
some
Maurice
busy
wrapping
up
some
other
stuff,
but
yeah
thanks.
Everyone
for
joining
I
see
that
we
have
couple
items
on
the
agenda
added
and
feel
free
to
add
some
more
while
we
are
talking
but
yeah.
Let
me
go
one
by
one
then,
so
we
don't
have
anything
in
the
items
format.
A
B
So
we
have
a
few
things
that
we
have
like
juggling
around
the
first
one
I
think
is
we
finished
a
research
for
the
point.
Aws
and
a
bunch
of
stuff
came
up
there
and
some
really
interesting
ones
like
it
turns
out
that
people
are
not
necessarily
using
environment
variables
in
order
to
store
their
AWS
variables
and
they're
using
different
types
of
methods.
B
So
one
thing:
that's
really
interesting
is
what
kind
of
integrate
integration
we
can
do
with
additional
I,
don't
have
to
call
secret
managers,
but,
like
AWS,
has
their
own
like
secret,
store
and
things
like
that.
So
that's
something
I
also
talked
about
with
Jackie.
That's
super
interesting
to
integrate,
because
I
know
there's
a
lot
of
work
now
with
vaults
and
it's
it's
not
necessarily
the
only
path.
So
that's
something
interesting.
B
So
probably
gonna
do
some
solution,
validation
with
Demetri
Ahmed
at
some
point.
So
that's
really
really
interesting.
We
have
some
additional
interesting
things
that
we're
working
on
now.
So
one
of
the
things
that
we
want
to
do
is
there
was
a
big
generic
research
effort
around
load
balancing.
So
today
we
support
advanced
deployments
canary
and
incremental
rollout
for
kubernetes
only
and
we
don't
support
any
any
other
like
custom
is
about
custom
abou,
advanced
employment.
It's
either
what
we
have
in
Auto
DevOps.
Are
that
or
you're
done?
B
That's
what
you
have
to
do
so
we
figured
out.
We
need
to
develop
a
load
balancer
and
we're
gonna
start
with
the
NGO
next
one.
So
we
are
starting
with
kubernetes
first,
but
I,
don't
know
if
it's
gonna
stay
like
that
forever,
but
there's
a
bunch
of
things
that
we
need
to
have
the
user
be
able
to
configure
in
terms
of
like
weights,
so
for
blue
and
greens
employments.
We
need
to
introduce
primary
deployment
and
a
secondary
deployment
and
be
able
to
switch
between
them
and
being
able
to
switch
with
them
with
them
with
weights.
B
So
I'm
not
really
sure-
and
this
is
a
conversation
I-
have
with
Demetrius,
where
we're
going
to
place
these
things
to
configure,
because
I
have
no
idea,
there's
like
different
options
or
maybe
just
rethinking
everything.
So
we
have
like
a
lot
of
things
to
talk
about,
and-
and
this
also
has
a
lot
of
work
to
do
with
the
deploy
boards,
because,
if
you're
switching
from
blue
to
green,
you
pretty
much
want
to
know
if
you're
a
primary
or
a
secondary
in
your
deployment.
B
So
the
idea
is,
since
the
monitor
team
is
already
collecting
a
bunch
of
metrics
on
after
deployment
which
may
be
HTTP
error
rate
or
CPU
usage
or
memory
usage,
and
we
already
have
some
kind
of
way
to
figure
out
that
there's
a
threshold
that
we
don't
want
to
cross
and
what
happens
today
is
there's
an
incident
response
connected
to
it.
So
if
a
threshold
is
met
automatically,
it
generates
an
issue,
and
you
know
the
appropriate
developer
and
what
we
want
to
do
is
take
this
mechanism
and
bring
it
to
the
pipeline.
B
So
if
there
is
a
kind
of
error,
that's
met,
we
want
to
either
roll
back
or
stop
this
appointment,
and
also
this
is
a
lot
of
changes
of
the
deploy
board.
So
it
kind
of
connects
to
it.
So
you
know
if
you're
deploying
something
and
there's
a
bunch
of
errors,
you
probably
want
to
tell
the
deployment
and
not
continue
with
so
so
that's
the
thinking
around
it,
and
we
have
a
lot
of
research
now
to
see
what
metrics
are
interesting
for
people.
Do
we
want?
B
A
C
Was
just
curious
about
the
deployed
boards?
For
some
reason
this
is
actually
not
a
question
really,
but
I
thought.
The
point
word
was
something
more
on
your
face,
but
I
remember
now
that
it
suggests
in
the
the
environments
right
did
you
have
any
discussions
on
it
in
making
that
I
don't
know
expending
the
way
that
users
are
consuming,
that
information
about
the
clusters
and
everything
that
specific
area?
Because
I
remember
we
had
a
conversation
ages
ago,
employment
boards,
so.
B
Yes-
and
this
is
where
it
spins
so
doves
team
in
monitor,
he's
doing
a
bunch
of
work
around
UX
around
the
deploy
boards.
So
I
don't
really
want
to
touch
anything
and
step
on
their
toes,
but
I've
had
a
lot
of
Mercedes
with
him
about
it
and
he
was
like
here
his
might
legends,
don't
touch
it,
don't
move
from
it.
Here's
what
you
need
to
do.
B
A
D
A
B
So
at
the
moment,
like
some
such
funds,
that
I
mentioned
was
secrets.
That
seems
like
an
interesting
points
just
in
how
we
can
connect
the
other
release
stage
with
with
the
deployments
AWS.
That's
something
really
interesting
and
something
that
I
ready
ping
jackie
on
was
that,
for
example,
post-deployment.
B
I
think
we
need
to
add
it
to
the
environment
dashboards.
So
if
there's
an
error
showing
up
in
some
kind
of
environment,
I
think
it
should
show
up
in
the
the
dashboard
itself
and
granted.
I
only
know
this
existence,
because
if
I
started
it
but
I,
don't
know
like
how
that
collaboration
works
with
other
stages.
C
Yeah
yeah
this
with
us
I
think
for
the
environments.
Dashboard
is
a
very
good
point
as
far
as
I
know
we'll
be
focusing
on
improving
the
pagination
living
apartments
dashboards
for
now,
and
then
in
the
other
part,
what
was
it?
My
god?
It's
something
else
where
that
environment,
oh
yeah,
and
it's
showing
the
the
environments
and
the
deployments
from
different
projects,
but
that
they
have
the
same
name
right,
because
right
now
we
only
see
one.
C
C
Have
to
go
crazy,
yeah
for
sure,
especially
with
this
dashboard.
It's
we
know
that
it's
going
to
change
and
we
want
to
update
it
at
some
point
as
we're
getting
a
lot
of
from.
As
far
as
I
know
from
Jackie's
interviews
that
people
are
not
making
real
use
of
that
dashboard
that
we
could
improve
the
way
we
are
displaying
the
data
and
that
we
are
relating
on
this,
this
environment,
oh
for
sure,
MBC
go
for
it.
C
B
C
B
Because
because
family
thing
was
a
Friday,
so
I
am
I
had
Wednesday
was
Independence
Day
here
super
boring
because
it
was
quarantine
like
lockdown,
so
we
had
Independence
Day
and
then
I
had
Thursday
a
totally
froze
day
and
then
I
had
Friday
off
and
Saturday
off.
So
it
was
a
nice
weekend
for
me
soon.
It's
nice
I
have.
A
I
need
some
find
a
way
to
make
sure
that
I
can
log
off
because,
like
yesterday,
I
was
actually
like,
partially
working,
which
is
horrible,
which
I
shouldn't
have
done,
but
and
I
yeah
I,
don't
know,
but
yeah
kind
of,
like
you
don't
feel
like
you
have
anything
else
to
do
in
this
situation.
So,
actually,
today,
I
was
looking
like
okay
I
need
to
find
a
hotel
where
I
could
just
like
even
go
and
give
myself
a
break
close
to
the
sea.
A
B
B
C
B
My
kids
today
first
time
to
the
city
because
I
wanted
to
buy
the
masks
and
they
were
being
very
difficult.
I
was
like
just
you,
go
and
choose
whatever
you
want
and
like
I
bought
them,
slushes
and
I
booked
them,
don't
miss
it.
They
haven't
been
under
house
for
two
months,
so
this
has
been
like.
It
was
such
a
treat
for
their.
B
B
B
D
B
A
A
Yeah
yeah,
so
actually
that's
some
good
news.
Thanks
kind
of
yeah,
okay,
I
actually
probably
even
know
what
is
it
exactly?
Oh,
that's
nice!
Anyway,
let's
go
back
to
the
discussion.
Three
first
question:
you
have
positive,
but
my
initial
question
was
I,
wanted
to
talk
to
you
folks
about
the
drug
stamp
issues
and
like
how
are
you
handling
them
in
your
stage
groups,
and
now
that
we
ever
had
a
discussion
with
an
already
I
was
curious
to
hear,
like
maybe
also
read,
you
can
give
us
perspective
on
the
progressive
delivery
yeah.
C
B
Now
that
Dimitri's
joined
the
there's
more
focus
on
UX
debt
than
there
was
before
I
wouldn't
say
we
have
a
process.
Yet
we
have
a
beginning
of
a
process.
So
the
first
thing
is
that
he
actually
looked
into
it.
So
that's
already
a
good
step
and
we
have
planning
issues.
I
know
that
you
also
have
planning
issues
Ayanna
and
he
for
the
next
milestone.
He
suggested
some
UX
debt
issues
that
we
should
include
in
the
milestone.
B
There's
two
problems
with
what
he
suggested
not
going
into
details,
but
although
items
that
he
suggested
have
not
been
weighted
yet
so
I
think
we
need
to
push
it
by
at
least
one
milestone,
just
because
it
wasn't
in
the
names
weight
issue.
So
you
need
to
make
sure
that
it
gets
waited
before
it
gets
into
a
milestone.
B
And
the
second
thing
is
we're
down
a
front-end
engineer:
cuz
Sara
moved
to
verify
so
there's
only
one
front-end
engineer
and
the
team
and
I
don't
know
how
much
capacity
just
one
person
has
I
know
that
Nicole
said
that
there
that
work.
We
are
backfilling,
but
then
Jackie
told
me
a
rumor
that
we're
not
so
I'm,
not
really
sure
where
that's
standing,
I.
A
See
bollocks,
it's
gray,
I'm
happy
to
hear
that
you're,
also
starting
to
walk
into
that.
Like
also
I,
see
that
some
people,
similar
to
Hannah
and
Jackie,
are
like
saying
we're,
gonna
look
into
one
or
we're
gonna
try
to
commit
to
one.
You
have
step
issue
or
whatever
process
around
that
to
make
sure
that
we
are
constantly
coming
back
I
like
the
fact
I've
seen
the
three
see
you
a
step
function
added
to
the
planning
issue.
So
that's
did
you
want
to
share
something.
D
D
Like
a
pretty
deep,
a
pretty
well-rounded
process
when
it
comes
to
installing
the
runners
for
managing
the
runners
or
he
never
fills
up
we're
currently,
at
least
until
this
point,
it
almost
feels
that
we're
just
catching
up
to
make
that
experience
minimal
just
to
keep
it
in
much
really
were
words,
it's
kind
of
interesting
because
runner
as
a
AUSA.
If
you
want
to
classify
this
category,
it's
very
much
sure
did
the
UX
part
fill
that
it's
always
catching
up.
D
Yeah
and
there's
you
X,
you
know,
there's
like
the
product
there's
already
a
process.
It's
our
runner,
there's
already
a
process
to
manage
runner,
but
it
always
feels
that
there's
a
lot
of
legacy
going
on
there
and
like
many
of
the
issues
that
you
see
right
now,
it's
like
improve
these
change
this
boat
on
make
this
more
clear
even
once.
Our
features
are
just
like
catching
up
to.
D
D
That
might
not
be
technically
correct,
as
you
mean
that,
just
because
it's
catching
up,
it's
you
accept,
but
yeah
in
intestine
is
different,
interesting
I
think
like
we,
we
are
on
in
a
different
situation
where,
like
there's,
actually
UX
that
issues
like,
for
instance,
like
improving
the
M,
are
widgets
that
certainly
you
accept
and
we
look
at
those,
but
but
quite
honestly,
like
I,
should
look
more
of
those
and
I
should
probably
talk
with
James
about
committing
to
fix
one
of
those
per
release.
Possible
I
also
fix
a
lot
of
those
myself.
D
Sometimes
you
know
so.
We,
like
even
forerunner
by
I,
have
to
try
I
have
been
trying
to
fix
like
one
per
release
myself
so
like,
for
instance,
when
you
go
to
settings
right
to
the
settings,
you
know
in
runner
and
there's
usually
like
a
lot
of
poorly
designed
things
there.
So
I
try
to
improve
one
thing
per
release
on
that
and
I
can
do
those
you
know
like
those
are
like
within
the
realm
of
my
technical
abilities,
so
I've
been
doing
that
but
yeah
it's
interesting.
That's
why
I
said
like
I
find
that
question
interesting.
D
You
like
it's
almost
like.
If
you
ask
me,
what's
you
ask
that
for
me
it
goes
beyond
the
label
itself.
I
know.
There's
many
things
are
not
tagged
with
the
label.
There
are
definitely
depth.
You
know
things
that,
like
we're
probably
thought
before
they
didn't
have
a
UX
or
didn't
have
a
so
a
good
product
manager
who
was
thinking
about
the
UX
or
did
he
didn't
have
a
product
manager?
Basically
I
mean,
like
many
of
these
things
were
created
very
early
when
gitlab
was
storing.
D
C
That
said,
that's
the
biggest
difference
like
between
what
we
consider
you
wax
depth,
and
maybe
this
new
wax.
What
do
they
call?
You
X
bug
right
because,
for
example,
UX
that
should
be
something
that
was
generated
by
engineering
depths
or
they
didn't
meet
the
design
guideline.
So
we
decided
to
leave
something
out
of
scope.
I
think
that's
the
biggest
difference
that
something
can
be
a
follow-up
feature
because
yeah
we
need
to
improve
the
workflow
here.
We
need
to
polish
the
UI,
but
that
was
not
part
of
the
scope.
C
I
think
that's
the
that's
the
biggest
difference,
and
it's
awesome
to
hear
it
also
that
you're
tackling
them
on
the
fly,
because
that's
one
of
the
difficulties
right
now
in
my
team,
at
least,
is
that
data
generated
during
the
merge
request
phase
and
because
I
cannot
be
I'm
not
like
super
conscious.
All
the
time
of
the
changes
and
the
micro
changes
that
they
make
in
the
scope
that
influence
the
UX
or
the
UI
I
have
to
keep
following
up
and
seeing
like.
C
Ok
can
I
write
that
yes
or
no
open
an
issue
this
and
that
so
and
I
think
it
makes
a
lot
of
sense.
What
you
say
is
in
you
tackle
things
on
the
fly,
and
you
know
ahead
that
that
is
being
generated,
but
that
is
not
yet.
This
is
not
yet
from
the
engineering
phase
is
just
UX
features
right,
nice
to
have
right,
correct.
D
D
And
you
can
tell
that
it
was
just
like
an
engineer
who
said
like
just
put
a
bar
on
there.
You
know,
like
it's
I
mean
I,
that's
one
of
the
exciting
things
about
working
for
forget,
lab
right,
like
we're
growing
we're
fixing
these
things
as
we
go
like
it's,
not
that
we're
like
100
percent
maturing.
All
this
area
so
like
as
I,
still
find
a
lot
of
those
areas
where
I
see
things
which
is
like
yeah.
C
Then
that
that's
that's
it.
If
that's
the
case,
then
it's
not
you
except
right,
because
there
was
no
UX
standard,
that's
just
a
bug
or
a
cleanup
or
whatever
you
like.
It
is
a
UI
polish.
So
that's
why
I
mean
I
confusing
about
us
about
this,
because
we
keep
creating
on
these
labels
to
identify
yeah,
yeah
and
then
to
me.
I
just
started
writing
this
letter.
The
u.s.
channel
Desiree
some
replies
I
my
opinion,
I
think
it
should
be
bug
and
then
it's
UX
bug.
C
Then
you
have
two
labels,
because
we
keep
having
this
happy
to
align
about
what
things
are
specifically
unless
we
want
to
track
like
what
we
do
for
you,
except
in
this
case,
but
I
think
if
you
can
burn
those
things
on
the
fly
and
identify
that
that
is
being
generated.
You
know
ahead
of
time.
That's
that's
pretty
great
I.
A
D
100
British,
like
almost
100
percent
sure
the
recent
wait
exists
because
there's
tag
dep
and
then
someone
said
like
you
know,
there's
also
UX
that
you
know
someone
said
it
and
then
likely
seed.
You
know,
because
I
have
her
seed
saying
that
a
lot
he
talks
about
you
except
as
well,
so
I
think
it's
just
like
because
it
makes
sense
to
have
symmetry
like
you,
you
don't
only
have
to
check
that.
D
A
Cool
things
around
for
sharing,
I
just
wanted
to
see
if
we
are
giving
a
therefore
your
xbox,
a
good
portion
of
attachment.
This
seems
like
we
are
getting
there
and
so
on.
It
seems
like
testing
well
I'm,
not
talking
about
rather,
but
seems
like
testing
is
not
having
that
included
into
the
planning.
Maybe
this
is
something
for
you
to
suggest
you
James
well,
I,
just
start
looking
into
that,
so
partly
because
I
see
more
and
more
PM's
are
doing
that
today
and
there's.
A
D
A
I
wanted
to
move
this
I
know
we
have
an
issue
open
by
me,
actually
I
about
documenting
the
arise
for
the
product
areas,
and
you
know
that
this
is
the
topic
that
we
have
been
discussing
in
one
of
the
previous
meetings
of
this
time.
I
wanted
to
get
a
bit
of
your
attention
of
advice
here
in
order
for
myself
and
ask
to
move
forward
with
that.
A
So
the
background
on
this
topic
was
that
we
wanted
to
be
to
find
the
ways
to
be
more
aligned
with
the
work
that's
happening
in
other
stage
groups
to
make
sure
that
we
are
not
overriding
each
other
work,
that
we
are
more
aligned
about.
The
decisions
or
solutions
that
we
are
working
on
and
some
of
the
outcomes
that
we
have
talked
about.
A
The
proposal
was
to
start
documenting,
did
your
eyes
for
the
features
and
we
kind
of
like
concluded
it
probably
a
nice
place,
for
that
would
be
in
the
product
stages,
handbook
page
and
thanks
everyone
for
dropping
the
ideas
there
and
basic.
A
couple
of
questions
that
I
have
is
in
the
issue.
We
started
like
putting
a
lot
of
really
detailed
features
and
I
was
thinking.
A
C
Can
we
start
with
the
merge
request,
so
we
have
an
idea
of
like
what
the
initial
step,
because
in
my
head,
it's
like
it
should
be,
for
example,
a
workflow
right,
but
it's
difficult
to
kind
of
give
an
opinion
on
that.
How
that
should
be
documented?
If
it's
not
on
the
page.
So
do
you
think
that
that
that's
a
possibility
so
that
we
work
on
the
fly
yeah.
A
So
your
proposal
is
to
basically
give
it
a
start,
for
them
are
and
add.
Maybe
those
already
feature
there
online
there
we
didn't
assign
I
think
that's
a
good
idea.
Yes,
sure
I
will
do
that.
So
we
listed
the
features,
but
we
didn't
assign
idea
rise
to
them.
Could
you
point
me
to
the
direction?
What's
the
best
way
to
effect
for
me
to
finding
that
theorize
is
contacting
the
closest
people,
I
know,
or
anyone
has
better
idea
how
to
do
that.
C
C
A
C
Today
they
had
a
call
with
chameleon
some
communities
from
secure
stage,
and
she
wanted
to
get
some
help
about.
This
features
is
working
on
is
called
an
on-demand
security
scan.
So
it's
kinda,
like
a
security
pipeline,
that
you
run
specifically
yeah
to
check
you,
security,
to
check
the
test
and
everything
and
she
had
a
lot
of
questions
about
pipelines
and
how
they
work.
C
She
schedule
call
with
me
today
and
then
we
were
just
just
chatting
about
it
because
she
wanted
like
some
perspective
and
to
understand
the
the
environments.
Sorry,
the
pipeline's
view
and
know
how
do
how
do
our
personas,
like
in
release
management
they
consume
that
information
I
mentioned
to
her
that
it's
yeah
it's
going
to
be
very
different,
but
a
lot
of
her
prototypes.
C
They
are
it's
the
pipeline
view,
but
in
a
different
section
of
gate
lab,
and
my
initial
idea
was
that
it
should
be
that
different
right
if
you're,
creating
a
new
type
of
pipeline,
just
add
that
in
the
pipeline
list
and
show
it
with
a
different
label.
For
example,
we
have
detach
pipelines,
we
have
a
bunch
of
things
in
the
UI
that
you
can
identify,
but
she
has
more
questions
related
to
the
CI
aspect
of
in
the
workflow.
Like
do
people
go
to
the
text
to
the
tabs
Security
tab?
Do
you
know
how?
C
A
Thanks
for
the
reason
why
I
was
asking
is
I'm
curious
like
how
do
we
reach
out
to
each
other
around
this
cross
stage?
Topics
yeah
I
would
also
encourage
camellia
just
to
like
put
it
there
in
the
UX
lag,
so
others
also
like.
So
we
do
more
or
more
of
this
cross-functional
aged
questions
in
slack,
but
yeah.
That's
94.
Thanks
for
the
heads
up
on.
A
D
I
mean,
like
your
questions,
are
yeah
I
mean
I,
don't
think
I
have
an
answer
for
the
first
one.
I
too
have
an
answer
for
the
second
one
which
I
can
assure
here
for
everyone,
which
is
why
people
go
to
the
pipeline
tation,
usually
because
they
are
ABCD
the
pipeline
or
they
are
like
troubleshooting
the
pipeline
or
the
one
understand
very
specific
things
about
the
pipeline,
structurally
speaking.
Otherwise,
there's
no
reason
to
go
to
that
page
because
you
can
accomplish
already
everything
from
the
EMR.
D
Even
if
I
go
into
the
jobs,
you
can
do
that
from
them
are,
but
I
think
she
raises
a
good
point,
which
is
many.
Functionality
is
hidden
on
the
pipeline
page,
so
I
don't
think
we
have
strong
affordances
or
reasons
to
take
people
to
the
pipeline
page.
It
happens.
Testing
as
well.
Testing
has
a
tab
there.
It
actually
has
two
tabs
there
and
I.
Don't
think
people
find
I
mean
right
now.
What
we're
trying
to
do
is
make
that
easier
for
them
to
go
from
the
mr
widgets
to
those
tops.
D
C
Exactly
like
a
similar
case
for
us
that
people
would
go
to
the
pipeline
unless
there's
a
detail
view
unless
there's
something
wrong
with
a
pipeline
right
and
they
need
to
debug
that
and
see
or
they
go
to
the
pipeline's.
Looking
for
the
deployments,
something
like
that,
but
her
case,
it's
so
specific
that,
yes,
from
what
she
explained
to
me,
is
that
the
user,
the
persona
every
quarter,
it's
gonna,
run
a
security
pipeline
or
every
milestone.
So
it's
really
like
an
ad
hoc
thing.
What.
C
But
it's,
but
but
there's
no
information
on
a
CI
file.
It's
really
like
from
a
form
everything
happens
in
the
UI
and
you
select
the
this
is
the
target,
but
I
want
to
run
in
I,
wanted
to
be
deployed
to
this
environment.
I
wanted
to
schedule
on
this
date
and
I
wanted
to
run
these
security
jobs
whatever.
D
C
D
D
D
D
C
A
D
I
will
say
that
they
are
potentially
even
three,
but
let's
keep
it
up,
which
is
more
reasonable
and
I
was
curious
because
I
just
sorry
I
had
my
first
call
and
the
customer.
He
basically
got
it
super
easily
to
one
of
our
user
flows.
He
didn't
get
I
encouraged
him
to
try
like
a
different
way
to
accomplish
like
to
I
I
told
him
like
hey
perfect,
you
did
it.
That's
perfect.
Now,
I
have
a
question
for
you.
D
If
you
had
to
do
it
in
a
different
way,
not
to
that
particular
affordance,
how
will
you
do
it
and
then
he
tried
and
he
failed
not
miserably.
He
actually
was
pretty
close
to
get
it,
but
he
for
some
visibility
reason
he
couldn't
see
like
the
Balkan
in
then
like
finalizes,
that
the
workflow
yeah,
so
I
was
curious
about
that.
C
Well
sure,
for
example,
when
you
release
management
when
creating
a
release,
you
have
one
job
to
be
done
right.
I
want
to
create
my
release.
You
can
do
that
through
the
UI
right
internet
or
the
CLI,
so
this
is
what
we're
calling
the
different
scenarios
and
then
I
hope
that
makes
sense,
because
it's
a
trying
to
process
to
process.
The
question
is
that
we're
really
looking
to
what
are
the
low-hanging
fruits
and
which
one
of
the
those
scenarios
we
want
to
tackle.
C
First,
that
would
help
us
reach
the
next
maturity
level
or
that
will
help
reach
more
value
for
port
functionality.
So,
for
example,
when
we
talk
about
creating
a
release
through
the
API
and
managing
the
release,
there
is
so
much.
Oh,
my
god
right
now,
that's
the
UI.
It's
really
the
focus
so
I
think
that
will
always
be
different.
Specially
with
this
technique
or
non-technical,
personas
you're
always
going
to
have
different
ways
to
accomplish
the
same
task.
So
one
job
to
be
done,
and
then
you
break
that
down
for
a
persona,
because
right.
A
A
Into
that
and
I
think
that
some
of
the
okay-
maybe
there
is
even
more
ways
to
accomplish
the
work
that
we
have
known,
an
idea
about
I,
feel
like
users
can
be
something
so
creative,
and
this
is
what
I
said
to
do.
I
think
I
think
with
Laurie
here,
but
I
think
if
we,
if
a
user
was
able
to
achieve
his
goal
in
one
of
the
ways
that
we
can
count,
that
already
was
a
good
sign.
Of
course
it
yeah
we
may
walk
into
it
while
the
others
failed,
but
I
guess
it's.
C
C
Yeah,
you
know
it
feels
like
a
fail
right
like
we're,
delivering
half
the
toughness
value
for
the
functionality.
I
think
it
really
depends
on
which
person
might
want
to
focus
for
us
yeah.
We
want
the
persona
that
it's
non-technical
that
needs
the
UI
to
succeed
in
their
jobs.
That's
why,
in
this
case,
this
multiple
scenarios,
a
job
to
be
done.
Yeah
generally
shouldn't
fail
on
any
scenario
right.
It
should
be
able
to
accomplish
in
job,
but
it's
a
little
bit
tricky,
whereas
Laurie.
A
A
A
All
right:
well,
we
are
at
the
end
of
the
time
almost
but
yeah
I
don't
know
if
anyone
has
anything
interesting
to
share
to
paste
here,
at
least
or
just
do
a
little
quick
shout
out
in
the
guards
look
to
the
books,
tutorials
conferences
and
stuff
actually,
actually,
last
week,
I
attended
my
first
ever
five-day
remote
conference
for
the
design
of
around
the
design,
and
that
was
actually
such
a
cool
experience
and
I've
wasted.
One
of
them
talks
that
really
inspired
me
into
the
feet.
A
Machado
and
let
me
just
copy
the
URL
they've,
been
kind
of
talking
about
different
ways:
creative
ways
of
using
figma
for
retrospectives,
for
everything
like
that,
all
the
unimaginable
ways
to
use
feet-
man
I
think
actually
is
sometimes
it's
a
nice
replacement,
even
for
MU
for
neuro
boards
of
we
are
using
and
other
talks.
It's
pretty
cool.
One
was
also
pretty
fun
talk,
so
I'll
just
drop
it
here
didn't
feed.
My
channel
looks.