►
From YouTube: Plan Stage Weekly - 2022-09-28
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
So
I
realized
and
we
can
change
this.
We
can
skip
this
if
I
just
missed
it
during
one
of
the
plan
week
please,
but
we've
brought
on
a
few
new
people
to
the
team
and
I.
Don't
think
we
ever
did
the
formal,
formal
introductions
so
I
added
it
to
the
to
the
team
meeting
today.
I'm,
not
sure
if
they're
all
here
but
Amanda
are
you
here.
Yes,
you
are
I'm.
B
B
Sure
so
I'm
Amanda
we'll
be
at
gitlab
four
years.
This
Saturday
coming
from
the
product,
intelligence,
team
and
fulfillment
before
that,
why
did
I
decide
to
join
plan?
B
I'm
a
big
dog
fooder
and
I'm
like
uber,
organized
or
I'd
like
to
be
and
I
really
want
to
make
to
improve
what
we
already
have
for
both
the
day-to-day
of
the
product
person,
but
also
like
cross-functional
projects,
I've
been
on
several
here
and
they're,
really
hard
to
organize
using
gitlab
and
I
have
like
this
lifelong
dream
to
keep
people
out
of
sheets
and
Google
Docs.
B
So
that's
basically
why
I
was
really
attracted
to
the
role
where
am
I
located
I'm
in
San
Miguel
de
Allende,
which
is
in
central
Mexico
I'm
about
four
hours,
Northwest
of
Mexico
City,
and
what
I
like
to
do
for
fun?
I,
don't
really
do
a
lot
of
things
for
fun.
I
have
two
boys,
six
and
11,
and
so
I'm,
usually
just
doing
stuff
with
them
or
cooking
or
chilling
with
my
jeans
and
that's
it.
C
Yeah,
sorry,
it's
a
little
early
and
I
in
Seattle
here
so
So
yeah.
Thank
you
for
the
the
brief
intro
I
just
jumped
on
so
I.
Don't
know!
If
anyone
introduced
me
at
all,
but
yeah
so
I
joined
playing
on
the
19th.
It
seemed
like
a
really
great
opportunity
to
improve
requirements.
Management
specifically
and
I've
been
digging
through
a
lot
of
the
tickets,
especially
from
internal
folks
and
there's
so
many
small
improvements
that
can
be
made
to
make
the
user
experience
better.
C
So
it
seems
like
a
really
good
chance
to
improve
something
about
the
product
that
maybe
just
a
few
customers
are
using
so
far
but
could
be
used
much
broader.
C
C
I'm
located
in
Seattle
I
am
originally
from
Montana
a
super
rural,
small
town
and
outside
of
work.
I
love
to
run
I
love
to
cook
I
was
talking
to
a
couple
of
people
yesterday.
So
I
like
to
bake
I,
have
a
Pieology
book
that
I've
been
digging
into
that's
super
fun
and
then
in
the
winters
I
like
to
ski.
D
Very
jealous
when
those
pictures
come
through
I
think
Matthew
I
will
be
signs
and
Mitzi
Harris
I've,
been
at
kitlab
since
January
before
being
in
certified
I
was
in
manage
working
on
the
important
optimized
groups
and
decided
to
join
plan
for
a
couple
of
different
reasons,
but
one
of
the
most
exciting
ones
is.
The
overlap
between
all
of
the
different
groups
in
plan
would
allow
me
to
work
really
closely
with
other
product
designers,
and
so
that's
something.
D
That's
really
exciting
for
me,
I'm
located
in
Barry
Island
in
South
Wales,
which
is
part
of
the
UK
and
on
the
right
on
the
coast,
about
10
minutes,
walk
from
four
different
beaches.
It's
lovely
and
similar
to
Amanda,
I
have
and
small
children,
which
means
there
is
no
outside
of
work
other
than
then
I've
got
a
four-year-old
and
a
18
month
old.
So
lots
of
time
is
spent
with
them
and
in
a
couple
of
hours
that
I
can
find
to
myself
play
lots
of
video
games
addicted
to
my
switch.
A
Awesome
well
thanks
all
and
welcome
to
the
planty
okay,
on
the
other
side
of
things,
I
think
everyone
has
seen
the
announcement
that
rajat
is
leaving
the
team
for
another
opportunity
last
day.
Is
this
Friday
I?
Don't
think
Richard
is
here
it's
pretty
late
out
there
yeah
he's
not
but
yeah
we'll
miss
we'll
Mr
Jatt,
it's
great
working
with
him
with
you
rajat
over
the
past
three
and
a
half
years
four
years
now,
but
again
excited
for
his
for
his
next
opportunity.
E
I
am
still
on
the
call.
I
will
leave
literally
internet
so
super
quickly.
We
have
architecture,
blueprint
merged
for
work
items,
it's
very
basic
as
per
now
very
high
level
and
I
would
be
happy
if
you
have
something
to
add
to
the
blueprint
and
I
believe
almost
everyone
has
something
to
add
to
it.
Just
keep
in
mind.
E
It
should
be
architectural
blueprint,
so
not
an
implementation
detail,
but
high
level
architecture,
I
plan
to
extend
it
a
little
bit
with
the
font
and
architecture
and
how
we
do
things
on
the
frontal
work
items,
and
it
would
be
great
to
see
something
from
the
back
end
too
now
rush.
But
if
you
have
time
and
inspiration,
please
do
contribute
and
Gabe
is
not
on
the
call
so
back
to
Donald.
A
Okay,
cool
next
time,
all
right
Gabe
says
there
is
a
renewed
interest
in
dog
fooding
service
desks
internally,
as
well
as
make
me
a
more
robust
to
support
additional
itsm
use
cases.
Gitlab
the
company
provided
a
list
of
requirements.
They
are
deciding
right
now
whether
to
buy
an
external
itsm
solution
or
make
an
investment
to
build
the
necessary
capabilities
into
our
product.
A
There's
a
chance
we
may
get
some
funding
to
hire
a
vendor
to
accelerate
in
the
near
term
or
being
asked
now
is
to
provide
a
high
level
summary
of
how
far
we
think
we
get
within
a
12
month
period
of
time.
What's
the
best
way
to
approach
this,
and
then
we've
got
a
couple
links
here
that
he
included
and
Alexander
oops
like
you
want
to.
A
F
Yeah
I
had
some
questions
basically
by
looking
briefly
looking
at
the
issue
and
given
his
question
is
how
how
what
was
the
best
way
to
kind
of
approach
it?
My
question
is:
how
does
that
align
with
whatever
we're
doing
in
work,
work.
F
Is
what
his
seemed
to
be
suggesting
for
him?
I
mean
Gabe,
so
yeah.
The
question
was
how
how
much
overlap
there
is
with
work
items
and
do
actually
the
priorities
for
for
that
interest.
Aligned
with
the
priorities
of
the
work
items,
because,
like
I
I,
have
a
feeling
that
in
Plano
is
we
cover.
F
Then
we
jump
from
one
thing
to
another,
so
yeah.
If,
if
the
priority
is
aligned
with
what
we're
doing
in
work
items,
we
can
slightly
maybe
readjust
to
what
we
want
to
do,
or
we
can
more
easily
guide
the
I.T
help
team.
They
may
want
to
implement
something
in
in
lines
with
what
we
do.
You
want
to
do
with
work
items
and
so
on.
A
Yeah
I
think
we
can
probably
just
have
everyone
read
through
that,
but
just
briefly
looking
through
it
looks
like
for
the
most
part,
there
is
a
lot
of
overlap,
but
I
think
before
we
even
talk
about
moving
sir
moving
that
stuff
over
to
work
items
like
we
want
to
see
if
there's
a
way
to
essentially
build
it
before
it's
a
work
item,
but
yeah
I
think
everyone
can
just
read
through
your
you're
engaged
back
and
forth.
There.
F
A
F
F
Maybe
concept,
structures,
maybe
a
lot
of
the
code,
but
have
it
into
a
different
data
storage
or
like
how
much
interaction
is
there
between
work
items
as
we
currently
see
them,
and
the
IT
staff
of
of
managing
a
lot
of
those
configuration
management,
different
decision
and
so
on
and
so
forth
like?
Why
are
not
issues
enough
to
track
the?
E
F
Really
only
about
custom
Fields.
Is
it
something
different
like
there
are
yeah
I?
Don't
I,
don't
exactly
I
didn't
go
through
everything,
so
probably
a
good
idea
would
put
me
would
be
to
just
work
for
everyone
just
to
go
and
and
see
what
what's
different
from
what
we
have
and
how
much
that's
where
it
were
like
how
how
much
we
should
debate
or
what
extra
we
need
on
top
because,
like
even
if
we
talk
only
about
custom,
Fields
I,
don't
think
that's
something
that
we'll
have
in
near
term.
F
C
Just
a
quick
note,
too:
the
service
desk
was
recently
realigned
to
certify
and
in
terms
of
privatization,
I
saw
Dan
was
just
putting
it
in
there.
C
It
was
relatively
small
in
terms
of
the
time
commitment
we
were
thinking
for
upcoming
planning,
so
we
were
hoping
to
focus
primarily
on
requirements
over
service
desk,
but
this
is
a
good
discussion
item
I,
think
I
can
chat
with
Melissa
and
I'm
so
new
to
the
team
that
I
think
it
would
be
really
valuable
to
get
her
opinion
on
it
and
I
know
Gabe's
not
on
here,
but
I
could
touch
base
with
him
as
well
to
see
sort
of
his
thoughts
around
this.
A
Yeah
and
that's
kind
of
been
the
question
around
service
desk
for
a
bit
is
that
there's
been
kind
of
this
desire
to
prioritize
it,
but
there
hasn't
been
a
whole
lot
of
commitment
internally
to
actually
putting
putting
effort
towards
improving
it.
So
I
don't
know
if,
just
with
what
Gabe
is
saying
here
on
kind
of
the
renewed
interest
in
internally
using
it.
If
that
means
we're
increasing
the
priority
of
it
as
an
organization
or
if
it
just
yeah
I'm,
not
sure
what
the
exact.
What.
A
As
far
as
what
we
want
to
commit
to
it
so
I
think
yeah,
that's
a
good
idea
to
to
meet
up
with
Melissa
and
kind
of
on
the
product
side
figure
that
stuff
out
before
we
decide
to
either
focus
on
it
internally
or
bring
on
a
third
party
to
help
us
with
that
or
not.
A
Okay,
we
want
to
move
on
to
the
next
point:
I'm
not
sure
who
put
this
on.
There
was
a
Gabe
or
someone
else.
G
Oh
yeah,
sorry,
that
would
have
been
me
sure,
so
this
is
like
literally
I
was
like
working
on
this
just
before
this,
but
I
figure
we
can
take
a
quick
look,
that's
some
of
what
we're
thinking
right
now.
The
goal
is
just
to
get
some
ideas
out
there
to
take
back
to
customers
related
to
Velocity
and
volatility.
G
So
this
is
basically
an
extension
of
the
cadences
and
iterations
functionality,
kind
of
allowing
teams
to
better
understand
the
typical
progression
of
the
team.
So
how
many
like
points?
G
Do
you
typically
do
on
average
and
trying
to
build
some
of
these
metrics
in
we've
got
some
like
customers
that
have
basically
sketched
out
different
things
that
they
want
different
metrics,
we're
starting
relatively
small,
with
just
more
or
less
velocity
and
volatility,
but
I
think
part
of
what
we're
looking
to
gain
a
better
understanding
of
as
well
as
like.
Do
those
two
alone
give
you
enough
value
out
of
the
gate,
and
then
we
can,
you
know:
can
we
build
in
some
of
those
more
business
oriented,
metrics
down
the
line?
G
You
know
different
ways
to
present
it,
and
things
like
that
so
kind
of
the
biggest
potential
change
here
is
that
your
cadences
page,
which
today
is
a
blend
of
cadences
and
iterations,
could
actually
become
a
driver
into
iteration
or
into
like
a
detail
page
that
doesn't
exist
today,
but
you
know
at
a
minimum,
basically
adding
in
some
the
metrics
here.
Velocity
is
typically
just
an
integer.
G
Volatility
is
typically
a
percent,
sometimes
with
a
standard
deviation,
which
would
just
be
a
number
and
then
potentially
some
sense
of
completion
for
the
current
iteration.
If
there
is
one
and
then
driving
into
a
detail
page,
so
this
is
a
detailed
page
for
Cadence
look,
so
this
doesn't
exist
today.
So
this
would
be
like
all
sort
of
net
new
where
you
can
see
your
your
velocity
and
then
this
is
sort
of
the
roll-up
of
that
velocity,
so
you're
typically
looking
at
like
what
did
you
plan?
G
What
did
you
actually
do?
How
does
that
sort
of
change
over
time
and
you'd
have?
Basically
it's
like
a
couple
things
to
add
here
would
be
like
the
velocity
line.
Maybe
an
average
trailing
velocity
so
just
giving
you
us
a
little
bit
of
a
sense
of
like
where
does
this?
This
number
come
from?
G
How
has
this
sort
of
change
over
time,
ideally
as
your
team,
matures
that
line
gets
pretty
flat,
maybe
with
a
few
changes
over
holidays
and
things
like
that,
and
then
a
view
of
your
iterations
within
this
Cadence,
so
you
can
kind
of
see
what's
coming
up
and
then
I
think
the
more
fun
part
of
this
is,
you
know,
actually
maybe
building
in
a
board,
so
you're
managing
your
iterations
within
this
Cadence.
G
This
is
something
that
teams
can
do
and
all
their
products
today
is
basically
like
just
quickly
get
to
this,
like
I,
want
to
move
this
from
this.
To
that
you
know
with,
while
seeing
some
of
the
like,
you
know,
velocity
metrics,
so
you
can
kind
of
see
I
think
the
Sprint
will
be
like
well.
You
know
this
Sprint,
like
let
me
kind
of
plan
accordingly,
today
you'd
kind
of
have
to
jump
around
a
little
bit
to
do
this
again.
G
These
are
just
ideas
that
we're
kind
of
testing
but
kind
of
a
you
know
showing
some
of
the
the
ideas
here
and
the
iteration
side.
Iteration
report
changing
only
a
little
bit
building
in
the
velocity
metrics,
and
maybe
some
cleanup
of
the
the
presentation
as
a
opportunity
for
if
we're
touching
this
and
then
again,
building
in
potentially
some
of
the
boards
and
things
like
that,
something
like
composition,
just
like
a
different
sort
of
way
to
analyze,
iteration.
G
G
G
So
this
could
either
be
scoped
to
like
current
iteration
for
a
Cadence,
where
it's
going
to
automatically
pick
the
iteration
or
to
a
single
specific
iteration,
just
whatever
it
gives
you
that
single
iteration
and
then
kind
of
pulling
in
some
of
those
metrics
into
the
board
View
with
like
an
extended
sort
of
preview,
so
that
you
know
again,
if
this
is
kind
of
your
workspace
for
managing
your
iteration,
you
can
kind
of
see.
Where
are
you
at
in
relation
to
your
velocity?
G
And
you
know:
how
does
that
sort
of
compare
to
things
over
time?
And
then
you
can
kind
of
track.
You
know
your
progression
as
you
as
you
work
through
that
Sprint.
Similarly,
you
could
do
this
at
the
Cadence
level.
So
if
you
Scope
this
to
a
single
Cadence,
you
get
that
same
sort
of
view.
Where
you
can
see.
You
know
your
next
five
iterations
or,
however
many
you
have
upcoming,
and
then
here
you
could
actually
put
like
the
the
Velocity
in
here
similar
to
like
a
whip
limit.
G
Where
you
know
you
can
kind
of
see
how
far
away
are
you
like.
You
know
how
here
you've
got
18.
You
could
add,
you
know,
maybe
a
bug
or
something
like
that,
and
obviously,
if
you
can
move
stuff
to
your
later
iterations
and
spread
it
out
and
then
similar
like
you
know,
this
could
grow
over
time.
As
we
add
some
of
these
other
analytics.
G
But
you
know,
starting
with
basically
volatility
and
velocity
and
and
then
trying
to
track
some
sense
of
like
plan
versus
completed
for
anything,
that's
in
progress
and
trying
to
kind
of
keep
those
metrics
like
similar
but
but
different,
so
that
we're
not
blending
too
much
of
the
planning
stuff
like
velocity
and
then
the
completion,
which
is
a
little
bit
different
Focus.
G
This
will
probably
change
a
little
bit
by
the
next
time.
You
see
it
but
yeah.
That's
kind
of
the
idea
of
what
we're
testing
out.
B
I
have
so
many
comments
and
questions
first,
I
couldn't
love
any
of
this
more,
it's
so
great
one.
A
lot
of
my
questions
are
going
to
be
because
I
don't
know.
I
haven't
been
here
who
owns
these
features?
Who
would
build
these?
Which
team.
B
All
right,
I'm
jealous
second
love,
the
composition,
feature
I,
think
that's
amazing.
It
would
be
really
cool
if
you
aren't
already
but
including
Health
score,
a
quick
view
to
see
by
the
health
score
and
then
like
a
drill
down
eventually
into
those
issues,
would
be
really
cool,
really
really.
B
So
I
apologize
first,
have
we
considered
a
future
for
capacity
tracking
at
all,
because
that
would
be
so
lovely
to
merge
into
this,
because
seeing
that
plan
number
right
next
to
the
capacity
number
right
would
be
really
powerful.
G
I
see
Gabe's
not
on
the
call
I
know,
that's
something
that's
out
there,
but
it's
not
I,
don't
think
it's
something
that
we
are
working
on
yeah,
but
I.
Think
Gabe
and
I
were
talking
about
this
yesterday,
like
that,
would
be
kind
of
like
the
next.
The
next
iteration
like
this
is
velocity
is
like
inside
in
some
ways
a
stop
Gap
to
capacity
it's
just
sort
of
flattening
Your
Capacity
out
to
a
single
like
Team
level
metric,
as
opposed
to
looking
at
like
something
individual.
G
One
thing
we
talked
about
was,
if
you
could
at
that
Team
level,
basically
just
say
for
this
iteration
we're
at
like
90
capacity,
which
I
think
he
has
a
more
complicated
way
to
describe
the
calculation,
but
I
think
it
basically
just
took
this
velocity
and,
like
tried
to
you,
know
calculate
what
90
of
that
would
be
using
some.
You
know
metrics
around
that
particular
you
know
team
and
and
what
they
typically
do.
G
So
that
would
be
like
the
lightweight
way
to
do
it
and
then
the
more
complicated
way
that
we
could
explore
in
the
future
would
be
like.
You
know
this
team
member
is
out,
and
what
does
that
team
member
typically
right
contribute
towards
this
velocity.
B
G
G
Right,
we're,
like
you
know
you
could
you
just
have
iterations
that
are
like
subordinate
to
iterations
and
one
of
those
basically
acts
as
a
milestone,
one
of
those
actual
generation
I,
don't
think,
there's
anything
kind
of
defined
or
planned
in
that
space
at
the
moment,
but
yeah
I
think
it's
something
that
we
would
like
to
look
at
at
some
point.