►
From YouTube: 2022-05-30 Delivery team weekly EMEA/AMER
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
Okay,
welcome
everyone,
so
we
have
a
few
announcements
time
out,
I'm
going
to
just
say
a
little
thing
about
mine,
so
I'm
out
from
this
wednesday
through
to
the
following
tuesday.
So
if
you
need
anything,
please
drop
me
a
note
today
or
tomorrow
and
I'll
do
my
best
to
help
out.
B
What
should
we
do
with
the
expenses
amy?
Should
we
send
it
to
you
today.
A
If
you
can
do,
that
would
be
great
yeah.
If
you
know
you're
gonna
miss
the
date,
then
just
let
me
know
I'm
I
am
around,
so
I
can
always
just
pop
on
later
this
week.
If
I
know
I
need
to
and
click
a
button,
that's
no
trouble.
So
if
you,
if
you
know
you
have
some-
and
you
might
miss
me
just
let
me
know
thanks.
A
Cool
so
mckelly
you
have
this
first
starting.
C
Yes,
so
to
with
a
session
last
wednesday,
with
the
delivery
system
team,
it
was
a
session
that
we,
we
usually
only
took
one
hour.
It
was
time
boxed.
We
had
a
set
agenda
with
several
activities.
We
used
a
a
co-creative
approach
with
a
white
board
and
the
goal
of
this
session
was
to
come
up
with
ideal
target
state
kind
of
topical
that
we
won't
like
to
aim
to
for
the
delivery
system.
C
Where
you
know,
we
would
like
to
innovate
or
try
to
say
something:
okay,
what
we,
how
cool,
would
it
be
if
we
could
be
able
to
do
to
a
delivery
system
that
is
able
to
do
that,
so
the
outcome
of
that
and
then,
where
a
lot
of
like
maybe
current
issues
that
we
were
facing
in
the
current
setup,
there
were
also
some
new
things
that
they
were
discussed
and
it
was
actually
pretty
pretty
interesting
also
to
see
how
the
all
the
several
items
scenarios
were
connected
to
each
other.
C
So
this
is
going
to
be
the
base
for
next
steps
to
operate
more
to
work
more
in
the
in
that
direction.
Iterate
a
bit
more
on
that
and
try
to
see
if
we
can
be
even
a
bit
more
visionary.
What
we
want
to
have
in
the
future
as
a
delivery
system,
try
and
try
to
remove.
C
C
Do
you
have
a
question
so
I'm
happy
to
take
them
and
everything
there's
also
our
recording.
So
if
any
one
of
you
is
interested
to
see
that
I
can
share
it
with
you,
and
it's
also
the
motherboard
that
we
use
for
the
forever
installment
is
also
available,
because
you're
also
interested
in
that.
A
Oh
thanks
for
sharing
that
a
couple
of
kind
of
things
around
this,
so
I
we
we
will
do
something
similar
in
orchestration.
That
will
be
in
a
few
weeks
time,
which
is
related
to
a
point
I
have
further
down,
but
we
haven't
forgotten
about
there
being
two
teams.
So
if,
if
you
haven't
yet
been
involved
in
one
of
these,
then
there
will
be
more
of
these
coming
and
I
might
actually
share.
This
is
super
early
stage.
A
So
the
other
piece
that
michelle
and
I
have
been
working
on
between
the
kind
of
the
long
term
stuff
is
the
also
the
today.
So
what
we
have
is.
A
A
spreadsheet-
and
you
may
recognize
some
of
this
stuff-
we're
still
working
on
this,
but
it
this
gives
you
our
current
thinking
of
all
of
the
open
delivery
issues
and
where
they
might
fit.
So
there's
lots
of
room
to
shift
this
around.
We've
got
another
iteration
that
we're
planning
to
try
and
help
make
this
more
useful.
A
But
just
so
you
kind
of
can
see
some
of
the
the
things
that
we're
already
going
through
to
try
and
help
us
work
out
like
what
does
the
the
next
six
months
or
two
years
start
to
look
like.
A
Yes,
so
we
probably
won't
attempt
to
do
all
of
them.
One
of
I
think
one
of
the
the
tricky
things
we'll
actually
be
figuring
out.
What's
the
stuff
which
we
just
just
park
like.
Maybe
there
are
some
themes
we
just
literally
just
close
out
and
say
this
isn't
the
thing.
Hopefully,
some
of
our
longer-term
thinking
will
remove
the
need,
so
some
of
this
will
be
like.
A
Awesome
thanks
for
sharing
kelly.
If
anyone
has
any
thoughts
on
that,
then
obviously
like
we
can
keep
chatting
about
these
things
and
slack,
and
these
meetings
and
there's
no
perfect
divide
between
you
know
turning
one
team
into
two:
there
will
be
some
messy
bits.
There
will
be
some
stuff.
We
still
need
to
be
figuring
out,
so
you
know
like
feel
free
to
keep
asking
questions
and
commenting
and
stuff
as
we
try
and
work
this
out.
B
Okay,
thank
you
emmy.
So
I
took
some
time
to
put
some
screenshot
here,
but
I
would
like
to
experiment
something
new
today,
which
is
I'm
gonna
share
my
screen
and
walk
you
all
through
this
three
graphs
here
and
showing
what
I
see
when
I
look
at
those
numbers
and
what
I'm
currently
looking
at
well
in
terms
of
deployment,
because
maybe
this
is
interesting.
B
So,
oh
here
we
go.
That's
my
screen.
Let
me
start
with
this
one,
which
is
my
favorite
new
dashboard.
So
this
is
I'm
focusing
on
the
on
the
upper
side
here.
So
we
have
in
green
how
many
packages
we
are
tagging
in
the
past
24
hours
of
a
given
point
and
the
yellow
line
is
packages
not
promoted
to
production.
B
So
what
we
want
to
have
here
is
something
like
this,
so
there
was
a
point
in
time
midweek
when
we
were
doing
great
every
single
package,
we
tagged
ended
up
in
production.
What
we
don't
want
to
have
a
situation
like
this
one,
where
we
tagged
10
packages
and
out
of
10
8
were
not
promoted
right.
So
what
this?
Inter?
What
struck
my
attention
here
was
basically
at
this
point
here
in
time
we
changed
tagging
frequency.
B
B
So
almost
eight
you
to
see
we
were
not
promoting
anything
so
which
means
that
by
the
time
I
was
able
to
start
promoting
something
we
already
wasted
many
packages,
and
so
basically,
what
we
ended
up,
removing
are
packages
being
tagged
around
this
point
in
time
every
day
this
was
specifically
true
for
monday,
because
monday,
we
also
have
pro
soft
change
locks
in
time.
So
grams
cannot
promote
stuff
in
his
evening
because
he's
still
affected
by
the
change.
The
soft
change
lock
that
we
have
over
the
weekend.
B
So
basically
the
emea
release
manager
is
the
only
one
allowed
to
start
promoting
something
on
monday
mornings.
So
all
those
things
together
are
show
up
here
and
what
we
see
also
here
is
the
family
and
friends
day
and
the
effect
of
not
blocking
out
the
deployment
because
of
we
had
an
incident
over
friday,
so
we
were
doing
great
and
all
of
a
sudden,
we
started
ramping
up
of
things,
getting
tagged
and
not
promoted,
because
no
one
was
around
to
actually
promote
them.
B
I
think,
except
the
only
one
that
was
the
fix,
and
then
we
see
things
ramping
down
because
of
the
we
are
no
longer
talking
because
we
entered
the
weekend
and
this
show
up
as
well
this
morning
this
morning
we
had
a
problem,
so
the
problem
is
that
we
had
still
something
coming
on
from
the
from
the
incident
as
well
as
we
had
another
problem
with
the
the
deployer
pipeline,
not
not
the
player.
The
release
does
not
be
able
to
trigger
a
pipeline.
B
That's
the
authorization
problem
that
we
have
so
basically,
we
we
were
not
able
to
promote
packages
because
the
production
canary
trigger
was
not
allowed
because
of
that
park,
and
we
basically
see
this
because
up
until
this
point,
we
were
still
not
tagged.
We
are
still
not
able
to
promote
packages,
and
so
I
managed
to
do
two
deployments
which
we
can
see
here
when
this
thing
goes
down
then
goes
up
again
because
a
new
auto
deploy
branch
comes
in
and
then
30
minutes
ago
kind
of
I
promoted
again,
and
then
we
see
the
number
going
down.
B
So
I
I
like
this
graph
because
kind
of
kind
of
gives
the
idea
of
how
things
are
going
for
release
managers.
I
will
take
a
look
at
this
closer
look
at
this
in
the
next
time,
and
then
this
one
I
decided
not
to
look
at
sisense,
because
I
prefer
to
give
a
look
at
the
what
we
have
in
the
product.
Now
that
is
tracking
the
right
information.
B
So
this
these
are
just
deployment
frequency
as
we
can
see.
This
is
last
month
right.
So
we
pick
it
during
this
is
this
was
still
yes,
this
was
still
15..
Oh,
we
had
some
good
moment
in
time.
We
were
doing
seven
deployment
a
days,
but
then
basically
we
can
see
here
that
we-
this
was
no
longer
the
case
in
in
the
past
two
weeks.
This
gives
an
idea
of
how
much
we
are
deploying,
but
it's
not
really
that
informative.
B
I
prefer
this
one,
because
this
one
is
the
closer
thing
to
mttp
that
we
have
in
the
product
and
this
kind
of
show
us.
I
mean
this
aligns
with
the
other
things
we
were
seeing
in
this
graph
here
right
when
we
struggle
at
the
beginning
of
the
week,
and
then
it
goes
better.
So
let
me
try
to
do
and
then
I
promise
that
I
will
stop
the
last
30
days.
So
we
see
the
same
time
span.
B
Yeah
beginning
is
hard
midweek
we're
doing
great
and
then
when,
at
the
end
of
the
week
we
start
struggling
again.
We
see
this
pattern
and
this
no.
This
is
not
not
this
as
well
here
and
this
pattern
as
well.
We
can
see
here
right
because,
obviously,
in
the
monday
we
have
mttp,
which
is
very
long
because
we
are
accumulating
things
over
the
weekend.
B
I
hope
this
is
just
people
working
apac
shift
and
u.s
shift
in
on
friday
and
not
many
people
working
over
the
weekend,
but
everything
could
happen
and
then
we
mid
week
we
kind
of
go
a
couple
of
times
here
is
better
below
the
medium
threshold,
which
is
12
hours,
which
really
aligns
with
our
mttp
targets,
and
so
basically
this
this
is
the
yeah
the
window.
This
this
popover
is
really
annoying.
So
the
thing
is
that
at
the
beginning
is
bad:
we
gradually
go
better
midweek.
A
One
thing
on
that:
one
before
yeah,
what's
interesting
to
see,
there
is
look
at
may
27th,
so
look
how
low
the
the
spike
is,
this
one
yeah,
so
so
what
I
think
what
that
does
tell
us
is
on
the
really
high
peaks
it's
the
they're,
probably
things
being
merged
sort
of
late
in
the
day
for
the
americas,
because
on
the
27th
we
didn't
have
that
because
most
people
were
on
family
and
friends.
So
that's
quite
interesting.
B
Yeah
so
yeah.
My
my
idea
here
is
that
this
do
push
all
of
you
to
try
to
look
at
data
and
try
to
figure
out
what
those
data
are
telling
us
or
if
we
are
missing
some
information.
I
oh
jesus.
I
I
okay,
I
did
something
I
enabled
the
recognition
of
gesture
and
so
my
mind,
soon
kind
of
lowered
my
rise
in
my
head.
That's
it
okay
and
that's
all
from
me.
A
A
I
wonder
I
do
wonder
whether,
rather
than
not
promoted
it
might
be
easy,
more
useful
to
show
promoted
and
where
the
lines
match
up.
We
know
we
have
we're
tagging
and
promoting
consistently
the
reason
I
kind
of
say
that
is,
we
often
have
other
uses
for
how
many
deployments
did
we
make
how
many
things
got
promoted,
so
it
might
be,
might
be
interesting
to
just
be
able
to
see
them
one
on
top
of
the
other.
B
It's
this
graph
below,
so
this
one
is
promotion
by
environment
and
with
yeah,
there's
no
tagging
here,
but
we
hope
that
unless
we
get
into
staging
canary
otherwise
it's
just
a
wasted
package.
So
if
the
the
number
doesn't
match
with
the
tagging
means
that
we
had
a
tagging
problem,
a
packaging
problem-
but
here
that's
basically
here
below,
is
exactly
the
same
graph.
B
I
just
find
this
harder
to
see
because
of
the
amount
of
environment
we
have,
and
so
this
kind
of
this
gives
me
the
the
gap
right.
So
I
want
to
to
have
the
the
gap
as
to
as
wide
as
possible,
which
means
I'm
not
wasting
packages,
but
we
have
both
information
available.
So
it's
just
a
matter
of
preferences
of
what
do
we
want
to
look
at.