►
From YouTube: 2021-08-23 Delivery team weekly
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
B
B
C
This
is
like
regular
working
office
working.
D
C
It's
pretty
awesome
awesome,
so
let
us
start
so
henry.
Would
you
like
to
give
us
an
overview
of
mttp.
A
Oh
wow,
I
didn't
prepare
for
that.
I
totally
forgot
that
we
should
do
this
as
always:
managers,
I'm
sorry,
but,
as
you
can
see,
I
think
we
have
done
pretty
well
in
the
last
days,
so
we
managed
to
stay.
A
I
think
you
can
see
it
really
good
here,
but
I
think
we
moved
below
the
target
for
most
of
the
time
and
yeah
need
to
look
into
the
details.
Sorry.
C
Okay,
the
next
time,
then,
because
what
would
be
great
to
know
is,
if
do
we
need
to
do
anything
differently
like
do
you
need
any
help
or
do
we
need
to
work
on
tooling
or
anything
like
that?
So
that's
a
really
useful
thing
to
check
in
but
good
to
see
the
mttp
is
a
bit
lower.
The
number
is
on
18.9
at
the
moment,
so
that's
not
looking
too
bad,
which
is
good
awesome.
So
I
added
some
read-only
announcements.
C
Robert
isn't
on
the
call,
but
has
anyone
talked
with
robert?
Like
do?
We
have
release
management
coverage
for
those
days
that
robert's
off.
C
No
okay
I'll
follow
up
robert
there,
oh
so
on
two
discussion
items
number
3a
is
is
semi
less
of
a
discussion,
but
I
put
it
here
just
in
case
people
had
questions
which
is
there's
here's
the
daily
stand-up
agenda.
I
recommend
keeping
in
touch
with
this.
The
meeting
is
every
day
at
3
utc.
C
So
now,
at
the
moment,
none
of
these
items
are
affecting
our
priorities
and
our
works,
but
they
are
rapidly
changing
and
they
are.
You
will
see
a
lot
of
the
impact
of
this
stuff
around
our
work.
So,
for
example,
scalability
are
doing
work
on
things
like
for
this.
Reliability
will
likely
be
picking
up
various
things
as
a
result.
This
is
where
a
new
staging
environment
has
come
from,
for
example,
but
also
lots
of
shifts
and
changes
on
the
development
side.
C
So
it's
a
good
one
just
to
keep
in
touch
with
for,
for
a
general
context
of
lots
of
things
going
on
right
now,
then
b,
so
I'm
heading
out
on
pto
later
this
week
towards
the
end
of
this
week.
So
the
the
main
thing
is
going
to
be
like
work
items
like
not
just
next
week
but
like
forever.
Like
you
know,
what
do
we
work
on
this
quarter?
C
I
think
will
be
more
important
than
maybe
any
that
we've
had
before
in
terms
of
the
board,
because
what
we're
seeing
is
we
have
lots
of
epics
in
progress
and
they
have
dependencies
to
some
degrees.
So,
for
example,
like
myrrh,
you
highlighted
like
single
pipeline
like
there's
lots
of
stuff,
we
can
do
there,
there's
a
good
subset
of
stuff.
We
can
do
there.
There's
also
some
of
those
pieces
actually
create
like
a
bit
of
a
blocker
for
the
new
staging.
C
The
qa
triggers
right,
so
there's
lots
of
pieces
there
that
suddenly
the
staging
work
will
affect
and
then
similarly
we're
going
to
have
some
of
those
single
pipeline
things
that
we
want
to
get
migrated
as
we
go
through
rollbacks.
C
So
in
order
to
so
those
are
just
some
examples
are
also
going
to
be
sort
of
like
the
random
tasks
that
come
in
there
may
be
random
staging
tasks.
There
are
always
a
few
random,
so
dris.
The
main
request
for
you
is
to
have
a
think
about
whether
there
is
anything
else.
I
know
you
all
have
your
own
epic
boards,
which
is
great.
C
That's
your
main
focus
is
to
make
sure
your
board
has
your
items
and
those
are
kind
of
the
top
things,
and
then
they
can
migrate
onto
this
workboard
and
we
can
anyone
looking
for
a
task.
Let's
pull
from
this
board.
C
So
I
have
I
shared
this
today,
I'll
go
through
it
all
with
you
like,
as
we
go
through
one
to
ones
like
if
I
or
I
ping
you.
If
I
see
things
that
we
need
to
modify
on
here,
I
actually
think
there's
quite
a
lot
of
work
on
this
board
already,
because
some
of
these
tasks
are
quite
big
but
we'll
try
and
like
over
inflate
it
a
little
bit
for
the
next
few
weeks,
so
that
there's
plenty
of
things
to
pick
for.
D
C
All
right,
yeah,
no,
that's
totally
fine
to
go
back.
I
was
gonna.
Actually
add
it
like.
Let's
chat
one
to
one
about
how
you
want
to
pull
that
stuff
in
so
we
can
get
those
things
on
here.
I
think
like
for
today
you
know
like
henry's
kind
of
busy
on
registry.
I'm
sure
graham's
got
plenty
of
web
stuff,
so
it's
totally
fine
for
today,
but
yeah.
That
was
one
thing
that
we
should
catch
up
on
this
week.
C
Awesome
if
you
have
any
expenses
reports
that
need
to
be
approved
before
the
6th
of
september.
I
think
some
of
you
may
please
could
you
submit
them
before
I
head
out
on
wednesday
and
I'll
approve
those
two.
If
you
come,
if
you
miss
that
and
you
need
something
marion
is
around
from
next
wednesday,
so
the
first
of
september
he's
back.
C
So
I
think
you
can
also
skip
past
me
if,
if
there's
absolutely
an
emergency
and
is
there
anything
else,
I
should
be
making
sure
I
have
in
place
or
covered
off
or
done
before.
I
go
away.
C
Okay,
if
you
think
of
anything,
please
just
give
me
a
shout
either
we
can
talk
one
to
one
or
ping
me,
so
we
can
get
things
covered
for
the
first
two
days,
both
marin
and
I
are
out
in
those
days
if
you
get
like
totally
stuck
and
steve's,
not
able
to
help,
you
can
ping
me
directly
like
on
slack,
you
might
get
lucky.
I
may
see
the
notification
if
I
don't
you've
got
my
mobile
number
on
my
slack
profile,
so
you
can
also
use
that
awesome
scalbeck
over
to
you.
D
I
plan
on
beginning
the
web
migration
during
my
work
hours
today.
I'm
going
to
wait
till
the
current
deployment
completes
for
any
future
deployment
for
the
rest
of
today
and
during
the
time
in
which
grain
will
pick
up
this
work,
because
it's
going
to
bleed
over
to
us
time.
Just
let
both
of
us
know
that
a
promotion
is
going
to
happen
such
that
we're
not
proceeding
forward
with
our
change
requests.
At
the
same
time,
deploy
is
going
out.
D
A
Notification
adding
to
that
there's
this
change
request
from
nails
right,
but
she
also.
D
A
To
execute-
and
I
think
it
makes
sense
if
he
starts
first,
because
his
one
is
much
shorter
than
yours,
so
we
should
let
him
go
first,
wait
with
deployments
anyway
until
he's
finished,
because
the
next
canary
is
nearly
ready
to
be
deployed.
I
guess-
and
we
shouldn't
do
that
right
now,
so
you
can
do
the
stuff
after
the
current
deployment
is
done.