►
From YouTube: Configure FY24 investment plans
A
A
All
your
feedback
is
welcome
in
this
merge
request
that
I'm
sharing
with
you
here
or
even
outside,
of
the
merge
request.
If
you
prefer
that
my
first,
what
is
this
all
investment
plan
thing
about
in
products?
We
typically
do
an
optional
exercise
close
to
the
beginning
of
the
start
of
the
financial
year.
That
is,
we.
A
The
product
managers,
come
up
with
a
plan
for
the
following
year,
given
our
current
investments
in
our
stage
in
our
Direction,
and
we
make
two
marines
of
this
based
on
what
would
happen
if
we
would
get
a
plus
10
percent
investment
or
a
minus
10
percent
decrease
in
investment.
Why
we
do
this?
We
do
this
for
many
many
reasons.
One
is
to
have
a
discussion
with
you,
the
team
itself,
then
to
have
a
discussion
with
product
leadership
so
that
they
we
can
signal
to
them.
A
What
to
expect
from
us
in
all
these
cases
and
to
especially
show
the
emerging
effects
of
an
investment
in
our
stages,
so
what
I
did
I
opened?
This
merge
request
here
and
if
you
scroll
down
in
the
Mr,
you
can
say
comment
and
as
everything
is
here
between
markdown
files,
gitlab
or
render
renders
them
for
us.
So,
let's
start
with
reviewing
the
flat
investment.
Oh
before
I
continue.
This
talk
might
be
more
than
two
minutes
so
feel
free
to
stop
and
come
back
to
it.
A
When
you
have
a
bit
more
time,
I
tried
to
speak
fast,
but
I.
Sometimes
you
have
to
think
about
what
I
have
to
say
so
feel
free
to
speed
up
the
video
and
let's
discuss
the
investment
plan
now.
So
what
do
I
expect
us
to
deliver,
and
all
of
this
is
made
up
by
me.
So
definitely
come
back
and
share
your
perspective.
If
you
think
something
is
totally
unrealistic
of
what
I'm
sharing
here
a
bit
of
context,
you
know
our
team
size.
A
You
know
our
current
Focus
rate
has
been,
and
you
know
the
current
Hot
Topic
of
discussing
of
moving
towards
flux,
or
not
all
the
investment
plans
that
I'm
showing
here
assume
that
we
are
going
to
move
towards
flux.
This
is
still
not
decided,
but
I
had
to
make
an
assumption
here
to
to
make
my
life
easier
in
creating
these
plans.
A
So
in
kind
of
Team
level
topics
I
would
say
that
we
have
three
big
themes
that
we
could
tackle.
One
is
to
move
the
GitHub
software
into
viable,
actually,
I
think
that
we
would
be
almost
close
to
complete
or
even
lovable,
but
we
might
not
get
there.
That's
why
I
wrote
viable,
but
we
are
counting
the
way
towards
complete
and
together
with
githubs
I,
might
call
this
our
commanders
offering
as
well.
So
it's
not
just
vetoes,
but
that's
what
I
wanted
to
emphasize
here.
The
second
theme
is
I.
A
Want
us
to
be
able
to
remove
the
certificate-based
Integrations
in
17-0.
This
means
I
think
that
we
should
ship
the
blocking
issues
by
the
middle
of
2024
at
around
June.
In
that
case,
we
can
make
the
removal,
if
we
just
ship
it
like
three
months
before
17-0,
is
our
duplication.
Process
typically
requires
not.
A
And
the
third
topic
is
to
start
our
start:
shipping,
a
solution
on
the
deployment
management,
Direction,
actually
I,
updated
during
the
holidays.
The
deployment
management
direction
as
well
and
I
would
like
to
emphasize
two
parts
here.
One
is
deployment
management
project.
This
is
what
we
will
discussing
a
little
bit
here
and
there-
and
this
is
just
our
current
best
idea
as
far
as
I
understood,
based
on
our
discussions
with
tiger,
especially-
and
that
is
the
gitlab
delivery
framework.
Actually
that's
framework
here,
which
is
doesn't
exist
even
in
discussions.
A
Yet
it's
mostly
my
idea
how
I
try
to
think
about
all
our
offering
and
how
it
might
build
up.
Actually
you
are
welcome
to
to
comment
on
those
as
well
and
I
would
love
to
invite
you
to
do
so.
If
I
break
down
these
three
themes
into
kind
of
priorities,
you
can
see
what
I
mean
here
by
moving
to
viable
maturity.
I
actually
meant
mean
mostly
the
items
that
say
viable
here
that
we
would
get
those
as
I
said.
A
Everything
here
in
this
beautiful
gun
chart
is
just
my
guess,
so
they
might
be
totally
unrealistic.
Please
Come
Back
to
Me
video
comments
on
that
and
I
guess.
Actually
we
see
it
better
once
the
investigations
are
finished,
but
basically
this
was
the
idea
and
you
can
see
like
moving
many
things
to
everything
needed
for
viable
writing
docs
around
flux
that
will
be
the
first
MVC
step,
basically
have
a
tremendous
overview
on
the
environments
page.
A
We
know
that
support
clusters
that
can
see
it
lab
needed
for
removal
of
the
certificate-based
integration,
of
an
alternative
to
git
language
clusters
needed
for
the
removal,
and
then
we
have
the
gitlab
deployment
project,
kubernetes
dashboard
and
some
lovable
feature
set
from
around
github's
support,
which
is
automatic
access
to
manifest
containers
and
ham,
charts
stored,
Within
gitlab.
These
are
the
approaches
that
I
could
come
up
with.
A
Please
come
back
with
your
ideas
here
and
that
made
a
rough
breakdown
on
how
I
expect
this
to
fit
into
the
ear
the
axis
showed
the
month
and
I
think
we
should
focus
on
these
and
that's
how
we
could
deliver,
and
we
do
all
of
this
in
order
to
move
our
product
metrics.
There
are
many
many
metrics
that
I
think
we
could
move.
A
Some
of
these
metrics
don't
even
exist
today.
Yet
like
the
monthly
active
user
of
github's
usage,
I
had
it
as
a
development
around
Q2,
and
then
we
will
see
some
metrics
in
Q3
and
Q4
and
the
other
Matrix
as
well
like
this
might
have
an
effect
on
environments,
page
monthly,
active
user
number.
If
we
have
the
integration
with
the
environments
page
so
I
think
that's
a
great
cross
stage
initiative
and
for
the
metrics
that
we
have
I
tried
to
come
up
with
guesses
on
how
I
expect
them
to
move
given
days
features.
A
What
I
expect,
basically
is
the
value
of
these
features
be
for
the
company,
as
self-managed
is
typically
lagging
by
three
months
behind
SAS
I
separated
the
number
of
active
agents
on
SAS
and
self-managed.
So
we
have
a
better
understanding
of
defect
and
I.
Try
to
fix
our
CI
CD
monthly,
active
user
numbers
that
we
expect
to
drop
a
lot.
Given
the
fix
that
hod
runs,
you
out,
Made
In,
The,
Matrix
calculation,
so
I
just
take
one
seventh
of
the
current
metric
as
the
estimated
value.
A
A
There
is
an
investment
case
out
there
to
start
a
new
infrastructures
code
team
that
would
focus
on
terraform,
perhaps
cross-plane
ansible.
There
are
many
things
written
down
in
that
investment
case,
and
this
is
for
their
consideration.
It
shouldn't
affect
our
work.
I
think
expect
if
somebody
wants
to
move
into
the
newly
formed
team.
A
So
in
total
this
would
mean
like
actually
it's
plus
10K.
Oh
yeah,
there
is
not
much
yeah,
so
it's
yeah.
These
are
the
Q4
changes
that
matters
most
there
and
if
you
get
in
decreased
investment
like
I
hope
it
won't
happen,
but,
like
somebody
leaves
the
team
in
that
case,
the
effect
would
be
that
we
couldn't
delay
more
the
migration
towards
flux.
A
So
that's
because
that's
our
part
number
two
and
I'm
glad
over
it
that
we
would
be
able
to
do
that
if
the
investment
is
decreased.
So
these
are
my
thoughts
about
becoming
Financial
year
and
I
would
love
to
hear
your
feedback.
Please
comments
in
this
merge
request.
The
video
will
actually
be
shared
here,
and
all
of
you
are
going
to
be
pinged
here,
thanks
for
your
or
doing
this
with
me
for
giving
your
feedback
here
and,
as
I
already
said,
I
have
a
peaceful,
2023.