►
Description
In this session- Alexis Ginsberg, Senior Product Designer from the Product Planning group walks through the first iteration of Epic Boards.
A
So
first
of
all,
you
may
have
heard
me
say:
product
planning
instead
of
portfolio
management,
and
you
heard
me
right.
The
plansage
has
a
sort
of
new
group
called
product
planning,
the
pm
of
certified
mark
in
the
designer
portfolio
management,
spoiler
alert.
It's
me
have
merge.
Forces
to
create
product
planning,
product
planning
will
encompass
all
the
work
that
certify
and
portfolio
management.
A
So
speaking
of
epic
boards
for
our
first
iteration
we're
keeping
these
fairly
similar
to
issue
boards.
That's
because
the
job
is
also
fairly
similar,
so
users
like
parker,
but
who
may
even
manage
more
teams
at
once
than
parker.
They
want
to
understand
how
larger
work
items
like
epics
are
moving
through
a
workflow
that
they've
defined
so
that
they
can
then
track
the
progress
of
these
larger
goals
or
ethics.
A
So,
basically,
epics
need
to
move
through
a
workflow
similar
to
issues,
but
users
don't
want
epics
to
move
through
the
same
workflow
as
issues
to
get
around.
This
users
are
currently
creating
issues
to
represent
epics
in
boards
because
they
can't
see
epics
and
boards
or
they're
just
resorting
to
planning
on
spreadsheets,
and
you
know,
I
think,
we've
all
heard
the
spreadsheets
thing
it's
kind
of
painful
and
we
want
to
make
things
easier
and
better
for
users.
A
So
if
you
remember
last
showcase,
I
talked
about
a
few
different
options
for
working
with
epics
within
a
board.
We
ended
up
prioritizing
option
c,
which
is
swim
lanes,
but
I
mentioned
the
option
b,
seeing
only
epics
moving
through
a
workflow
that
that
would
be
prioritized
probably
soon
and
that
time
is
now
ish.
A
So
let's
go
ahead,
get
and
get
hands-on
with
what
this
could
potentially
look
like.
So
again,
during
the
last
showcase
I
showed
y'all
swim
lanes
and
how
applying
swim
lanes
to
an
issue
board
could
help.
You
understand
how
not
only
issues
are
moving
through
a
workflow,
but
also
how
those
issues
are
funneling
up
and
progressing
towards
a
larger
goal
or
an
epic
or
a
child.
Epic,
in
the
case
of
this
so
really
for
epic
boards,
we're
just
basically
zooming
out
even
further.
A
A
So
here
you
can
see
that
I'm
now
within
an
epic
board
in
the
epic
section
again,
it
should
seem
fairly
similar
to
issue
boards
for
our
first
iteration,
like
I
mentioned
before,
because
it
is
kind
of
similar.
This
group
is
called
clammy.org,
where
someone
is
perhaps
planning
out
goals.
They
want
to
accomplish
kind
of
more
personal
goals
here
and
they're
leveraging
multiple
teams
to
help
them
accomplish
these
goals.
This
is
pretty
similar
to
someone
like
parker
planning
out
goals.
A
So
going
back
to
the
planning
party,
the
birthday
party
planning
scenario
that
I
keep
hammering
to
death,
let's
think
about
how
to
investigate
that
party
planning
we
looked
at
before
and
see
how
it's
progressing
at
an
even
higher
level.
So
now
I'm
going
to
create
an
epic
board
specifically
for
my
party
planning
team,
so
I've
created
my
party
planning
team
board
and
I've
scoped
it
to
the
events
team,
which
is
the
party
planning
team.
A
So
now
I
could
see
that
the
epics
that
the
events
team
is
working
on,
but
I
really
want
to
understand
how
these
epics
are
moving
through
our
workflow
stages
in
order
to
understand
how
they're
progressing.
A
In
order
to
do
this,
I
need
to
add
those
workflow
stages
by
adding
some
label
lists
time.
A
Boxes
like
milestones
and
iterations
could
also
be
really
helpful
here,
really
helpful
context,
as
perhaps
a
swim
lane,
or
maybe
also
as
lists,
but
for
our
first
iteration
we're,
starting
only
with
label
lists,
so
keep
watching
we're
going
to
keep
improving
this,
but
for
now
we're
starting
with
label
lists,
and
these
lists
would
really
vary
depending
on
what
workflow
user
prefers,
or
you
know
how
their
organization
is
structured,
but
you
may
notice
that
these
are
pretty
similar
to
the
ones
at
the
beginning
of
our
workflow.
A
That's
because
these
workflow
stages
to
the
left
of
a
board
should
ideally
be
worked
through
at
a
higher
or
epic
level,
so
I
could
see
maybe
designers
and
pms
working
on
epic
boards
in
the
future
working
through
epics
before
they
hit
the
issue
board,
but
I'll
get
to
that
in
a
second.
For
now.
A
A
I
think
she
may
want
to
shower,
but
I'm
not
totally
sure
I
wanted
to
really
validate
this
assumption,
that
she
even
wants
a
party
or
that
she
wants
it
to
be
a
baby
shower.
Maybe
there's
another
babe
there
another
party
she
wants,
and
I
really
want
to
know
what
kind
of
shower
she
would
like
and
what
requirements
she
has
to
make
her
party
a
success.
A
So
once
I
kind
of
know
that
I
may
move
this
epic
over
to
start
ideating
on
solutions
and
start
thinking
about
how
to
fulfill
those
requirements
or
requests
and
how
to
make
this
shower
a
success
and
once
I've
ideated
some
on
those
solutions-
and
I
have
the
idea
of
maybe
a
perfect
baby
shower.
I
can
then
move
this
epic
over
to
start
by
validating
those
ideas
that
I
came
up
with.
So
maybe
that
wanted
it
to
be
a
surprise.
A
I
could
talk
with
her
friends
or
family
or
other
moms
like
her
to
really
understand
what
that
perfect
baby
shower
is
and
how
close
to
that
mark
I've
gotten
and
once
I'm
fairly
sure
that
you
know,
I
know
how
to
plan
this
shower.
A
This
is
when
I
would
then
turn
to
my
team,
and
this
is
the
team-
that's
helping
me
build
or
implement,
or
throw
this
baby
shower.
So
I
work
with
them
to
break
down
my
big
idea
into
smaller
and
more
manageable
chunks
of
work,
so,
for
example,
this
could
be
things
like
buying
decorations
and
putting
them
up
sending
invitations
ordering
her
favorite
brunch
planning
silly
baby
shower
games.
A
I
don't
like
the
ones
that
involve
diapers
or
whatever,
so
this
is
where
I
would
start
creating
issues
that
are
smaller,
they're
actionable
and
they
could
be
flatted
out
in
an
optimal
way
to
make
sure
we
have
an
understanding
of
really
when
we
can
get
this
baby
shower
done,
and
if
it's
you
know
going
to
take
longer
than
expected,
maybe
we
can
scope
some
of
these
issues
down.
So
this
is
really
probably
when
I'm
moving
over
to
my
issue
board,
and
maybe
it
would
be
an
issue
board
with
epic
swim
lanes
applied
to
it.
A
So
that
kind
of
shows
you
how
epic
boards
and
issue
boards
could
work
together
and
why
you
might
work
on
one
versus
another.
A
So
you
could
also
think
about
it
in
terms
of
users,
for
example,
users
like
parker
or
maybe
some
casual
observers,
they're
really
interested
in
that
high
level
view
that
epic
board
provides.
They
might
not
be
as
interested
in
the
granularity
of
issues
and
probably
not
the
code,
whereas
users
like
sasha
or
delaney,
they
really
care
about
issues.
That's
what
they're
working
in
every
day.
That's
what
they're
creating
mrs
from
they
care
about
the
code
there
and
they're
really
interested
in
those
later
workflow
stages
that
you
often
find
in
development
or
issue
boards.
A
A
So,
let's
say,
for
example,
within
my
team,
going
back
to
the
birthday
party,
I
see
that
my
birthday
party
we're
almost
done
planning
it.
You
know
we're
already
we've
already
pretty
much
decorated.
The
team
has
done
a
really
great
job
of
breaking
down
this
decoration,
epic,
into
smaller
issues.
A
It
looks
like
most
of
them
are
on
track,
so
we're
doing
great
there,
but
we
do
seem
to
be
still
ideating
on
solutions
for
our
birthday
cake,
so
I
don't
know
exactly
what's
going
on,
but
I
think
what
it
is
is
that
we
don't
know
what
the
birthday
boy
would
prefer:
chocolate
cake
or
carrot
cake.
So
I
mean
I
need
I
may
need
to
like
ping
my
teammates
and
see
why
they're
still
working
on
this
and
ask
them
to
quickly
validate
some
of
their
assumptions.
A
So,
for
example,
I
think
they're,
assuming
that
he
would
want
a
carrot
cake.
So
maybe
they
can
move
this
to
solution,
validation
and
do
some
testing
on
the
recipe
or
you
know,
have
his
friends
test
out
that
carrot,
cake
and
see
if
that's
actually
what
he
would
prefer
and
then
we
can
get
that
that
epic
moving,
so
that
we
could
have
our
birthday
party
in
time.
A
A
I
could
also
just
have
another
board,
for
example,
the
plan
me.org
team
board-
and
this
is
looking
at
all
the
teams
in
this
group
and
seeing
how
the
ethics
within
them
are
moving
through
again
that
same
workflow.
A
So,
for
example,
here
I
see
that
go
on
a
road
trip.
This
epic
is
still
in
solution
validation,
but
I
know
that
our
team
wants
to
go
on
this
road
trip
after
we're
done
with
this
birthday
party
and
we're
almost
done
with
the
birthday
party,
so
they
should
probably
be
a
little
bit
further
along.
A
So,
to
do
this,
I
could
just
basically
set
up
a
board
using
team
labels
as
lists
instead.
So
here
you
see,
I
have
this
trip
planning
team,
and
this
is
the
team
that
has
to
go
on
a
road
trip,
epic
and
I'm
kind
of
noticing
that
they
may
be
struggling
capacity
wise,
who
isn't
right
now,
especially
due
to
the
current
events.
A
You
know
planning
trips,
it's
kind
of
hard,
so
one
thing
I
could
do
to
try
to
help
them
is
to
limit
their
work
in
progress,
so
I'm
going
to
set
a
width
limit
of
one,
and
you
could
see
that
here
and
there's
three
epics
within
it.
So
you
know
the
whip
limit
has
been
exceeded
and
what
this
is
telling
the
team
is
that
they
should
be
focusing
on
only
one
epic.
At
a
time.
A
This
will
hopefully
help
them.
Instead
of
focusing
on
many
things
within
this,
this
list
just
focus
on
one
thing:
get
it
done
before
they
start
moving
on
to
anything
else.
The
problem
with
this,
though,
is
that
I
actually
see
that
the
team
is
working
on
this.
Have
a
covid's
vacation,
epic
they've
done
a
great
job.
They've
already
started
breaking
it
down
and
the
issues
within
it
seems
to
be
fairly
healthy
and
on
track,
but
the
problem
here
is,
I
really
don't
want
them.
A
I
want
them
to
focus
on
a
road
trip
first,
because
that
is
blocking
some
of
the
party
planning
work,
so
I'm
going
to
go
ahead
and
rank
this
higher
in
the
list
so
hopefully
signify
and
signal
to
the
team
that
I
want
them
to
work
on
this
first
and
only
because
they
should
only
be
working
on
one
epic
at
a
time.
A
I'm
also
noticing
that
within
the
household
management
team,
they've
created
this
repair
exterior
epic,
but
I
think
there
should
be
a
repair
interior,
epic
here
as
well,
so
I'm
going
to
go
ahead
and
create
that
now
I
see
this
within
the
list
and
at
some
point
I'm
going
to
go
through
this
and
refine
it
with
my
team.
Add
things
like
labels
and
figure
out
when
it
should
be
due
and
started,
but
I'm
not
going
to
do
that
now.
A
So
that
was
my
very
quick
basic
demo
of
epic
boards.
We
have
a
lot
to
work
on
here,
a
lot
to
do
we're
still
working
very
heavily
on
epic
swim
lanes
and
also
requirements
management.
So
there's
plenty
of
time
for
us
to
keep
getting
feedback
from
y'all.
If
you
have
it,
I
created
a
very
general
feedback
issue
here,
if
you'd
like
to
add
anything,
there's
also
a
really
another
little
demo
of
epic
program
boards
in
there
thanks
so
much
to
everyone,
who's
already
left
feedback
in
there.
A
I
really
appreciate
it
and
I've
actually
applied
some
of
it
already.
So
what
you
do
really
matters,
and
I
really
appreciate
it-
you
can
also
leave
feedback
in
our
epic
that
includes
epics
pertaining
to
epic
boards.
A
Anywhere
you
want
to
leave.
Feedback
is
great.
You
can
always
ping
me,
though
I
see
mark
as
well,
so
keep
it
coming.
I
love
the
feedback.
I
really
appreciate
it.
Otherwise,
thanks
for
listening,
y'all
I'll
see
you
next
time.