►
From YouTube: Triage Package iteration, more emphasis on customer bugs and features that are unscheduled
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
This
is
the
latest
iteration
of
a
charge
package
that
we
invented.
We
meaning
that
quality
I
mean
invented
this.
This
takes
place
the
sitting
down
a
room
together,
going
through
the
JIRA
board,
with
your
managers
and
grooming
stuff.
So
we
essentially
put
out
a
automate
report
for
every
group
and
the
PM
and
EMS
are
cc'd.
The
first
second
is
on
schedule,
issues
that
it's
affecting
a
customer
and
that
the
matter
one
is
without
a
customer,
so
it's
always
customer
first
and
no
customers.
A
So
this
is
the
feature
section
and
the
second
one
is
bugs
so
there's
a
heat
map
for
funnin
sorry
heat
map
for
all
bugs.
Actually
you
may
be
familiar
with
this
with
some
representation
in
our
table,
so
unscheduled
front,
end,
customer
bugs
and
then
I
think
front
end
is
actually
doing
good
job
with
bugs
with
customers
or
didn't
have
that
section,
but
they
have
a
front
end
bug,
but
if
there
were
front
end
customer
bugs
they
would
have
another
section
in
here.
The
second.
B
A
Back
in
bug,
so
we
have
two
back
in
box
that
involves
a
customer
label
and
the
rest
are
non
customer
button.
There's
a
heat
map
for
miss
SLO
as
well.
It's
good
to
be
aware:
there's
no
action
item
for
for
any
of
us
to
do
anything
here.
It's
mostly
the
e/m
and
NPM
to
take
a
stake
in
the
ground
for
for
scheduling,
so
with
that
I
will
leave
it
up
to
team
to
decide
if
you
want
to
BCC
it
on
the
issues
or
not
and.