►
From YouTube: Plan UX 13.1 Initiatives - Project Management
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
Hi
this
is
holly
Reynolds
senior
product
designer
for
a
plan,
just
because
I'm
not
quite
sure
who
all
gets
to
see
this
video
just
wanted
to
spend
a
couple
of
minutes
talking
about
what
we're
gonna
be
working
on
for
the
next
milestone.
I'm
gonna
share
my
screen.
This
is
the
project
management
side
of
plan
in
particular,
so
all
of
our
initiatives
will
be
focused
primarily
on
that,
with
the
exception
of
the
last,
which
is
a
little
broader.
A
Alright,
so
focusing
on
the
larger
monitor
here
and
I'm
gonna
zoom
in
just
a
little
bit
in
case
it
is
kind
of
small,
the
three
primary
initiatives
that
I'm
focused
on
in
particular
for
this
next
milestone
are
the
iteration
report.
So
this
is
the
report
view
that
shows
when
someone
selects
an
iteration.
This
is
going
to
function
very
similarly
to
a
sprint
or
the
concept
of
a
sprint,
but
we
are
calling
it
an
iteration,
because
his
friend
is
is
more
of
a
scrum
focus
term.
A
So
we
are
going
with
a
report
view
that
is
accessible
in
a
very
similar
manner
to
viewing
an
issue
or
MRR
youth
browse
the
item
from
a
list
that
you
would
select
from
that
kind
of
list
view
side
menu
and
then
choose
your
actual
iteration
from
there
and
then
that
would
take
you
to
kind
of
this
report
view.
We
went
through
several
revisions
of
this
particular
design.
So
you
can
see
some
wireframes
here.
A
This
particular
issue
by
the
way
is
to
180
to
77,
and
you
can
see
there's
a
lot
of
discussion
as
we
kind
of
started
going
through
even
more
happened
outside
of
this
particular
issue
and
some
other
issues
and
in
whimsical
and
where
we
have
kind
of
landed
is
here,
and
so
in
this
view
you
can
see
kind
of
overview
of
this
sprint,
page
or
iteration
page.
It
shows
the
status
of
the
iteration
a
title,
some
basic
description,
information
very
similar
to
the
milestone
page
currently,
and
then
we've
got
some
high
level.
A
Metrics
I've
actually
just
revisited
the
design
of
those
and
the
segmented
control.
Here,
after
some
quick
discussion
with
Nick
post,
that
was
super
helpful
on
how
he's
organizing
the
analytics
content
just
to
be
sure
that
we're
consistent.
So
they
can
filter
by
this
information.
These
particular
charts,
and
that
is
the
burn
down
and
burn
up
chart.
And
then
they
can
also
see
a
list
view
of
the
information
here,
either
by
issues
or
merge
requests
with
a
status
and
the
assignee
is
also
displayed.
A
A
The
next
would
be
the
JIRA
importer,
so
we're
working
now
on
phase
2
of
this
and
the
primary
area
that
I've
been
focused
on
for
this
is
setting
up
user
mapping.
So,
basically,
when
someone
imports
a
project
from
JIRA,
we
need
a
way
to
say
here
are
the
people
that
you
had
in
JIRA
that
may
have
commented
on
issues
or
so
or
whatever
the
case
may
be
in
JIRA,
and
then
we've
got
the
same
people
potentially
in
gitlab,
and
we
want
to
try
to
find
a
way
to
merge
those
those
users.
A
So
we
went
through
a
lot
of
discussion
about
this
particular
approach
again
as
well,
and
where
we
have
ended
up
is
something
kind
of
like
this,
where
they
can
choose
the
project
that
they're
importing
from
we
auto
assign
a
label
to
that
particular
project.
So
they
can
start
to
filter
issues
by
that
label
and
kind
of
organize
their
information.
A
That
way,
and
then
also
we
are
displaying
the
user
names
in
JIRA,
as
well
as
the
assumed
user
names
associated
with
that
individual
and
get
lab,
but
they
will
need
to
kind
of
verify
that
this
is
the
case.
If
there's
a
scenario
where
we
have
people
and
get
lab,
but
they're,
not
GRE
users
associated
with
it,
then
we
will
display
the
name
of
the
person
who
is
actually
conducting
the
import
process.
They
will
be
kind
of
the
new
owner
of
that
particular
issue
or
piece
of
work
you
can
see.
A
There
are
some
questions
here
from
the
developer
that
need
to
be
revisited.
One
other
piece
of
this
that
we're
considering
is
an
infinite
scroll,
so
in
this
case
they
could
potentially
have
lots
and
lots
of
users,
obviously
and
I,
wanted
to
find
a
way
where
we
could
preserve
the
buttons
here
at
the
bottom,
but
still
enable
the
infinite
scroll.
So
this
approach
is
proposing
kind
of
a
sticky
bottom.
I
know
that
we
have
the
footer
bar
that
displays
when
they
have
a
maybe
footer
alert
message
turned
on.
A
So
we
need
to
be
cognizant
at
that
and
how
these
items
might
stack
on
top
of
each
other,
not
literally
overlapping,
but
so
that
both
can
be
visible
and
accessible
at
all
times.
So
that
has
been
taken
into
consideration
as
well,
and
then
the
last
is
improving
the
love
ability
of
issues.
This
is
one
of
the
UX
okrs
and
it
also
includes
a
category
maturity
scorecard
process.
So
there
are
five
primary
issues
that
we're
focused
on
here,
one
which
has
several
smaller
issues
underneath
it.
The
first
is
to
fix,
select
and
search
inputs.
A
This
one
has
also
had
a
lot
of
dialogue
and
where
we
have
landed
with
this
is
it
seems
that
it
is
most
popular
in
terms
of
feedback
internally,
that
we
have
just
a
simple
X
that
appears
here
and
as
they
hover
over
at.
Perhaps
you
can
see
maybe
a
hover
state
to
provide
feedback
that
they
are
looking
to
select.
A
A
The
next
is
label
quality
of
life
improvements.
This
one
has
a
lot
of
issues
within
it,
so
you
can
see
there
are
a
lot
of
opportunities.
We
felt
to
improve
labels.
I,
don't
see
us
getting
to
all
of
those
in
this
particular
milestone,
but
we
do
have
a
few
that
we've
prioritized
as
kind
of
the
high
level
items
that
we
want
to
work
on.
First
and
those
are
listed
in
the
description
here.
A
So
that's
also
going
to
be
a
part
of
this
love
ability
of
issues,
effort
and
then
the
last
is
having
the
ability
to
assign
an
epoch
to
a
group
when
creating
an
epoch
from
within
an
epoch.
So
the
proposal
in
this
particular
case
and
we're
working
with
portfolio
management
on
this
one
is
to
simply
add
in
a
group
drop-down
when
you're
creating
a
new
epoch
so
that
you
can
select
a
group.
This
is
using
an
existing
pattern
very
similar
to
choosing
a
project
when
you're
creating
a
new
issue
within
an
epoch,
so
very
similar
functionality.