►
From YouTube: 2021-02-01 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).
B
A
You
could
see
that
it
only
takes
10
seconds
of
courage.
A
C
Awesome
so
we
don't
have
myra
at
the
moment,
so
she'll
be
around
later
on.
C
Oh
and
thanks
alessio
for
adding
the
redacting
tool,
it's
like
a
nice
new
additional
stuff.
It
does
actually
work.
So
I
tested
out
expenses
last
month,
redacted
all
my
information,
which
I
don't
know
how
they're
approving
things,
but
it
happened
and
money
came
through
so
go
ahead
if
you
want
to,
if
you
want
to
do
that
cool,
so
I
wanted
to
talk
to
you
a
little
bit
about
the
department
strategy
so
I'll.
C
Let
you
all
like
read
the
actual
strategy
and
the
team
strategy
yourselves,
and
if
you
want
to
improve
things,
then
please
go
ahead
and
put
mrs
in,
but
I
wanted
to
just
tell
you
a
little
bit
about
why
this
stuff
has
happened
and
it's
been
in
progress
for
a
few
months,
and
so
we
have
a
company
strategy
and
it
was
updated
sort
of
towards
the
end
of
last
year,
and
so
this,
what
this
is
designed
to
do
is
to
link
what
you're
individually
working
on
right
through
up
to
their
company
strategy.
C
So
the
way
we
do
that
is
we
cascade
the
company
strategy
down
into
a
department
strategy
and
then
from
that
link
to
the
delivery
team
strategy.
So
within
infrastructure,
each
of
our
five
teams,
we
all
collectively
contribute
to
the
department
strategy.
If
we
all
like
achieve
everything
we
set
out
to
do,
then
the
department
strategy
will
be
achieved
and
if
every
department
achieves
their
whole
strategy,
then
the
company
strategy
is
achieved.
C
What
it
should
hopefully
do
so
not
only
will
it
hopefully
help
link,
maybe
some
smaller
tasks
that
we
do
day-to-day
to
like
the
overall
company
goals,
but
it
should
help
us
our
prioritizations.
I
think
a
complete
like
a
consistent
challenge.
We
have
is
on
the
number
of
things
that
we
want
to
be
working
on,
and
how
do
we
prioritize
those?
We
see
it
like
when
we're
picking
up
okrs,
but
we
also
see
it
like
day
to
day
with
all
the
kind
of
little
things
that
come
in
or
the
requests
that
people
make
of
us.
C
So
the
goal
of
having
a
team
strategy
is
basically
to
help
you,
when
you're
trying
to
prioritize
your
time
to
actually
know
like,
what's
going
to
be
the
most
valuable
thing
to
focus
on
and
that's
going
to
be
anything
linked
to
team
strategy.
Basically,
are
there
any
questions
about
strategies
or
for
what
you've
read
of
this
one
so
far
like
it
doesn't
like?
Also
like
I'm,
not
assuming
I'm
assuming
everyone
might
not
have
read
it.
So
don't
feel
bad
if
you
haven't
read
the
actual
strategy,
but
does
anyone
have
any
questions
about
strategies.
C
Awesome,
let's
say:
go
ahead
and
like
read
them
through
and
like,
if
you
want
to
talk
about
one
to
ones
or
we
can
follow
up
in
a
future
meeting,
that's
also
completely
cool.
This
will
get
increasingly
useful
as
we
go
through
and
get
more
comfortable
with
our
kind
of
okr
selection
process.
So
this
time
around
in
q1
the
categories
we
were
ranking,
the
okrs
around
were
roughly
linked
to
the
strategy
and
in
as
we
go
into
q2
they'll
be
absolutely
linked.
C
So
it
should
help
us
to
really
be
able
to
like
easily
prioritize
but
where's
the
best
case
to
spend
our
time
awesome
and
then
number
two
is
maybe
quite
updated,
but
I
put
it
in
discussions
just
in
case
people
have
comments
and
things
they
want
to
talk
about.
So
I've
put
in
a
weekly,
rollbacks
demo
call
starting
from
tomorrow.
C
The
idea
behind
this
is
to
try
and
replicate
what
we've
been
doing
with
the
kubernetes
demos,
where
basically,
the
primary
goal
of
it
is
to
share
what
we've
done
to
like
properly
demo.
What
we've,
what
we've
been
working
on,
have
a
discussion
about
that
like
if
we've
got
a
like
a
technical
thing,
we
want
to
unblock
or
we're
not
sure
what
the
approach
is
then
perfect
place
right.
C
So
it's
not
intended
to
be
an
update,
meeting
or
really
even
a
kind
of
work,
prioritization
meeting
it
should
be
about
like
how
do
we
want
to
progress
on
this
stuff?
C
So
it
might
be
a
little
bit
early
tomorrow
in
terms
of
like
it's
day,
two
of
this
quarter,
but
I
thought
I'd
just
put
it
in
anyway
and
we
can
either
use
it
to
talk
about
how
we
want
to
set
the
okr
up,
or
maybe
the
things
from
the
coordinate
deployments.
C
Work
that'd
be
worth
demoing
and
discussing
and
using
that
to
sort
of
feed
into
the
rollback.
So
it
will
become.
I'm
sure,
it'll
take
us
a
few
weeks
to
get
into
a
rhythm
of
it.
But
if
you
have
things
already,
you
can
think
of
you'd
like
to
either
demo
or
see
in
action
or
discuss.
Then
please
just
go
ahead
and
stick
those
on
the
agenda.
C
I've
put
you
all
as
optional,
so
you
know
choose
your
time
like
use
it
as
you
want,
but
hopefully
it'll
be
become
the
place
where,
like
you
know,
if
we
want
to
just
quickly
make
like
unblock
things
or
discuss
approaches
for
rollbacks
or
anything
like
that,
then
this
would
be
the
place
to
go
cool.
Any
comments
on
rollbacks
and
meetings.
C
D
C
A
I
know
the
the
got
wants
to
do
a
maintenance.
I
can't
recall
what
all
time
this
stuff
is,
but
it's.
C
D
A
C
Nice
awesome
sounds
good
eric
over
to
you.
B
Yeah
thanks
yeah.
This
was
just
a
question
like
I
was
originally
going
to
use
release
tools
for
the
changelog
testing
like
first
I'd.
Do
it
manually
myself
and
then
I
would
ask
you,
know
everybody
in
delivery,
like
hey
when
you
submit
merge,
requests
to
add
this
little
tag
to
your
commit
messages,
but
then
I
found
out
that
the
last
changes
we
made
over
these
tools
were
about
a
week
ago
and
there
aren't
really
any
open,
merge
requests
that
are
actively
worked
on.
B
So
I
suspect
the
volume
of
changes
is
going
to
be
so
low
that
it's
not
going
to
be
terribly
helpful
as
I'm
kind
of
curious.
If
anybody
has
any
suggestions
of
fairly
small
and
isolated
projects
with
frequent
enough
changes,
but
not
enough
developers
that
introducing
this
testing
period
significantly
complicates
or
frustrates
the
process,
because
probably
first
sort
of
big
satellite
project
I
want
to
test
on
is
giddly
because
it
is
fairly
self-contained.
It
has
quite
some
developers,
but
I
think
that's
a
bit
too
early
now
alessio
suggests
gitlab.
D
B
Let's
see
quickly
looking
at
the
commits
yeah,
it
seems
active
enough,
although
yeah
it
seems
there's
like
a
bunch
of
merch
requests
that
are
a
few
weeks
old.
So
oh
I'll,
take
a
look
at
it
see
if
we
can
maybe
do
there
and
otherwise.
If,
if
there's
no
small-scale
projects,
I
guess
it's
manual
testing
and
then
we
pick
gilly.
For
example,
oh.
C
B
Yes,
so
my
plan
is
to
do
that
just
completely
on
a
separate
branch
and
just
commit
some
nonsense.
Data
to
the
the
branch
generate
the
change
lock
there
review.
If
it's
you
know
sensible,
and
then
we
wipe
the
branch.
Basically,
when
we're
done.