►
From YouTube: UX Kickoff 13.1 - Plan:Portfolio 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
there,
my
name
is
Alexis
Ginsburg
I'm,
seeing
a
product
designer
on
the
planned
stage,
I
work,
mostly
within
the
portfolio
management
group,
so
I'm
going
to
quickly
walk
you
through
or
working
for
13.1.
One
of
our
main
areas
of
focus
is
four
lanes:
Ameche
boards
and,
more
specifically,
epic
swim
lanes
within
a
shoe
board.
So
thank
you
for
how
users
my
group
issues
within
their
board
buy
epic.
A
First,
we
really
want
to
think
through
what
is
the
experience
of
turning
these
swim
lanes
on
with
an
issue
blood.
So
what
does
that
look
like?
What
is
the
experience
of
turning
these
on
and
specifically,
what
is
the
experience
of
turning
epic
swim
legs
on
and
then
also?
What
does
that
swimmingly
and
then
look
like
once?
It's
enabled
within
my
board
and
again
more
specifically,
what
does
an
epic
swim
lane
look
like,
and
how
might
we
make
this
the
most
usable?
A
It
can
be
we're
also
adding
in
a
few
configuration
options
into
the
Edit
board
Moodle,
so
for
NEC,
we're
adding
the
option
of
hiding
the
open
list
and
hiding
the
close
list
right
now.
A
user
can
collapse
these
two
lists,
but
they
can't
hide
or
remove
them
from
the
board
entirely
and,
more
importantly,
they
can't
hide
or
remove
the
issues
within
these
lists
entirely.
This
is
important
for
users
who
just
plan
a
little
bit
differently:
methodology
where
maybe
they
have
their
own
swim,
lay
our
own
labels
that
they
use
to
denote
open
and
close.
A
A
Once
we
have
swim
lanes,
we
also
want
to
allow
users
to
collapse
these
swim
lanes.
This
is
really
important
if
there's
perhaps
a
lot
of
swim
lanes
within
the
board,
maybe
they're
really
long.
Maybe
teams
have
multiple
teams
within
one
board,
so
some
of
the
swim
lanes
aren't
really
pertinent
users,
so
they
want
to
hide
them.
Maybe
they
just
want
to
tell
a
better
story
by
walking
through
one
swimlane
at
a
time
and
really
focusing
in
so
again
the
idea
of
letting
users
focus
on
what's
important
to
them
within.
A
A
Perhaps
I
can
also
see
it
with
an
epic
tree,
and
I
can
also
see
how
the
child
or
sub
epics
are
progressing
and
within
that
with
an
epic
tree
for
every
see
the
progress
metric
will
be
wait,
but
we
are
gonna,
keep
iterating
here
and
thinking
about
other
ways.
He's
always
wanted
to
know
progress
what
metrics
they
want
to
use.
Maybe
it's
a
issue
count
completion.
Maybe
it's
something
else:
we'll
keep
searching
and
iterating
here.
Another
big
area
focus
is
health
status,
so
we've
recently
introduced
this
and
we
think
it's
really
beneficial
to
users.
A
So
we
want
to
drive
usage,
how
we
can
and
make
this
the
most
usable
and
easy
to
use
as
it
possibly
can
be,
and
one
way
to
do
this
is
by
making
it
easier
to
assign
how
status
and
easier
to
edit
health
status.
So
one
first
step
here
is
showing
health
status
contacts
within
issue
list
itself.
Once
we
do
that,
we
can
allow
users
to
bolt
a
sign
or
book
edit
health
status
within
the
issue.
Us
so,
let's
say
I
know,
there's
five
issues
here:
that
I
want
to
assign
the
health
status
of
that
risk.
A
I
can
quickly
go
within
here
and
select
this
five
focus
on
the
health
status
of
that
risk.
Instead
of
going
to
each
of
those
issues
individually
and
I'm.
Not
once
we
have
this
as
well,
we
could
allow
users
to
filter
by
health
status.
So
again,
maybe
I
just
want
to
know
which
issues
in
my
lesser
at
risk,
I
can
quickly
filter
by
health
status
of
at
risk
and
action.
Upon
knows
how
I
want
you?
A
Similarly
to
this,
we
also
just
want
to
give
this
context
of
how
status
within
the
board
and
within
the
issues
within
the
board.
So
this
is
in
the
ability
users
to
see
the
health
status
of
the
issue
within
the
nation
board
itself
and
again
allowing
them
to
easily
edit
an
assignment
at
us
again
to
drive
usage
and
make
this
a
more
useable
feature.
So,
within
the
board,
I
can
quickly
assign
a
status
to
an
issue.
A
You
know
probably
the
board
the
sidebar,
because
that's
our
current
pattern
and
again
similar
to
the
issue
is
allowing
users
to
filter
by
status.
So,
let's
say
I'm
within
my
plan
board
I
want
to
know
what
needs
attention.
What
has
the
status
of
needs
attention
so
I
can
quickly
go
through.
I
can
filter
by
a
health
status
of
needs
attention
and
then
I
see
only
the
issues
that
need
attention
within
my
board.
A
We
also
want
to
iterate
on
our
drag-and-drop
interactions.
This
is
really
important
to
me
as
we
keep
adding
complexity
to
the
issue
board.
The
list
that
brick
tree
and
just
like
ultra
get
what
we
really
want
to
make
sure
these
are.
These
interactions
are
still
useable
and
then
also
add
in
a
lot
of
guidance
and
documentation
around
these,
so
that
we
could
better
utilize
them
I'm
working
on
this
with
a
member
of
the
US
Foundation,
it's
use
I'm
really
excited
about
that.
A
And
last
but
not
least,
we
are
thinking
about
initiatives
and
goals,
so
basically
strategy
planning.
So
this
was
really
at
the
research
and
validation
phase.
Thinking
about
how
users
would
plan
like
a
theme
level
or
an
initiative
level.
Currently,
we
only
have
epics
as
a
higher
level
object.
So
how
could
we
get
even
higher
level
objects
here?
What
would
users
expect?
A
How
would
they
want
to
use
those
we're
doing
like
I
said
some
validation
here
so
keep
watching
this
space
as
we
implement
some
of
these
ideas
that
will
be
coming
in
the
coming
milestones,
but
if
you'd
have
any
feedback
suggestions,
comments,
anything
feel
free
to
reach
out
to
Keenan
and
I
we're
happy
to
hear
from
you
have
to
talk
to
this,
otherwise,
this
13.1
and
in
that
child.
Thanks
for
listening
and
I'll
see
you
next
time.