►
From YouTube: UX Showcase - Brief overview of Plan::Project Management group features and user value
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
All
right,
that's
what
I
was
waiting
for.
Thank
you
so
much
so
hello,
everyone,
my
name
is
holly
reynolds.
I
am
a
senior
product
designer
here
at
get
lab
on
the
plan
team,
I'm
having
some
zoom
window
issues
at
the
moment,
but
we'll
get
through
it.
I
want
to
take
a
quick
poll-
and
you
can
put
this
in
the
slack
or
in
the
zoom
chat
if
you
aren't
sharing
your
camera.
A
So
just
out
of
curiosity,
I'd
like
to
have
on
a
scale
of
one
to
five,
with
one
being
very
little
and
five
being
very
high,
where
everyone
thinks
that
they
rank
in
terms
of
understanding
of
plan,
particularly
as
a
stage
group
when
you
think
of
our
users,
maybe
the
things
that
we're
working
on
the
things
we
have
coming
on
the
pike,
I'd
just
love
to
see
either
show
of
hands
or
just
one
to
five.
Where
do
you
think
you
fall
on
that
scale?
A
See
a
three
two.
Let
me
check
the
chat,
really
quick
one.
Three
four
so
yeah
seems
like
it's
around
like
kind
of
kind
of
middle
of
the
ground
which
is
about
what
I
expected.
So
thank
you.
All
for
participating
in
that
that
helps
to
address
a
theory
that
I
have
so
plane
is
a
pretty
big
stage
group.
It
covers
a
large
amount
of
ui
real
estate
alexis
and
I
occasionally
get
pinged
in
issues
and
mrs
because
people
aren't
entirely
sure
if
we're
the
dri
on
a
specific
piece
of
the
product
or
not.
So.
A
My
first
objective
today
is
to
just
give
a
quick
overview
of
plan
and
maybe
help
clarify
a
little
bit
about
what
we
tend
to
kind
of
be
a
good
resource
for
she,
and
I,
in
terms
of
who
to
contact.
Of
course,
anyone
can
contribute
to
any
stage
group.
But
if
you
do
have
specific
questions
about
some
of
these
things
then
feel
free
to
ping.
A
Us
we
might
be
a
good
resource
to
check
in
with
next
I'm
going
to
provide
just
a
brief
overview
of
some
of
the
interesting
things
that
are
currently
happening
in
plan
and
then
touch
on
some
of
our
long-term
goals.
So
my
vision
here
is
just
to
zoom
out
a
little
bit
from
a
specific
feature
presentation
and
give
maybe
just
a
quick
refresher
of
a
broader
view
of
the
group.
A
Everything
is
in
the
handbook
for
the
most
part,
but
it's
kind
of
scattered
in
various
places,
and
I
know
we're
all
very
busy
working
on
our
own
stage
group
stuff.
So
my
theory
is
that
doing
this
kind
of
presentation
periodically
might
help
to
just
give
everyone
kind
of
a
quick
refresher
as
to
what
this
group
does
and
who
we're
working
for
and
then
again
kind
of
our
current
initiatives
and
upcoming
initiatives.
A
This
actually
came
about
after
chatting
with
valerie
not
too
long
ago,
on
the
importance
of
cross-stage
collaboration,
and
I
found
myself
thinking
through
it
and
asking
what
are
some
of
the
additional
ways
that
I
could
maybe
help
to
surface.
What
plan
is
doing
and
better
understand
what
other
groups
are
doing,
and
so
I
just
again
felt
that
having
this
refresher
at
a
very
high
level
at
times
might
be
helpful
to
kind
of
keep
some
of
these
things
top
of
mind
for
other
folks.
A
So
there's
three
stages
or
three
groups
within
our
stage:
project
management,
product
planning
and
certify.
We
work
closely
with
create
manage,
but
also
with
monitor
and
have
recently
worked
with
other
stage
groups.
Of
course,
some
of
the
things
that
keep
us
busy
most
frequently
are
issue
tracking
time,
tracking
boards,
epics
and
road
maps,
but
we're
also
good
resources
for
some
of
these
other
things
like
working
on
assignees.
A
If
you
find
yourself
with
questions
about
labels,
maybe
about
quick
actions,
but
plan
group
is
going
to
be
a
good
group
just
to
just
to
ping
and
maybe
see
if
we
have
any
additional
insights,
because
typically,
we
have
done
some
degree
of
research
on
most
of
these
things
and
have
talked
with
those
users.
So
we
may
already
have
some
understanding
that
might
be
beneficial
to
you.
A
So
before
I
go
into
the
next
slide,
another
quick
show
of
hands
or
scale
of
kind
of
one
to
five
in
terms
of
level
of
understanding
of
who
plans.
Personas
are
just
maybe
like
to
see
like
where
people
feel
like
they
think
they
stand
in
terms
of
knowing
who
those
folks
are
probably
like
a
two.
My
zoom
window
got
moved
over
here
again.
So
let
me
pull
it
back
over
see
some
chats
coming
in
so
yeah
felt
about
three
four
couple
of
fours.
I
see
so
that's
good
to
know
so
I'll.
A
Just
briefly
briefly
touch
on
this
because
again,
this
is
in
the
handbook,
but
the
personas
that
we
focus
on
most
heavily
are
parker,
which
is
the
product
manager
generally
delaney,
which
is
more
of
an
engineering
lead
presley
which
is
more
of
our
ux
interaction,
design,
product
designer
persona
and
then
sasha.
Who
is
the
engineer?
So
if
you
find
yourself
working
with
these
personas
and
have
some
questions
about
them
feel
free
to
ping,
us
we've
had
a
lot
of
conversations
with
these
personas
in
the
past.
A
We
have
a
lot
of
insights
as
to
what
their
challenges
are,
their
motivations
and
pain
points.
We
also
see
a
need
for
an
executive
persona
in
the
future.
Currently
we
have
that
as
a
buyer
persona,
but
we
are
looking
to
add
in
plan
analytics
in
the
future,
so
maybe
having
that
as
a
user
persona
in
the
future
is
going
to
be
something
worth
exploring,
but
an
example
of
why
this
is
potentially
valuable.
A
To
mention
here
from
a
recent
situation
was,
I
couldn't
tell
you
top
of
mind
who
monitors
users
were
until
recently
when
emilia,
and
I
had
to
work
together
on
incidents
which
was
something
she
was
creating
for
her
stage
group,
but
it
was
based
on
the
foundation
of
issues
which
is
my
stage
group.
So
it
was
an
opportunity
for
me
not
to
just
focus
on
my
own
personas,
but
the
personas
that
also
impacted
her
stage
group
as
well.
So
that's
really
the
main
reason
I
bring
it
up
here
again
in
the
handbook.
A
So
some
of
the
things
that
we
are
working
on
right
now
are
work
items.
The
long-term
vision
and
plan
is
to
make
the
process
of
work
stream
management
highly
configurable,
with
a
focus
on
having
a
great
user
experience
for
our
customers
and
the
context
of
tracking.
What
we
currently
know
of
today
is
issue
tracking.
This
means
allowing
users
to
create
generic
objects,
call
them
what
they
want
relate
them
to
one
another.
However,
they
want
and
customize
the
components
and
metadata
with
them.
A
However,
they
want
so
a
really
customizable
interface
for
those
elements
formally
known
as
collab
checks.
I
did
do
a
presentation
on
that.
In
the
past,
we
now
call
them
work
items
they're
kind
of
the
humble
beginnings
of
this
larger
vision.
So
again,
what
we
know
today
is
issues
epics
requirements
incidents.
They
may
eventually
become
types
of
work
items
alongside
bugs
features,
maintenance,
which
is
what
we're
calling
tech
debt.
A
So
those
are
some
of
the
reasons
again
I
mentioned
it
here
is
that
I
think
there's
a
lot
of
potential
to
interact
with
several
other
stage
groups
in
the
future,
and
I
just
want
to
surface
it
so
that
everyone
kind
of
knows
what
we're
doing
so.
Some
of
the
other
aspects
of
this
might
include
inline,
editing
for
titles
and
description
creation,
ux
improvements
to
help
reduce
context.
Switching
there
are
some
research
issues
that
I'm
working
on
currently
as
well.
A
But
if
you
see
that
this
is
something
that
might
be
impacting
something
you're
working
on,
please
feel
free
to
ping
me
reach
out,
and
this
could
be
an
opportunity
for
us
to
collaborate.
Feedback
is
always
highly
desired
as
well.
So
if
you
just
have
thoughts
on
on
these
experiences,
I'm
happy
to
share
my
figma
files,
anything
that
might
be
relevant
to
help
you
understand
kind
of
where
we
are
with
this.
A
The
next
is
automation
of
iteration
creation.
So
currently
our
users
have
to
manually
create
new
iterations
rather
than
setting
a
cadence.
We
do
have
the
concept
of
cadences
built
it's
behind
a
feature
flag
right
now
and
we're
sorting
through
some
some
issues
with
that.
But
the
thought
in
the
future
is
that
this
would
be
something
that
they
just
set
the
cadence.
It
automatically
looks
for
work
items
that
are
identified
as
open
and
rolls
them
over
automatically
into
the
next
cadence
saving
them.
This
need
to
have
to
go
in
and
manually,
create
one
each
time.
A
So
that's
something
that
is
currently
also
in
play,
improving
performance,
so
we've,
probably
most
of
us,
experienced
a
500.
Unfortunately,
when
pulling
up
our
issue,
lists,
we're
looking
to
improve
things
like
that,
as
well
as
making
discussions
load
faster,
use,
a
little
bit
less
memory
and
better
time,
better,
real-time
architecture,
so
time
unified,
state
management.
An
example
of
this
is,
if
you
have
closed
an
issue
recently,
you
may
have
noticed
that
you
don't
actually
see
the
state
change
to
closed
until
you
do
a
page
refresh.
A
So
this
is
something
else
that
we're
we're
working
on
and
looking
to
to
improve
the
experience
of.
As
far
as
what's
next,
we
have
extensible
issues.
This
is
creating
that
customizable
layout
for
work
items
so
again
giving
people
the
ability
to
really
determine
the
kind
of
widgets
and
metadata
that
they
might
want
to
have
in
their
work
item
views
that's
long
term
velocity
measuring
team
performance
for
better
planning.
A
This
might
include
showing
the
average
weight
completed
over
five
previous
iterations,
for
example,
showing
trending
and
velocity
and
volatility
over
previous
iterations,
so
really
helping
the
team
to
be
as
informed
as
possible
so
that
they
know
how
to
best
plan
for
upcoming
work.
Next
is
issue
statuses,
going
beyond
just
open
and
closed
for
what
would
actually
be
work
items
in
the
long
term,
two
offering
things
like
inactive
active,
completed
and
incomplete,
so
something
that's,
probably
a
bit
more
meaningful.
A
This
is
something
we've
had
a
lot
of
customer
requests
for,
and
I
think
it
could
be
really
valuable
to
to
offer.
This
also
saved
views
having
the
ability
to
define
and
save
configurations
for
views
like
lists
boards
and
roadmaps
and
finally,
actually
not.
Finally,
I
just
added
in
the
last
two
rollups
for
higher
initiatives,
so
surfacing
the
relationships
between
work
items
and
higher
level
initiatives.
A
The
primary
use
case
for
this
is
to
enable
our
business
leaders
at
the
executive
executive
level
to
be
able
to
create
a
set
of
business
goals
and
initiatives
and
map
those
efforts
toward
them
over
time.
This
will
also
allow
them
to
understand
how
much
work
was
committed
and
executed
toward
a
goal,
track
progress
toward
the
goal
and
understand
success
and
failure
over
a
period
of
time,
as
well
as
report
on
that
custom
fields
is
coming
up
much
much
later.
A
That
has
also
been
highly
requested
by
our
users
as
well
as
automation,
so
I
kind
of
like
get
lab
tree
at
triage,
but
having
that
as
a
native
option
within
gitlab,
I
know
that
was
a
lot
to
cover.
So
thank
you
for
your
time.
I
would
love
questions.
I
would
also
love
to
know
if
this
kind
of
presentation
is
useful
to
you
all.
Is
it
valuable
to
have
this
kind
of
high
level
overview
at
times
just
to
understand
what
a
stage
group
is
doing
at
a
high
level.