►
From YouTube: Plan 14.3 Kick-off
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
B
The
first
one
is
a
shared
kind
of
initiative
across
all
of
the
stages
are
all
the
groups
within
the
plan
stage
and
it's
called
work
items
we've
talked
about
this
a
little
bit
before,
but
the
work
item
initiative
is
is
mainly
to
sort
of
merge
requirements,
epics
and
issues
under
the
same
data
model.
Its
goal
is
to
enable
us
to
reduce
technical
product
debt
and
for
performance
and
create
a
better
foundation
for
more
efficiently
realizing
our
future
plan
direction.
B
B
So
we
have
sort
of
kind
of
a
fresh
in
the
first
kind
of
mvc,
one
we're
focusing
on
adding
a
title,
adding
an
assignee
and
adding
a
description
and
then
being
able
to
create
and
save
that
it's
pretty
straightforward.
B
As
part
of
this
work,
we're
probably
going
to
be
able
to
ship
default
issue
types
is
what
we're
calling
right
now,
which
will
be
customer
facing
so
issues
will
now
have
a
type
feature,
will
be
reserved
sort
of
behind
a
feature
flag
as
we
work
on
that,
but
you'll
be
able
to
win,
creating
an
issue
now
selected
if
it's
a
bug,
an
enhancement
if
it's
technical
debt
or
if
I
think
we're
renaming
this
maintenance-
and
we
already
have
our
system
default
issue
types
of
incident
issue
and
test
case
at
this
point
in
time,
and
I
think
requirements
will
be
closed
as
well.
B
Along
with
this,
we
want
to
add
support
for
filtering
by
issue
type
within
boards
and
lists.
So
if
customers
and
users
want
to
be
able
to
just
look
at
their
incidents,
they
can
do
that
or
just
the
requirements
or
just
test
cases.
They
can
filter
down
within
the
board
view
to
view
just
those
types
of
issues
as
well
as
within
the
list
view.
So
that's
sort
of
what
we're
tackling
for
the
work
items
initiative
and
then
there's
some
other
things.
We're
going
to
be
spending
50
of
our
backend
engineering
capacity
on
sas
reliability.
B
B
We're
also
going
to
be
focusing
on
improving
performance
of
projects
endpoints,
which
is
the
worst
performing
endpoint
from
an
air
budget
standpoint
and
then
also
improving
the
performance
of
bonsai
pipelines,
which
bonsai
pipelines
are
the
things
that
render
a
lot
of
the
markdown
to
determine
rules
like
who
to
highlight
or
who
to
app
mention
and
then
to
support
the
starting
effort.
B
We're
going
to
be
focusing
on
changing
the
project
to
use
the
not
use
the
access
taggable
gym,
and
this
will
allow
for
kind
of
some
isolation
so
that
we
can
move
forward
with
the
sharding
initiative
and
then
there's
a
couple:
security
regression
high
performance
bugs
which
you're
gonna
also
try
to
tackle,
and
then,
lastly,
we
weren't
quite
able
to
finish
up
iteration
cadences
and
make
a
general
available
in
14.2.
B
C
Let's
just
share
desktop
share
the
whole
screen,
okay,
so
my
name
is
kristin
debenko
and
I'm
also
senior
pm
in
the
plan
stage,
and
I
have
the
product
planning
group
just
like
you
mentioned.
All
of
us
are
focusing
on
the
work
item
initiative.
So
that's
our
priority,
but
we're
also
trying
to
put
around
50
capacity
towards
error,
budgets
and
performance
issues.
So
I'll
just
talk
through
a
couple
of
these
a
shared
one
that
gabe
mentioned
is
the
observability
of
the
bonsai
pipeline.
C
If
we
get
this,
this
will
open
up
a
lot
of
other
performance
and
we'll
be
able
to
see
a
lot
more
of.
What's
going
on.
There,
we've
also
opened
this
spike
to
investigate
an
alternate.
Alternate
implementations
of
issue
counts
on
gitlab.com,
and
so
this
will
allow
the
engineers
to
get
in
there
and
see
if
there's
anything
else,
that
we
can
do
around
issue
counts
and
how
those
are
performing.
C
We've
prioritized
four
error
budget
issues,
the
first
meaning
the
first
being
visiting
epic
boards
in
public
groups
as
a
non-logged-in
user
can
fail
this
one,
we're
not
sure
exactly
how
much
this
one
will
contribute
to
improving
them,
but
it's
an
important
one
to
look
at
testing
500
cases
instead
of
404s
when
records
are
not
found
serving
resized
design.
Images
has
invalid
sql,
which
is
slowing
things
down,
and
then
we
still
have
from
our
q3
okr
and
a
carryover
from
14
2,
which
is
improving
performance
of
epics
discussion.json
endpoint,
so
that
we'll
keep
working
on.
C
There
is
still
some
work
going
on
on
roadmap
filtering,
which
is
a
carryover
from
14.2
and
adding
horizontal
scrolling
with
infinite
dates.
This
one
has
actually
slipped
a
few
milestones,
but
hopefully
in
143
we'll
have
this
shift
and
we're
looking
at
our
board
code
and
some
of
the
cleanup
that
we
can
do.
We've
got
two
open
issues
here
for
issue
boards
to
make
them
more
performant
and
those
are
also
carrying
over
from
14
too.
D
B
D
As
they
mentioned
above,
the
workout
initiative
is
the
primary
thing
that
is
being
done
in
the
certified
team,
because
we're
very
excited
to
update
requirements
to
use
this
requirement
issue
type.
This
will
be
a
huge
benefit
to
our
requirements.
Users,
it'll,
bring
things
like
labels
and
other
issue
type
items
to
requirements
which
has
been
often
demanded
by
our
customers,
so
that's
really
exciting
other
than
that.
D
Our
error
budgets
actually
look
pretty
good
right
now,
but
I
know
that
some
of
the
back
end
team
is
assisting
the
portfolio
team
and
the
product
planning
team
on
their
efforts
as
well.
So
we're
very
excited
to
see
some
of
those
air
budgets
be
decreased
over
time.
That's
pretty
much!
What
we
have
here.
The
one
issue
we're
tackling,
as
I
mentioned
above,
is
the
requirement.