►
From YouTube: 12.10 KickOff Plan: Portfolio Management
Description
Plan Vision : https://about.gitlab.com/direction/plan/
Plan 12.10 Issues: https://gitlab.com/gitlab-org/plan/-/issues/79
Questions? Comments?
Ping me on GitLab!
@kokeefe
A
Everybody,
this
is
Keenan
from
the
product
came
here
to
talk
portfolio
management
in
1210,
I'm,
go
ahead
and
share
our
planning
issue;
okay,
so,
first
off
we're
going
to
be
kind
of
kicking
off
a
really
continuing
validation
on
what
has
branched
into
two
separate
problems
that
we
want
to
solve
here
in
the
near
future.
One
of
those
is
being
able
to
represent
epics
and
their
own
horizontal
swimlane
on
an
issue
board,
as
well
as
the
ability
to
build
like
a
program
level
board
or
an
epic
board
or
board
of
boards.
A
As
we've
had
some
customers
talk
about
it
with
just
giving
you
the
ability
to
actually
work
epics
across
a
horizontal
workflow.
Just
like
you
do
with
issues
open,
open,
a
new
epic
curating,
it
running
researcher
analysis
to
make
sure
it
has
all
the
information
in
it
to
make
you
work
breakdown,
where
it's
actually
getting
new
issues
added
to
it
that
aren't
ready
to
be
developed
yet
all
the
way
through
to
ready
for
implementation.
So
you
can
manage
a
board,
an
epic
on
a
board
level
and
get
to
a
point
where
it's.
A
This
is
now
ready
to
be
handed
off
to
the
engineers
or
to
the
development
team.
Actually,
kick-off
implementation
on
we've
had
a
lot
of
conversations
with
customers
concerned
scaling
their
planning
process
since
I
did
get
lab,
and
this
has
come
across,
as
you
know,
necessary
for
especially
we're
going.
Today's
is
running
safe,
really
again
just
trying
to
scale
an
agile
system
and
project
methodology
across
their
work,
so
we're
going
to
be
digging
into
that
really
heavily
over
the
next
couple
weeks.
If
thoughts
concerns,
you
have
strong
opinions
on
what
that
should
look
like.
A
Please
hop
into
that
into
that
issue,
which
you'll
be
able
to
get
to
from
the
description
of
this
video
we'd
love
to
talk
to
you
and
hear
from
you
and
even
hop
on
a
call,
if
you're
open
to
that.
So
we
can
pick
your
brain
as
far
as
design
priorities.
Go
we're
going
to
start
slowly
start
on
designing
what
we've
kind
of
talked
about
as
strategic
initiatives
or
mapping
work
to
value
in
get
lab
oftentimes.
A
This
is
how
many
issues
have
gone
towards
this
goal,
or
this
is
how
many
mrs
have
been
merged
towards
this
objective.
You
could
think
of
you
know.
Maybe
an
objective
is,
you
know,
increase
usage
of
new
product
by
fifteen
percent
and
maybe
you're
looking
amazing,
some
onboarding
flows
or
feature
adoption.
A
Who
who
would
be
interested
in
a
feature
like
this,
so
we
can,
we
can
gain
a
get
some
insight
and
some
feedback
on
the
designs
same
thing
with
epic
progress,
indication
we've
been
working
on
this,
as
we've
had
bandwidth
over
the
last
couple
releases,
which
is
really
like.
How
do
we
show
progress
inside
of
an
epic?
Isn't
a
progress
bar
his
progress
related
by
wait,
completed
or
issues
closed?
A
We
should
be
putting
some
design
designs
up
and
those
issues
soon
so
keep
an
eye
there
again
we'd
love
to
have
your
feedback
and
any
discussion
to
and
have
on
it
we're
open
to
that.
In
fact,
we
really
really
encourage
it.
So,
let's
talk
about
features,
we're
hoping
to
release
until
a
big
item,
we're
kind
of
collaborating
across
the
entire
planned
stage.
So
you
should
see
this
mentioned.
The
other
kickoff
videos
is
a
JIRA
importer,
which
would
be
our
first
VC
of
this.
You
know
this.
A
But
again
you
know
it's
one
separate
time
and
we're
gonna
we're
gonna
step
into
this
a
little
bit
each
each
release.
You
know
there
are
some
quick
wireframes
up
of
what
that
experience
is
going
to
look
like
it's
trying
to
keep
it
as
simple
as
possible.
We'd
love
for
you
to
hop
in
there
and
give
us
some
feedback.
A
But,
yes,
we
were
planning
on
putting
out
the
MVC
of
this
in
1210
so
that
we
hopefully
can
have
users
who
are
either
looking
to
move
off
here
and
come
to
get
lab
for
their
issue
management
or
any
organizations
that
are
maybe
okay
using
both
letting
one
team
use
it
and
giving
this
first
tool
to
kind
of
easily
pull
issues
over
that
they
need
to
start
working
in
get
loud.
So
please,
let
us
know
your
thoughts
on
that.
A
You
know
on
track,
needs
attention
or
at
risk
so
that
we
can
actually
start
bubbling
that
up
into
an
aggregated
level
report
to
kind
of
give
us
some
some
explanation
of
the
risk
or
the
health
of
a
chunk
of
work.
And
so,
if
you
actually
look
at
you
know,
here's
the
here's,
the
design
mock-up
that
we're
working
on
right
now
up
at
the
top.
You
actually
can
see
this
parent
epic.
A
You
know
it's
got
a
total
of
59
issues
inside
of
it
as
well
as
11
sub
X,
sub
epics,
and
here
you
say:
okay,
30
of
those
issues
are
in
track.
186
need
attention,
89
at-risk,
of
course
these
are
just
stub
numbers,
so
they
don't
have
a
properly,
but
it's
just
a
design,
design,
mock-up
and
eunsuh.
Then
each
sub
epic
also
has
like
a
mini
health
report
on
there,
showing
how
many
issues
are
on
track.
How
many
needs
gets
attention
again?
A
How
many
are
at
risk
and
then,
as
you,
expand
an
epic
in
the
epic
reopen,
you
can
see
the
individual
issues
and
their
their
health
risk
status
assigned
and
the
the
goal
again
here
is
really
just
to
start.
Giving
some
level
of
granular
reporting
of
how
work
is
progressing
and
providing
an
easy
way
to
flag
work
that
needs
attention
from
save
the
product
manager
or
maybe
a
director
or
something
they
need
to
be
reported
at
a
mid-level,
beating
or
a
director,
or
even
to
an
executive
team.
A
A
This
is
a
we're
super
excited
about
this
one,
we're
really
hoping
that
helps
users
solve
a
lot
of
these
reporting
problems
that
we
hear
them
talking
about
in
every
interview
that
we
do
so
again
keep
an
eye
out
for
that
in
12,
10
and
then
the
next
items
are
really
all
about
confidentiality.
We
talked
about
this.
The
last
couple.
Kickoff
calls
we've
been
slowly
moving
the
ball
forward
on
this,
but
we're
hoping
to
get
to
the
point
where
we
can
release
it
in
1210.
A
The
idea
that
you
know
we
already
let
you
have
confidential
issues
in
get
lab
and
a
lot
of
users,
especially
those
in
like
HR
finance
roles,
who
are
trying
to
combine
information
and
organize
it
have
struggled
because
you
can
actually
have
a
confidential
epic
to
house
your
confidential
issues.
So
here
the
first
time
we
were
to
do
is
being
able
to
any
new
epics
can
be
created
as
confidential
and
really
as
a
staff
just
like
on
issues
now
so
little
checkbox.
That
says
this
is
confidential.
A
With
the
follow-up
iteration
of
then,
allow
me
to
edit
its
existing
epics
to
toggle
them
unto
a
confidential
state
so
again
really
kind
of
quality
of
life
organization
of
confidential
information,
a
really
excited
to
kind
of
get
that
flexibility
to
the
users
that
need
it,
but
for
portfolio
management,
that's
what
we
have
for
1210
again.
My
name
is
Keenan.
You
can
find
me
in
debt
lab
at
K
O'keeffe.
A
You
can
hit
me
in
any
issue
or
apathy
of
topics
that
you
want
to
talk
about
feedback
concerns,
I'm,
always
open
to
getting
on
a
call
or
come
bruising
in
the
tool
or
over
email
on
to
collect
any
of
those
from
users
who
are
interested
again.
That
all
will
be
linked
in
the
bottom
of
this
video.
Thanks
for
watching
CNS.